Re: How to do multilanguage support
Re: How to do multilanguage support
- Subject: Re: How to do multilanguage support
- From: JC Helary <email@hidden>
- Date: Thu, 2 Feb 2006 22:24:18 +0900
When i searching about the localization, i just saw the tool named
"appleGlot". I hope we can also use this tool for translations....
Can any one used this tool... if so can you shed some light...
--Elango C
Appleglot is a tool that will help you manage incremental
localization projects. It is good for _big_ things.
Basically you create a translation project, put your app in a folder
(don't remember the name but the manual explains that pretty well,
except that the info is hidden in a late chapter...) and parse it
with AppleGlot.
The result will be a pseudo bilingual .wg file (.wg is a format
similar to xliff, ie. it is an xml based translation memory format).
This .wg file has to be edited in a corresponding editor (there are a
few: AppleTrans, LocFactoryEditor Lite etc) or simple in a text
editor (change the mode to xml to have some sort of syntax coloring).
The edition is basically: put the corresponding translation below the
original (English ?) language. So you'll have a localizer who'll put
your file in English-French, another who'll do the English-Japanese
version etc.
Once the .wg file is edited, put the thing back in AppleGlot, push
the magic button and AppleGlot creates the corresponding .lproject
files in your bundle. You can test the localization by launching it
is the relevant environment (see System->Preferences->International,
language pane, put the desired language on top of the list and launch
the app).
The guy who makes LocFactoryEditor also has a few mini tools that do
the same thing as AppleGlot but it is easier (like drag&drop).
If you have RTF files to localize things get more complicated. You
can use Heartsome's localization suite (not expensive, Java app,
excelent support) or convert your file to OpenDocument with
OpenOffice and localize with OmegaT, a free and open source Java tool
for translators (not specifically for localizations but includes
support for Java .properties files).
If you have HTML files, OmegaT is the best choice, just create a
project, feed OmegaT the files (with any directory structure) in the /
source/ folder, open the project and have the guys translate. The
html will be integrally respected and the directory structure will be
reproduced as in /source/.
Basically that's pretty much all you need to get a full localization
of your apps.
Summary:
AppleGlot for the app GUI strings to be processed as a single .wg file
LocFactoryEditor to edit the .wg file by adding the translated strings
Heartsome or OpenOffice+OmegaT for RTF files
OmegaT for HTML files.
I have no idea how the Localization suite works and by looking at
their site it looks pretty nice. So you just need to choose your
translators and give them the files they need.
JC Helary
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden