I too am interested in knowing how exactly to use the Babel PTT to satisfy
the localization should-do for DTP for the Galileo simultaneous release.
We're already good as far as getting everything into Babel (map files and so
on), but I can't find anything on the wiki or newsgroups or doing a Google
search to figure out what exactly is necessary to use the Babel PTT.
Any suggestions would be very helpful.
--Fitz
DTP PMC Lead/Connectivity sub-project lead/Enablement sub-project lead
"Víctor Roldán Betancort" <vroldan@xxxxxxxxxxxxxxxx> wrote in message
news:gri31v$pki$1@xxxxxxxxxxxxxxxxxxxx
Hi everyone,
as a member of the CDO component, we are trying to fulfill our
localization needs for the Galileo release. I'll try to expose here what
I've understood.
(Please correct me if wrong) The steps to properly prepare our project for
babel are:
1. Externalize all Strings that are subject to be shown in the UI from our
plugins (in our case, I expect only UI and Exceptions are subject to be
shown). Use JDT and PDE tooling to externalize strings.
2. Create a babel map. If I understand it correctly, this is kind of a
file that exposes which externalized Strings can be translated by the
Babel community. I saw this is done through a webapp. The first thing I
see is our project does not appear, which I understand since we are not
top level project under modeling, but rather under modeling.emf. How can
we add our component to this list? Is there anything we should do?
4. Perform PTT to see everything is fine?
How is exactly the Pseudo Translation Test performed? I believe I should
download the PTT plugin and then configure eclipse.ini to use it? Which is
the flag I should use? If I understood correctly:
a. Hard-coded strings don't have prefix
b. Externalized Strings have prefix. If the string has the prefix, what
does it exactly mean?
Question: where is the index file that maps prefix to file containing the
string?
Thanks in advance :D
Víctor.