[Caminol10n] Using iLocalize

Markus Amalthea Magnuson markus.magnuson at gmail.com
Fri Mar 7 00:59:17 PST 2008


I've had problems with iLocalize, someone with more experience from
the application might be able to help me.

1. When I created the initial project and imported by a localized copy
of Camino, both "sv.lproj" and "Swedish.lproj" was created in the
resulting copy. Even worse, when I updated the project with the latest
release, the new files were only placed in one of these lproj folders.
Luckily I was able to fix this by renaming the language (Project >
Rename "sv"…) and then renaming it again. I renamed to "sv_SE" and
then back to "sv" and everything was back in order.

2. iLocalize won't pick up the string changes from bug 410110
(https://bugzilla.mozilla.org/show_bug.cgi?id=410110), I only get
error messages about missing keys and not used keys. Isn't that the
purpose of incremental localization, to be able to detect and import
new strings and remove old ones? I am sure iLocalize is capable of
this, I just haven't figured out how to do it. Someone else who knows?

As soon as we can get all the quirks sorted out, and have some good
tutorials, I am all for a switch to iLocalize. It's a relief not
having to think about encodings and missing files deep down in the
hierarchies. It even found an untranslated string for me that
AppleGlot had missed.
-- 
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


More information about the Caminol10n mailing list