Re: Localization of GNUstep strings
p.o.rous...@free.fr wrote: Selon p.o.rous...@free.fr: Selon Fred Kiefer fredkie...@gmx.de: [snip] cd gui/Resources make_strings -L German ../Source/*.m Before every release of gui we should update these files and add the missing new translations. Fred PS: I find the way you have to write the non-ASCII characters a bit clumsy, but I didn't want to switch to UTF-8. Clumsy looks like an understatment :o) Seriously though, is utf-8 an option ? I'm willing to start a french translation and I would prefer something easier for all accentuated caracters. Here's my first take on a French.lproj. Answering to myself, yes utf-8 is an option and that's what I used. You just have to had the 3 bytes marker at the beginning of the file (and that's ugly imho). Gorm panels of gnustep-gui (and maybe something else) need to be translated too I guess. Can you give me a hint on how to do that ? Thank you for starting on this. There are quite a lot of non-translated strings left in the file. Should I commit it anyway or are you planing to add these as well? You always should run the make_strings command multiple times. For me it found additional strings during these extra runs. It will also sort the newly translated entries. Translating the panels is easy, just copy the directory Panels/English.lproj and then load the panels in it one by one into Gorm, translate the texts and do any other changes your language requires and store them. Maybe I should do that for German to show the idea. Ignore the gmodel files in the Panels directory, these are unused and need to be replaced by gorm files. Yes, we really should implement all panels via gorm or NIB files now. I would prefer NIB files as key value coding allows for easier extension. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Localization of GNUstep strings
Le lundi 02 mars 2009 à 13:56 +0100, Fred Kiefer a écrit : p.o.rous...@free.fr wrote: Here's my first take on a French.lproj. Answering to myself, yes utf-8 is an option and that's what I used. You just have to had the 3 bytes marker at the beginning of the file (and that's ugly imho). Gorm panels of gnustep-gui (and maybe something else) need to be translated too I guess. Can you give me a hint on how to do that ? Thank you for starting on this. There are quite a lot of non-translated strings left in the file. Should I commit it anyway or are you planing to add these as well? Yes, I plan to translate all strings when I get time but I wanted to know if I was on the right track before continuing. Is the utf-8 encoding is ok with you ? You always should run the make_strings command multiple times. For me it found additional strings during these extra runs. It will also sort the newly translated entries. Ok, good to know. Translating the panels is easy, just copy the directory Panels/English.lproj and then load the panels in it one by one into Gorm, translate the texts and do any other changes your language requires and store them. Maybe I should do that for German to show the idea. Ignore the gmodel files in the Panels directory, these are unused and need to be replaced by gorm files. Yes, we really should implement all panels via gorm or NIB files now. I would prefer NIB files as key value coding allows for easier extension. That's bad. Even if tranlating the strings is the only modification to be done, you have to copy the whole gorm file ? Why can't it use Localizable.strings ? Philippe ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Localization of GNUstep strings
I just updated the GNUstep gui localization files for English and German. While doing so I noticed a few issues with our current localization handling. One was in base, where the switch to output missing localization values would always write out nil, not very helpful while looking for the missing keys. The other problem was harder. In gui we override the _() and NSLocalizedString macros to use the gui bundle to resolve the localization. This is needed and great, but needs the include of GSGuiPrivate.h in the gui source file to work and this was missing for a lot of your files where localization had only been added recently. We also have a process issue here. All the localization files were last updated 2006 and for many important languages we don't even have localizations. It would be great, if all the non-English native speakers could adopt there own language and create translations for it. Creating and updating these files is really easy. All I had to do was: cd gui/Resources make_strings -L German ../Source/*.m Before every release of gui we should update these files and add the missing new translations. Fred PS: I find the way you have to write the non-ASCII characters a bit clumsy, but I didn't want to switch to UTF-8. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Localization of GNUstep strings
Selon Fred Kiefer fredkie...@gmx.de: [snip] cd gui/Resources make_strings -L German ../Source/*.m Before every release of gui we should update these files and add the missing new translations. Fred PS: I find the way you have to write the non-ASCII characters a bit clumsy, but I didn't want to switch to UTF-8. Clumsy looks like an understatment :o) Seriously though, is utf-8 an option ? I'm willing to start a french translation and I would prefer something easier for all accentuated caracters. Philippe ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: Localization of GNUstep strings
Selon p.o.rous...@free.fr: Selon Fred Kiefer fredkie...@gmx.de: [snip] cd gui/Resources make_strings -L German ../Source/*.m Before every release of gui we should update these files and add the missing new translations. Fred PS: I find the way you have to write the non-ASCII characters a bit clumsy, but I didn't want to switch to UTF-8. Clumsy looks like an understatment :o) Seriously though, is utf-8 an option ? I'm willing to start a french translation and I would prefer something easier for all accentuated caracters. Here's my first take on a French.lproj. Answering to myself, yes utf-8 is an option and that's what I used. You just have to had the 3 bytes marker at the beginning of the file (and that's ugly imho). Gorm panels of gnustep-gui (and maybe something else) need to be translated too I guess. Can you give me a hint on how to do that ? Philippe Localizable.strings Description: Binary data ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
