Kit,
I could define the map files for BIRT 2.3.
But, I could not define the map files for
other branches due to ViewVC exception.
Thank you,
Doshiro.
From: babel-dev-bounces@xxxxxxxxxxx
[mailto:babel-dev-bounces@xxxxxxxxxxx] On
Behalf Of Kit Lo
Sent: Monday, February 11, 2008
10:42 AM
To: Babel committers mailing list
Subject: RE: [babel-dev] Eclipse
Platform SDK 3.2 translations
Doshiro-san, thanks for monitoring our mailing list!
All
you have to do is:
-
go to http://babel.eclipse.org/babel/map_files.php (you will be asked to login
with your Bugzilla ID and password)
-
select your project name and release version
-
enter the
ViewCVS download URL to map file, for example,
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.releng/maps/core.map?view=co
- click the Save button
The
map files are read nightly, and any .properties files (except build.properties)
contained in the plugins they reference will be parsed and imported into Babel, allowing the
community to translate the externalized strings.
Here
is a screen capture for reference:
Kit Lo
IBM Eclipse SDK Globalization Technical Lead
Eclipse Babel
Project Co-lead
|
"Yasuo Doshiro"
<doshiro@xxxxxxxxxxx>
Sent
by: babel-dev-bounces@xxxxxxxxxxx
02/11/2008 01:19 PM
|
Please
respond to
Babel
committers mailing list <babel-dev@xxxxxxxxxxx>
|
|
|
To
|
"Babel
committers mailing list" <babel-dev@xxxxxxxxxxx>
|
|
cc
|
|
|
Subject
|
RE: [babel-dev] Eclipse Platform SDK 3.2
translations
|
|
Kit,
If you give me an instruction how to define map files, I can
create map files for BIRT.
Thank you,
Doshiro.
From:
babel-dev-bounces@xxxxxxxxxxx [mailto:babel-dev-bounces@xxxxxxxxxxx] On Behalf Of Kit Lo
Sent: Thursday, February 07, 2008 1:38 PM
To: Babel committers mailing list
Subject: Re: [babel-dev] Eclipse Platform SDK 3.2 translations
1. Can we only import translations for projects that have map files defined
(like Eclipse Platform and CDT), and ignore all other translations until the
projects' map files are defined? I know that's more work for you :-(
2. >I'd need to define the 3.3.1 map files, import the 3.2 strings into the
3.3.1 tree (where the string names match).
I think that's the right approach. When we see obsolete strings in 3.2
that are not in 3.3, we should skip importing them.
Kit Lo
IBM Eclipse SDK Globalization Technical Lead
Eclipse Babel Project Co-lead_______________________________________________
babel-dev mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
