Re: Localization good practices

Hi Philippe,

[email protected] wrote:
> 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 ?

Just wondering ... it looked like that while while reading some emails, 
but I don't know that method, I thought I was missing something.


>  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 ?

I also know as the only safe method the overriding method - it is what 
GWorkspace does.
Sooner or later I want to bring StepSync into that direction. It is not 
that hard, but has the pain that every element needs to be referenceable 
with an IBOutlet.

E.g. often things lie NSBoxes are just instantiated in Gorm or Buttons 
that have only actions can just be connected with IBActions and have no 
corresponding explicit ivars.

> 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.

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?

Riccardo