Le 3 juil. 06 à 23:45 Soir, Theodore H. Smith a écrit:
From: Arnaud Nicolet <[EMAIL PROTECTED]>
Date: Mon, 3 Jul 2006 20:15:51 +0200
Thanks, an interesting way to achieve it (this would be an
enjoyable =20
part to do).
But I see 2 problems:
1: I'll lose the benefit of the "disable/reorder" languages of
MacOS =20
X (for example, in the info window of the bundle, where you can =20
deactivate the languages, and the "International" system
preferences =20
where you can reorder the preferred languages).
True, you'll lose reordering. I don't see why disablement is a
problem, though. You'll need some way to grab the OS X's prefered
language. Surely MBS can help you there? You are using it already??
I think I can use it for the main (first) language. But if the main
language is not handled by my app, I'll have to figure out the second
(third, etc.) until I find one that I know.
But I can also put a popupmenu in the prefs window (where the user
selects a language).
2: Since bundles aren't so known in Win32, anyone will clearly be =20
able to modify those files (well, like on Mac, but it is a bit
hidden =20=
there).
Not really a problem though? Anyone can edit your app anyhow...
Indeed. But my first idea was to make a localization only for MacOS
X. For Win32, I'd keep a single language.
On MacOS X, to edit the Localized files, bundles have to be open
using "Show package contents", which some (like my mother) know
nothing about.
Thanks._______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
