[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| 
[dsdp-tm-dev] FW: [cross-project-issues-dev] Re: [babel-dev]	Identifying (andexternalising) untranslated strings
 | 
Hi Dave,
 
can you check whether the "Remote Systems" Preferences 
Category is externalized,
and if not create a bug for externalizing 
it?
 
thanks,
--
Martin Oberhuber, Senior Member of Technical 
Staff, Wind River
Target Management Project 
Lead, DSDP PMC Member
 
 
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> 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
Senior Software Engineer
Engineering - 
  Internationalisation
Red 
  Hat
_______________________________________________
babel-dev 
  mailing list
babel-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/babel-dev
 
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev