to devs from a translator
This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
| to devs from a translator | Marco Ciampa | 07 Jul 18:41 |
| to devs from a translator | Alexandre Prokoudine | 07 Jul 20:20 |
| to devs from a translator | Sven Neumann | 07 Jul 20:58 |
| to devs from a translator | LightningIsMyName | 08 Jul 07:58 |
| to devs from a translator | Marco Ciampa | 08 Jul 11:19 |
| to devs from a translator | Sven Neumann | 08 Jul 23:52 |
to devs from a translator
Please differentiate more the strings.
For example the "None" string has many meanings in English that in Italian correspond to different words. Unfortunately "None" is used in many different context so it's difficoult, if not impossible, to give the translation the exact meaning that it deserve.
Please split strings more!
to devs from a translator
On 7/7/10, Marco Ciampa wrote:
Please differentiate more the strings.
For example the "None" string has many meanings in English that in Italian correspond to different words. Unfortunately "None" is used in many different context so it's difficoult, if not impossible, to give the translation the exact meaning that it deserve.
You see, you say that the problem exists, but you don't say where exactly :)
Alexandre Prokoudine http://libregraphicsworld.org
to devs from a translator
On Wed, 2010-07-07 at 18:41 +0200, Marco Ciampa wrote:
Please differentiate more the strings.
For example the "None" string has many meanings in English that in Italian correspond to different words. Unfortunately "None" is used in many different context so it's difficoult, if not impossible, to give the translation the exact meaning that it deserve.
We can easily add context to strings where necessary. The framework for this is there and it is being used. We just need the translators to tell us exactly where translation context is needed. Preferably open bug reports for this.
Sven
to devs from a translator
Hello
On Wed, Jul 7, 2010 at 9:59 PM, Sven Neumann wrote:
On Wed, 2010-07-07 at 18:41 +0200, Marco Ciampa wrote:
Please differentiate more the strings.
For example the "None" string has many meanings in English that in Italian correspond to different words. Unfortunately "None" is used in many different context so it's difficoult, if not impossible, to give the translation the exact meaning that it deserve.
We can easily add context to strings where necessary. The framework for this is there and it is being used. We just need the translators to tell us exactly where translation context is needed. Preferably open bug reports for this.
I also had this issue with translating to Hebrew, and so I recently added some context to the strings of the undo descriptions.
Marco: There is a really easy way to add these contexts - I can show you how if you'd like (or you can take a look at the patch I submitted here http://git.gnome.org/browse/gimp/commit/?id=5930b13084497d8720ac3b0c51daa0d0ffe4bdda ). Usually when translating GIMP, I discovered that's it enough to look at the source code to understand what most strings are from the name of the functions they appear in. Usually, looking at the code is enough if you know just a bit of programming (even if it's in a different programming language), usually you can manage without knowledge of how GIMP's code work.
Sven: I think this should somehow be handled for the future - what's the best place to leave a note to developers/commiters that before commiting new strings they should add some contexts for their strings? If we don't do this, we will have this problem of mis-translation continue to appear every time new strings are introduced...
~LightningIsMyName
to devs from a translator
On Thu, Jul 08, 2010 at 08:58:08AM +0300, LightningIsMyName wrote:
Hello
On Wed, Jul 7, 2010 at 9:59 PM, Sven Neumann wrote:
On Wed, 2010-07-07 at 18:41 +0200, Marco Ciampa wrote:
Please differentiate more the strings.
For example the "None" string has many meanings in English that in Italian correspond to different words. Unfortunately "None" is used in many different context so it's difficoult, if not impossible, to give the translation the exact meaning that it deserve.
We can easily add context to strings where necessary. The framework for this is there and it is being used. We just need the translators to tell us exactly where translation context is needed. Preferably open bug reports for this.
I also had this issue with translating to Hebrew, and so I recently added some context to the strings of the undo descriptions.
Marco: There is a really easy way to add these contexts - I can show you how if you'd like (or you can take a look at the patch I submitted here http://git.gnome.org/browse/gimp/commit/?id=5930b13084497d8720ac3b0c51daa0d0ffe4bdda ). Usually when translating GIMP, I discovered that's it enough to look at the source code to understand what most strings are from the name of the functions they appear in. Usually, looking at the code is enough if you know just a bit of programming (even if it's in a different programming language), usually you can manage without knowledge of how GIMP's code work.
Sven: I think this should somehow be handled for the future - what's the best place to leave a note to developers/commiters that before commiting new strings they should add some contexts for their strings? If we don't do this, we will have this problem of mis-translation continue to appear every time new strings are introduced...
~LightningIsMyName
Many thanks one example is worth a thousand words...I see that the context strings of gettext is exactly what I was looking for.
One typical example is here:
from po-plugins/it.po
#. if and how to center the image on the page
#: ../plug-ins/common/align-layers.c:423 ../plug-ins/common/align-layers.c:454
#: ../plug-ins/common/cml-explorer.c:165 ../plug-ins/common/file-ps.c:3242
#: ../plug-ins/common/file-ps.c:3254 ../plug-ins/common/file-psp.c:646
#: ../plug-ins/file-fits/fits.c:1044
#: ../plug-ins/fractal-explorer/fractal-explorer-dialogs.c:998
#: ../plug-ins/fractal-explorer/fractal-explorer-dialogs.c:1039
#: ../plug-ins/fractal-explorer/fractal-explorer-dialogs.c:1080
#: ../plug-ins/lighting/lighting-ui.c:415
#: ../plug-ins/print/print-page-layout.c:461
msgid "None"
msgstr "No"
waaaayyyy too many contexts for that string!
Example:
align-layers.c = (IT) allineamento livelli -> None = No or Nessuno (ok!) file.psp.c = (IT) compressione dati -> No or Nessuna (ok!) fractal-explorer-dialogs.c = (IT) composizione -> Nessuna or No (ok!) ....
lighting-ui.c = (IT) tipo luce -> Nessuna (no! ---> I or someonelse will add some context strings)
Now I know how to do it.
Thant you very much to pointing me to the right direction...
to devs from a translator
On Thu, 2010-07-08 at 08:58 +0300, LightningIsMyName wrote:
Sven: I think this should somehow be handled for the future - what's the best place to leave a note to developers/commiters that before commiting new strings they should add some contexts for their strings? If we don't do this, we will have this problem of mis-translation continue to appear every time new strings are introduced...
We certainly don't want to do this for any new string that is added. If you like you can add a note to README.i18n though and suggest that strings which are likely going to be troublesome should have translator context added.
Sven
