[Caminol10n] Using iLocalize

[Markus Amalthea Magnuson]

On Thu, Mar 6, 2008 at 1:59 AM, Stefano <bwstefano at gmail.com> wrote:

> Hi everyone!
>  So... I'm fed up with AppleGlot/AD Viewer and since J.J. Enser
>  mentioned iLocalize as an alternative localization tool I looked for
>  that app to see how it works, etc. It fits us like a glove! The app is
>  easy to use and prevents errors on translating other app. Moreover, it
>  is available in 9 different languages so almost everyone will be able
>  to work with the language that feels more comfortable. Not only that
>  but iLocalize is also free for open source projects, like Camino. I
>  used it to translate Camino to Portuguese and everything went perfect.
>  Now I will send the application to a reviewer and in a couple of weeks
>  I'm going to send it for the list.
>
>  One issue iLocalize pointed out is relative to the file "Camino.app/
>  Contents/Frameworks/Sparkle.framework/Versions/A/Resources/
>  SUStatus.nib". Since it's not inside a .lproj folder, it has not been
>  translated by iLocalize and, I think, will not be localized by any
>  other application such as AppleGlot. Should this be filed as a bug?
>
>  If Camino team decides to use iLocalize as its default localisation
>  app I'm volunteering myself to write tutorials about it, just like
>  Marcello Testi did for AppleGlot and Package Maker.
>  Stefano

I haven't had a chance to try out iLocalize myself, but I've heard
it's good. I am also fed up with all the AppleGlot trouble and we
should really consider changing the default localization environment.
It is important that we come up with a simple series of steps to
migrate an already translated copy of Camino to iLocalize.

I will try out iLocalize as soon as possible.
-- 
http://konstochvanligasaker.se
http://nattlek.se

"Life... is like a grapefruit. It's orange and squishy, and has a few
pips in it, and some folks have half a one for breakfast."
 – Douglas Adams