Correction, the related bug is 260013 :BIRT 2.3.1
Translation for 6 languages in group 1
From: Xiaoying Gu
Sent: 2009年2月5日 17:22
To: For developers on the BIRT project; Sean Flanigan
Subject: RE: [birt-dev] Re: Re: [babel-dev] Identifying (and
externalising) untranslated strings
The BIRT language pack in Babel is 2.3.0 release, which is quite
out of date. So the Babel pseudo langpacks which generate on the fly was out of
date too.
Actually these string have been externalized in BIRT 2.3.1
release already.
Please refer bug 238688. When it gets
resolved, these string will be externalized in Babel pseudo langpacks
Thanks,
Xiaoying
From: birt-dev-bounces@xxxxxxxxxxx
[mailto:birt-dev-bounces@xxxxxxxxxxx] On Behalf Of Scott Rosenbaum
Sent: 2009年1月19日 22:50
To: Sean Flanigan; For developers on the BIRT project
Subject: [birt-dev] Re: Re: [babel-dev] Identifying (and externalising)
untranslated strings
Sean,
Could you please log a bug in Bugzilla?
Scott Rosenbaum
Sean Flanigan wrote:
Apologies for the dev-spam, but I finished going through all the
Preferences nodes, and found a few buried more deeply:
WTP:
* Web Services/Axis2 Preferences
and contents of this node (both tabs)
* Web/JavaServer Faces Tools (and subtree: FacesConfig Editor,
Libraries, Validation, Views, JSP Tag Registry)
preference node names
and all node contents
BIRT:
* Report Design/Bidirectional Properties
and contents
As with my previous list, these strings have apparently been hard-coded
in English [as of the Ganymede-SR1 release]. Please, externalise your
strings! As Antoine said, ask babel-dev if you need help.
Thanks!
Sean.
Antoine Toulme wrote:
I am adding the cross-project list in CC.
Committers, if you find an unexternalized string in the list below is
part of your plugin, please act on it. Please do not reply to
cross-project, please reply to babel-dev if you have an idea to make
this easier or need help.
For now I don't see a better way of dealing with this problem.
Thanks for reading, and thanks Sean for bringing this to our attention.
Antoine
On Wed, Jan 14, 2009 at 10:54 PM, Sean Flanigan <sflaniga@xxxxxxxxxx
<mailto:sflaniga@xxxxxxxxxx>> wrote:
I'm testing the Babel pseudo langpacks [editA: the pseudo langpacks
are just the english strings prefixed with a number to identify
them] with eclipse-jee-ganymede-SR1
[plus JBoss Tools pseudo langpacks], and ending up with a fair number of
unexternalised strings. For instance, in Preferences, these category
names are coming up in plain English:
- Agent Controller
- Data Management
- Install/Update
- JPA
- Profiling and Logging
- Remote Systems
- Tasks (Mylyn)
- Test (TPTP)
- Usage Data Collector (Mylyn?)
- XML (Webtools?)
In some cases, I can hazard a guess as to which project provides that
Prefs page. In others, two minutes of research, or someone more
knowledgable, should identify the project easily enough. But that's
still pretty coarse-grained.
Anyone know of any shortcuts for identifying the exact source of a
string, other than grepping the relevant projects' source trees for the
string in question, and hoping it's unique?
Any AOP tricks that log a stack trace when creating SWT objects?
Perhaps an SWT option which provides tooltips identifing the plugin
which created a GUI control?
Or is it just a matter of running the Externalize Strings wizard on the
relevant project(s), and seeing what pops out?
Regards
--
Sean Flanigan
