Guy who asked Patrick to make a french version of each gorm file here... > Just my opinion: > > I do not believe that there is a single 'good practice' here. The > differences in the lengths of phrases in different languages can mean > that a layout that suits one language may not suit another language, so > sometimes an app developer may want to provide multiple gorm files. The > standard resource loading mechanism supports this, picking the correct > gorm file for the currently selected locale in preference to any > unlocalised file. > > I think an app developer should always provide a gorm file (or > equivalent xib etc) which will be used if there is no specifically > localised file for the current locale. > > While locale specific files may provide the best possible UI, it's a lot > more work for the developer/maintainer of an app, so it's optional. > Carefully designed interfaces can generally be made to work with a small > amount of text and be designed so that the necessary text will look good > in all (or almost all) languages.
Are you saying that UI displayed thanks to a gorm file should be translated automagically if the strings are correctly translated in Localizable.strings files ? >From what I saw it only works if every string present in the gorm file is overwritten manually in the code, which is a pain to do. If I'm wrong (and in this case I'm sorry Patrick), what is the right way to translate gorm UIs with Localizable.strings files ? By the way, this whole UI translation subject is one the reasons I should have used Renaissance library to build SimpleAgenda, it is way cleaner in my opinion. Simple text files, easily handled in svn, git or whatever, no compatibility problems because you edited your UI with a too recent version of Gorm, simple and nice autolayout etc. I really don't understand why Renaissance hasn't become the preferred way to build UIs in GNUstep applications. Philippe
