[Caminol10n] Camino 1.5 Norwegian

[Stefano]

2007/5/6, Markus Magnuson <markus.magnuson at gmail.com>:
>
> 6 maj 2007 kl. 22.57 skrev Erik Sørngård:
>
> > Thanks. This took care of the nibtool error message from AppleGlot.
> >
> > The two annoying strings (the caption of the preference pane "Web
> > Features", and the caption of the download window) still won't
> > translate into Norwegian.
>
> I had problems with the Web Features nib, and it turned out that the
> file Localizable.strings in that nib (which is in preference panes
> subfolder) is in little-endian utf-16, and needs to be converted to
> regular utf-16 to work.

Yeah Erik, just like Markus wrote, you need to convert the files to
the regular UTF-16 to  make them understandable by AppleGlot.
It turns out that the latest version of AppleGlot has been released
before Apple planed to make Macs with the Intel processor and some of
the latest changes on Camino has been made on a Mac Intel. This caused
some files to be encoded as little endian UTF-16, the standard format
on Mac Intel machines. AppleGlot just recognizes regular UTF-16 docs
so some of the strings to be translated will not appear in it.
To convert a file, open it with AD Viewer and save it again using your
PowerPC Mac to the same location with "File - Save As..". In the "Save
As" window, change the encoding to "Uncode (UTF-16)" if needed.
I recommend you to, before running the "Inicial Pass" on AppleGlot, to
open all the ".strings" files under the "English.lproj" folders inside
the Camino application on the folder "_NewBase" in the environment and
do the conversion process with those enconded as "Unicode (UTF-16)
little endian". You will know when a file is encoded with this type of
Unicode when a window entitled "UTF-16 for Intel platform?" appear
just before opening the file wit AD Viewer.
When you finish doing all this hard work, you may run the "Inicial Pass".

I'm looking forward on making a guide regarding those errors if those
problems don't get solved soon. I guess it won't be necessary because
it seems Apple is really close to release a newer version of AppleGlot
with this bug solved.

Stefano