Riccardo Mottola wrote: > That's a matter of taste, Renaissance still exists, is supported and I > think you can even make pieces in gorm and renaissance in the same > project. > But how should it make translation easier here?
Gorm files are "fixed" interfaces, so consider this example, a window with two NSButton's: ,---------------------, | Start downloading? | | | | ,----, ,--------, | | | OK | | Cancel | | | `----' `--------' | `---------------------' All fits nicely in English but since the window size and the buttons' sizes are fixed, strings get truncated in a Bulgarian translation: Започване на изтеглянето? Добре Отхвърляне No matter how "carefully", as Richard said, the developer designs the interface, it would inevitably fail for a plethora of languages (and will look ugly in English if you leave too much space to accommodate other languages). No developer in the world can predict how the UI will look (or must look) when translated to a foreign language; there are too many of them with too many specifics. Toolkits like GTK or GNUstep+Renaissance will automatically expand the UI element (a.k.a widget) so that it fits the localized string, and will recalculate the sizes of the parent widgets accordingly. So shipping additional .gorm files for translations if something that is quite often necessary. And as a translator I feel terrorized when I have to edit .gorm files. Futhermore, things go havoc when the developer changes the English .gorm files in a new version but the translated .gorm files are not updated. NeXT's IB files are an abomination that GNUstep replicated.
