Yuri D'Elia wrote:
> In article 
> <[EMAIL PROTECTED]>,
>  "MacArthur, Ian (SELEX GALILEO, UK)" 
>  <[EMAIL PROTECTED]> wrote:
> 
>> I have several apps, from various sources and various toolkits, that
>> attempt this. At the last count (and I counted twice, to be sure)
>> exactly 0 of them managed this. Every single one had some text that
>> didn't fit it's widget, or widgets that were forced too far out of
>> position, or some other basic usability failing.
>>
>> To be fair, most sort of managed, more or less, most of the time, so it
>> all still "works". But it doesn't actually work "right".
> 
> I agree.
> 
> I'm wondering how localization actually works with Cocoa/OSX (never used 
> the IBuilder). Widgets support automatic or relative positioning, but 
> I've not noticed an huge amount of GUIs done using either. Most of the 
> windows are either empty (toolbar and content only) or completely fixed, 
> like most of the preference panels.
> 
> Setting up localization strings there has the same problems as FLTK, as 
> far as I can tell. The nice thing about bundles however, is that you can 
> have different GUIs for different locales, so I presume this the way it 
> is actually used when needed, though I don't see how this is "efficient" 
> to maintain in the long term.
> 
> Has anyone experience on this?

Nibs are localized in the application bundle, so you'll see a .lproj
subdirectory in the bundle's Resources directory for each language
that is supported.

As for efficiency, it is faster to load a localized nib than to load
a generic nib, localize all of the strings in the nib, and then re-
layout the controls.  You pay (somewhat) as the developer to keep
the nibs synchronized, but there *are* translation tools that can
merge nib changes and the separate file approach allows for
localized layouts which otherwise require more complex run-time
layout engines and localized attributes.

-- 
______________________________________________________________________
Michael Sweet, Easy Software Products           mike at easysw dot com
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to