Home » General (non-technical) » Eclipse Foundation » Re: Galileo release plan, and how it will fit with Babel
Re: Galileo release plan, and how it will fit with Babel [message #56251] |
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 #56288 is a reply to message #56268] |
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 #56300 is a reply to message #56288] |
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/
|
|
| | | |
Goto Forum:
Current Time: Fri Apr 19 09:13:14 GMT 2024
Powered by FUDForum. Page generated in 0.02125 seconds
|