Hello On Wed, Jul 7, 2010 at 9:59 PM, Sven Neumann <sven@xxxxxxxx> 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 _______________________________________________ Gimp-developer mailing list Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
