Home » Eclipse Projects » Babel » Galileo release plan, and how it will fit with Babel
| Galileo release plan, and how it will fit with Babel [message #21359] |
Tue, 30 September 2008 13:02  |
Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
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
|
|
|
| Re: Galileo release plan, and how it will fit with Babel [message #21407 is a reply to message #21359] |
Mon, 06 October 2008 07:05  |
| Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
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
|
|
| |
| Re: Galileo release plan, and how it will fit with Babel [message #21433 is a reply to message #21415] |
Tue, 07 October 2008 16:45 |
| Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
Ed,
have a look at Kit lo's update:
http://www.eclipse.org/newsportal/article.php?id=196&gro up=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
>>
|
|
|
| Re: Galileo release plan, and how it will fit with Babel [message #21443 is a reply to message #21433] |
Tue, 07 October 2008 19:34 |
 Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------040800030906000204050908
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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&gro up=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
>>>
>
--------------040800030906000204050908
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Antoine,<br>
<br>
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).<br>
<blockquote><a
href="http://wiki.eclipse.org/Planning_Council/Oct_27_2008">http://wiki.eclipse.org/Planning_Council/Oct_27_2008</a></blockquote>
I expect many people would advocate and support required
externalization testing...<br>
<br>
Mailing list noise? I don't know what you're referring to. :-P<br>
<br>
<br>
Cheers,<br>
Ed<br>
<br>
<br>
Antoine Toulme wrote:
<blockquote cite="mid:gcg3ms$eji$1@build.eclipse.org" type="cite">Ed,
<br>
<br>
have a look at Kit lo's update:
<br>
<a class="moz-txt-link-freetext" href=" http://www.eclipse.org/newsportal/article.php?id=196&gro up=eclipse.technology.babel#196"> http://www.eclipse.org/newsportal/article.php?id=196&group=eclipse.technology.babel#196</a>
<br>
in particular the first paragraph where he talks about testing
hardcoded strings:
<br>
<a class="moz-txt-link-freetext" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=217339">https://bugs.eclipse.org/bugs/show_bug.cgi?id=217339</a>
<br>
<br>
The screen capture helps to understand the testing, a string is
hard-coded if it does not have the special prefix:
<br>
<a class="moz-txt-link-freetext" href="https://bugs.eclipse.org/bugs/attachment.cgi?id=113122">https://bugs.eclipse.org/bugs/attachment.cgi?id=113122</a>
<br>
<br>
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.
<br>
Plus maybe Kit or Denis would have more weight than me on this matter.
<br>
<br>
Thanks,
<br>
<br>
Antoine
<br>
<br>
Ed Merks wrote:
<br>
<blockquote type="cite">Antoine,
<br>
<br>
It sounds like a good idea. What kind of testing is involved? Probably
<br>
you should make sure the Planning Council considers this issue when
next
<br>
it meets. A cross-projects mailing list note might reach a broader
<br>
audience of the involved parties...
<br>
<br>
<br>
Antoine Toulme wrote:
<br>
<blockquote type="cite">Crossposting to foundation.
<br>
<br>
Antoine Toulme wrote:
<br>
<blockquote type="cite">Hi everyone,
<br>
<br>
I see that i18n is cited as the 16th item on the list for the Must Do's
<br>
of Babel.
<br>
<br>
I think we should come up with a set of rules applied to the release
<br>
candidates before the Galileo build is published.
<br>
<br>
I would ask that all code must have its strings externalized for RC1.
At
<br>
that time, we can test what strings are not externalized using the
<br>
recent work Kit did.
<br>
<br>
Then we freeze the code with regard to the texts used in it, and we can
<br>
start a new pass of translations that would end when Galileo is
<br>
released.
<br>
<br>
What do you think ?
<br>
<br>
Thanks,
<br>
<br>
Antoine
<br>
</blockquote>
<br>
</blockquote>
</blockquote>
<br>
</blockquote>
</body>
</html>
--------------040800030906000204050908--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| | | | |
| Re: Galileo release plan, and how it will fit with Babel [message #26193 is a reply to message #26113] |
Tue, 24 March 2009 13:12 |
| Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
Werner Keil wrote:
> One crucial dissonance I found is the HELP content.
> Nothing seems translated into any other language so far, but I guess
> this may be acceptable for Galileo??
That's because help files are xml files that don't fit into Babel. We
have a bug for this.
>
> As long as the header and footer of the help window are localized
> correctly ;-)
>
> I would personally consider it a smoothe thing if at least some of the
> key concepts like "Workbench basics" were also available in some languages.
> Does this fall within the Babel scope, or is it translated elsewhere?
You can still translate the xml file and send it to the committers so
they incorporate it to the help system. But it won't be maintained as
well as in Babel.
|
|
|
| Re: Galileo release plan, and how it will fit with Babel [message #574471 is a reply to message #21359] |
Mon, 06 October 2008 07:05 |
| Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
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
|
|
|
| Re: Galileo release plan, and how it will fit with Babel [message #574500 is a reply to message #21407] |
Mon, 06 October 2008 13:32 |
Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
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
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Galileo release plan, and how it will fit with Babel [message #574568 is a reply to message #21415] |
Tue, 07 October 2008 16:45 |
| Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
Ed,
have a look at Kit lo's update:
http://www.eclipse.org/newsportal/article.php?id=196&gro up=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
>>
|
|
|
| Re: Galileo release plan, and how it will fit with Babel [message #574590 is a reply to message #21433] |
Tue, 07 October 2008 19:34 |
Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
This is a multi-part message in MIME format.
--------------040800030906000204050908
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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&gro up=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
>>>
>
--------------040800030906000204050908
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Antoine,<br>
<br>
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).<br>
<blockquote><a
href="http://wiki.eclipse.org/Planning_Council/Oct_27_2008">http://wiki.eclipse.org/Planning_Council/Oct_27_2008</a></blockquote>
I expect many people would advocate and support required
externalization testing...<br>
<br>
Mailing list noise? I don't know what you're referring to. :-P<br>
<br>
<br>
Cheers,<br>
Ed<br>
<br>
<br>
Antoine Toulme wrote:
<blockquote cite="mid:gcg3ms$eji$1@build.eclipse.org" type="cite">Ed,
<br>
<br>
have a look at Kit lo's update:
<br>
<a class="moz-txt-link-freetext" href=" http://www.eclipse.org/newsportal/article.php?id=196&gro up=eclipse.technology.babel#196"> http://www.eclipse.org/newsportal/article.php?id=196&group=eclipse.technology.babel#196</a>
<br>
in particular the first paragraph where he talks about testing
hardcoded strings:
<br>
<a class="moz-txt-link-freetext" href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=217339">https://bugs.eclipse.org/bugs/show_bug.cgi?id=217339</a>
<br>
<br>
The screen capture helps to understand the testing, a string is
hard-coded if it does not have the special prefix:
<br>
<a class="moz-txt-link-freetext" href="https://bugs.eclipse.org/bugs/attachment.cgi?id=113122">https://bugs.eclipse.org/bugs/attachment.cgi?id=113122</a>
<br>
<br>
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.
<br>
Plus maybe Kit or Denis would have more weight than me on this matter.
<br>
<br>
Thanks,
<br>
<br>
Antoine
<br>
<br>
Ed Merks wrote:
<br>
<blockquote type="cite">Antoine,
<br>
<br>
It sounds like a good idea. What kind of testing is involved? Probably
<br>
you should make sure the Planning Council considers this issue when
next
<br>
it meets. A cross-projects mailing list note might reach a broader
<br>
audience of the involved parties...
<br>
<br>
<br>
Antoine Toulme wrote:
<br>
<blockquote type="cite">Crossposting to foundation.
<br>
<br>
Antoine Toulme wrote:
<br>
<blockquote type="cite">Hi everyone,
<br>
<br>
I see that i18n is cited as the 16th item on the list for the Must Do's
<br>
of Babel.
<br>
<br>
I think we should come up with a set of rules applied to the release
<br>
candidates before the Galileo build is published.
<br>
<br>
I would ask that all code must have its strings externalized for RC1.
At
<br>
that time, we can test what strings are not externalized using the
<br>
recent work Kit did.
<br>
<br>
Then we freeze the code with regard to the texts used in it, and we can
<br>
start a new pass of translations that would end when Galileo is
<br>
released.
<br>
<br>
What do you think ?
<br>
<br>
Thanks,
<br>
<br>
Antoine
<br>
</blockquote>
<br>
</blockquote>
</blockquote>
<br>
</blockquote>
</body>
</html>
--------------040800030906000204050908--
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| |
| Re: Galileo release plan, and how it will fit with Babel [message #575072 is a reply to message #21938] |
Tue, 21 October 2008 08:54 |
Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
Kit,
Of course history tells us that development issues will definitely come
up such that a small number of translatable strings trickle in after the
planned cutoff date. I get the impression that our processes are so
well thought out that a small number of late arrivals would be easily
handled. I notice that all these statements are should-do. Is is
possible to participate in Babel without doing at least the second
bullet? If not, perhaps that one should be first in the list and should
be a must-do...
Kit Lo wrote:
> I've proposed the following 3 Babel topics for discussion in the up
> coming Eclipse Planning Council meeting. The chair of the Planning
> Council Rich Gronback has already added Babel participation as a
> Must-Do requirement for the Galileo release, and indicated an M6
> completion date.
>
> - each Eclipse project should add the Babel Pseudo Translation Test to
> their release plan to make sure their project is properly globalized,
> with all strings externalized, and all layout problems fixed
> - each Eclipse project should define their project map files at the
> Babel Translation Server so translators around the world could help
> translating the Eclipse project
> - each Eclipse project should freeze their translatable strings at M6
> to give translators enough time for translation before project release
> date
>
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| | |
| Re: Galileo release plan, and how it will fit with Babel [message #577707 is a reply to message #26113] |
Tue, 24 March 2009 13:12 |
| Eclipse User |
|
|
|
Originally posted by: atoulme.intalio.com
Werner Keil wrote:
> One crucial dissonance I found is the HELP content.
> Nothing seems translated into any other language so far, but I guess
> this may be acceptable for Galileo??
That's because help files are xml files that don't fit into Babel. We
have a bug for this.
>
> As long as the header and footer of the help window are localized
> correctly ;-)
>
> I would personally consider it a smoothe thing if at least some of the
> key concepts like "Workbench basics" were also available in some languages.
> Does this fall within the Babel scope, or is it translated elsewhere?
You can still translate the xml file and send it to the committers so
they incorporate it to the help system. But it won't be maintained as
well as in Babel.
|
|
|
Goto Forum:
Current Time: Fri Apr 19 23:53:16 GMT 2024
Powered by FUDForum. Page generated in 0.04494 seconds |
] 
Search
Help
Register
Login
Home
