Antoine,
I see. This is totally cool! I'd suggest adding this to the
planning council wiki's agenda for their face-to-face meeting (which
unfortunately I can't attend).
http://wiki.eclipse.org/Planning_Council/Oct_27_2008
I expect many people would advocate and support required
externalization testing...
Mailing list noise? I don't know what you're referring to. :-P
Cheers,
Ed
Antoine Toulme wrote:
Ed,
have a look at Kit lo's update:
http://www.eclipse.org/newsportal/article.php?id=196&group=eclipse.technology.babel#196
in particular the first paragraph where he talks about testing
hardcoded strings:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=217339
The screen capture helps to understand the testing, a string is
hard-coded if it does not have the special prefix:
https://bugs.eclipse.org/bugs/attachment.cgi?id=113122
I would stage carefully a move to mail cross-project as there seems
there is quite a lot of noise on the mailing lists those days.
Plus maybe Kit or Denis would have more weight than me on this matter.
Thanks,
Antoine
Ed Merks wrote:
Antoine,
It sounds like a good idea. What kind of testing is involved? Probably
you should make sure the Planning Council considers this issue when
next
it meets. A cross-projects mailing list note might reach a broader
audience of the involved parties...
Antoine Toulme wrote:
Crossposting to foundation.
Antoine Toulme wrote:
Hi everyone,
I see that i18n is cited as the 16th item on the list for the Must Do's
of Babel.
I think we should come up with a set of rules applied to the release
candidates before the Galileo build is published.
I would ask that all code must have its strings externalized for RC1.
At
that time, we can test what strings are not externalized using the
recent work Kit did.
Then we freeze the code with regard to the texts used in it, and we can
start a new pass of translations that would end when Galileo is
released.
What do you think ?
Thanks,
Antoine
|