topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • February 24, 2020, 12:29 AM
  • Proudly celebrating 14 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Last post Author Topic: RealWorld Paint 2013.1  (Read 17570 times)

fenixproductions

  • Honorary Member
  • Joined in 2006
  • **
  • Posts: 1,186
    • View Profile
    • Donate to Member
Re: RealWorld Paint 2013.1
« Reply #25 on: June 26, 2013, 06:24 PM »
Is it possible to have translation files in plain text form?

I know that having all localisation strings in DLL may be easier to implement but it burned down my desire to have decent Polish version. Current one is rather poor* and web interface for localisation is not a good option.
Do I really need to translate something via website and wait for next application version to even check if it fits? Seriously?

I am also wondering about support for plural forms: some languages have more than one plural and I can't see it supported here. To be honest, most of the software do not care about it and only XYplorer has it right as far as I know.

*) i.e. "blur" is translated as "not sharp" instead of true "blur"; "animation" is translated into word that does not even exist

vlastimil

  • Honorary Member
  • Joined in 2006
  • **
  • Posts: 308
    • View Profile
    • Donate to Member
Re: RealWorld Paint 2013.1
« Reply #26 on: June 27, 2013, 03:02 AM »
Yes, it is possible, but I would not recommend it. The dictionary files are located in AppData folder if you use the portable version or in %APPDATA%\RealWorld\RWPaint if you have the application installed. The file with Polish dictionary is called 0415.po. It uses the common unix .po file format, but there are important differences. UTF8 encoding must be used.

Translated pair of strings look like:
msgid "english_string"
msgstr "translated_string"

If the string is not yet translated:
#^ 30
msgid "english_string"

The first line indicates how many times has the string been requested by the application so far. When you are translating from within the application it puts the most often used strings first.

If you have translated a string and it is not yet uploaded to the web server, it looks like:
#!
msgid "english_string"
msgstr "translated_string"

So, if you translate something in the text file, be sure to add the #! line before the pair of strings. Otherwise it will not be sent to the server and may be lost if someone else translates that string too. Also, to generate the file, you need to turn on the "Translator mode" in the application - otherwise, the untranslated strings won't be in the file.

That said, I would recommend to use the website or the built-in GUI for translation. You do NOT need to wait for next application version if you use either of those. The translated strings are added to the database instantly and you only need to refresh the dictionary within the application (for example by clicking again on language name on the Online page) to get the latest translation from the web.

The quality of the translation is not great, it is all made by volunteers and I have no feasible way to check the quality myself. I have assigned you the "language moderator" role, which gives you the right to change translations made by anyone else.

It is true that the same English word or phrase could be translated differently depending on context. But using the dictionary method, it is would not be trivial to capture the context. And so, I have accepted this limitation reasoning that it is better to have a imperfect existing translation than not having anything at all (which was the case before, when language DLLs were used and no volunteer was able to make them).
« Last Edit: June 27, 2013, 03:40 AM by vlastimil »

fenixproductions

  • Honorary Member
  • Joined in 2006
  • **
  • Posts: 1,186
    • View Profile
    • Donate to Member
Re: RealWorld Paint 2013.1
« Reply #27 on: June 27, 2013, 07:04 PM »
Darn, I missed this option somehow. Thank you for pointing this out.

It took few minutes to get translation file working properly in poEdit tool but now it should be lot easier to work with it.

apogee22

  • Participant
  • Joined in 2007
  • *
  • Posts: 15
    • View Profile
    • Donate to Member
Re: RealWorld Paint 2013.1
« Reply #28 on: September 12, 2013, 03:22 AM »
Thanks very much. Ill try it. Many old fotos need touching up!

JoTo

  • Super Honorary
  • Charter Member
  • Joined in 2005
  • ***
  • Posts: 236
    • View Profile
    • Donate to Member
Re: RealWorld Paint 2013.1
« Reply #29 on: September 12, 2013, 04:04 AM »
Hi Vlastimil,

wonderful piece of software. And i can't believe its free. I've seen much less mighty and poor programmed apps that cost $50+.

And for me Adobe Photoshop is definitely a no-go. Too pricey for the small amount of graphic work i have to do and the GUI is visually impaired unfriendly. So "NO" for me to PS. But i often need to load a psd file or whatever, and then RWP comes to help.

So RWP has definitely its place in the software scene.

Donation is on the way!
Greetings
JoTo