Update french translation file including new line 834 and new translation of 1711.
I have started translating to Brazilian Portuguese. I will post the translation file in a few days
Hello Alberto, I read on pixls.us that you changed Log Encoding into Log Tone Mapping. We must find a way to inform translators about these kind of changes, as it is impossible to check all those ~2000 lines of the default file every day!
I propose to add new/changed language strings at the end of default, with a # in front of it, or just add a new line above a string that has changed.
My apologies Paul, you are absolutely right. We need to find a mechanism that ensures the smallest overhead possible for translators. I am fine with your proposal. An alternative could be to simply write a comment in this issue, do you think that would work? Incidentally, I've just added one more key to the language file:
TP_LABMASKS_DELTAE_TOOLTIP;Select regions of similar colour\n(according to the CIELAB ΔE* metric)
I suggest that in the comment you added the line number in the default file.
Yes, that’s a good idea, just write new/added strings right here, with or without lines numbers (my editor has a search function )
Just my 2 cts: wouldn’t it be enough if the translators use a file compare/diff tool such as Meld?
This way, when the default language file is updated, you just open the new one against the older language file, and then it should be easy to locate the changed lines and to update the language file.
I don’t think that is a good idea. Translators are humans (as opposed to devs, as everybody knows…) and a program like Meld generates more confusion than that it clarifies, I’m afraid. See screenshot, it highlights all the translations as well!
In order for software to be translated in as many languages as possible, the act of translation has to be as easy as possible. That means no diff or meld or other ‘difficult’ software.
I’m a member of the Dutch Gnome translate team (I do Gimp and gThumb among others) and there we work with po files and a po editor, which is a thing made for translators. It automatically shows untranslated/new or changed entries. It’s easy like a text editor and everybody can use that.
ART and RT use plain text files, which is fine. But we need a simple way to show translators what is new or what has changed. RT places new entries at the end of the default file, with a ! in front of it. That works. If Alberto wants to place them here, that’ll work as well. In that case it’s perhaps a good idea to start the default file with a link to this discussion.
PS. I generated the Nederlands-for-ART file with a diff on the Nederlands-for-RT.
I am not at all an experimented translator. The way I process here is to stick to the same number of line between the default file and the language one. Then as Alberto always gives the line number in the commit I know where to insert the new line or where lines have to be modified. I am open to any solutions aimed to improve the work.
The last french translation file including the new line 1689
Paul, you're right, a text comparison tool is not as easy as I thought.
Though it helped me checking Serge's translation file with more recent default file (as it took me several days to go through all the translation strings, and the default file was updated during the process).
But now for simple modifications, the solutions you and Serge propose are easier.
Alberto ,there is something I do not clearly understand. On the master branch the version is 1.2.10 and in new-texture-boost 1.2.15. You announce that you have merged the branches, are the feature of 1.2.15 included in the master and what about the translation file ? thanks for your help so that I translated the updated version.
I have not merged anything yet (I have merged master in new-texture-boost, not the other way round), but I plan to do it over the weekend.
Regarding the version numbers, they are computed automatically and very unreliable (as written in the output of the compilation command). You should use the commit hash (the Commit: entry in AboutThisBuild.txt), that’s the only reliable info for development builds.
The last french translation file. Many thanks to D. Catalina for introducing french translated lines. I slightly modified the line order to kept a perfect match between the line number of default file and the french one.
Ready for 1.3 ?
Here is the french translation for the tootip for Inspector.
We are almost ready for 1.3. There are only a couple of glitches that I’d like to fix, but they are quite minor. In the meantime, here is a list of the new/changed entries in the language files (ping @Paul Matthijsse and @Felipe Simoes )
Typo in the default language file on line 1266: PREFERENCES_OVERLAY_FILENAMES_FILMSTRIP;Overlay filenames on thumbnails in the editor pannel, should be panel.
thanks! The typo was recently fixed (a few hours ago)
line 2008 is not translated:
TP_RAW_IMAGENUM_TOOLTIP;Some raw files consist of several sub-images (Pentax/Sony Pixel Shift, Pentax 3-in-1 HDR, Canon Dual Pixel, Fuji EXR).\n\nWhen using any demosaicing method other than Pixel Shift, this selects which sub-image is used.\n\nWhen using the Pixel Shift demosaicing method on a Pixel Shift raw, all sub-images are used, and this selects which sub-image should be used for moving parts.
Noticed it while working on the RT “Nederlands” file (and comparing it to the ART version)…
Hello, I commented that line out because as far as I can tell, it is not used in Art. Perhaps I oversee something?
I did not realize that you used > to comment it out, I thought it might be left there by a diff as > is used in diff output… Sorry for the confusion.
No problem. For the first translation of Art (the beta) I indeed diff’ed the art default language file with the rawtherapee default language file. Many strings from RT were not used in Art, so I commented them out and checked if that did harm to the Dutch translation. Which was not the case according to me. But of course I can always oversee things.
Good luck with the translation of RT, some sections are quite difficult to attack (especially those made by Jacques Desmis).
If you have any question regarding your translation, feel free to contact me. As you can see in the RT default translation file, I did that for some years. Now I do Art, Gimp and gThumb.
Thanks for the info Paul!
I feel like writing something to check 1) if a translation is used and 2) if a translation is missing, by scanning all sources for the M(XXX) pattern. I’ll let you know if I find missing or unused translations. But don’t hold your breath yet.
Hi Alberto, here is a french translation for version 18.104.22.168. Although all lines are identical to the default file, translations are missing for the TP WB using the camera preset scrolling menu. Where would be my problem ?
Many thanks for your suggestions.
Hi Serge, those strings are currently not translated, they are hardcoded in wbpresets.json. I still haven't found a good/efficient way of managing their translation unfortunately (the json file is automatically generated)
One thing Alberto. Using White Balance - Camera presets, I can't find those strings in the dropdown list (direct sunlight, shade, etc.) in the default language file of ART. Are they hard-coded perhaps?
Thanks for the translation!
I can't find those strings in the dropdown list (direct sunlight, shade, etc.) in the default language file of ART.
I missed that one, so hard-coded indeed. I thought that already, as all those entries are lowercase, which isn’t the style of RT/ART.
more than hardcoded, they are automatically generated. I haven’t come up yet with a good way of translating those…
Hi Alberto, Thanks for the translation of line 239. I would like to ask you what do you mean with “range”. In french I would have said “Gamme” that means the extension of the scale in EV, it could be also translated by “Etendue” what do you think ? Sincerely SM
Feel free to post a new translation. I was merely using a dictionary and tried to pick what made sense to me…but of course I might be totally wrong
Range in this context means the interval of values between min and max, so according to your explanation gamme seems appropriate
Hi Alberto, the latest french file up to version 22.214.171.124
I am ready to release 1.5.4. If you want to update translations, here are the keys that changed wrt. 1.5.3. I’ll probably do this over the weekend.
HISTORY_MSG_DISTORTION_AUTO;Auto Distortion Correction HISTORY_MSG_FLATFIELD_EMBEDDED;Flat-field embedded TP_FLATFIELD_EMBEDDED;Embedded in metadata TP_LABMASKS_DRAWNMASK_ADD_BOUNDED_TOOLTIP;Add the brush mask on top of the other masks, but only within the active area mask