|[cross-project-issues-dev] Re: [babel-dev] Identifying (and externalising) untranslated strings|
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
- 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?
Senior Software Engineer
Engineering - Internationalisation
babel-dev mailing list
Back to the top