You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Kevin Menard <ni...@gmail.com> on 2009/02/02 01:20:48 UTC
New i18n strings
What's the general policy on adding i18n strings? E.g., I'd like to
add a new one for TAP5-151, but I'm only going to be able to provide
an English translation to start.
Should I keep the issue open until all translations are in? Should I
open a new issue requesting that string to be translated? Or is there
some other procedure to follow?
--
Thanks,
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: New i18n strings
Posted by Massimo Lusetti <ml...@gmail.com>.
On Mon, Feb 2, 2009 at 9:37 PM, Howard Lewis Ship <hl...@gmail.com> wrote:
> I think add it, and add a new issue requesting translations. The new
> issue can be broken into tasks per supported language. As it annoys
> people, they'll provide translations :-)
I'll handle Italian's one.
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: New i18n strings
Posted by Ulrich Stärk <ul...@spielviel.de>.
I could take care of german translations.
Howard Lewis Ship schrieb:
> I think add it, and add a new issue requesting translations. The new
> issue can be broken into tasks per supported language. As it annoys
> people, they'll provide translations :-)
>
> On Sun, Feb 1, 2009 at 4:20 PM, Kevin Menard <ni...@gmail.com> wrote:
>> What's the general policy on adding i18n strings? E.g., I'd like to
>> add a new one for TAP5-151, but I'm only going to be able to provide
>> an English translation to start.
>>
>> Should I keep the issue open until all translations are in? Should I
>> open a new issue requesting that string to be translated? Or is there
>> some other procedure to follow?
>>
>> --
>> Thanks,
>> Kevin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: New i18n strings
Posted by Kevin Menard <ni...@gmail.com>.
Okay, thanks for the clarification. I'll summarily close the issue.
--
Kevin
On Tue, Feb 3, 2009 at 11:54 AM, Andreas Andreou <an...@di.uoa.gr> wrote:
> Framework messages were not translated in T3 & T4 either so I
> guess developers are ok with english.
>
> Of course, if someone wants to add translations, he can just create an issue..
> so, Kevin, i feel you dont have to create an issue for translations yourself, if
> it's just about framework messages (the way Ulrich just defined them)
>
>
> On Tue, Feb 3, 2009 at 11:12 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
>> I just had a look at StructureStrings.properties and it appears that there
>> is no translation whatsoever. The question is, should we really start to
>> translate framework messages, i.e. messages that aren't presented to the
>> user, into other languages? One could argue that a programmer should have
>> enough english language skills to understand those...
>>
>> Uli
>>
>> Howard Lewis Ship schrieb:
>>>
>>> I think add it, and add a new issue requesting translations. The new
>>> issue can be broken into tasks per supported language. As it annoys
>>> people, they'll provide translations :-)
>>>
>>> On Sun, Feb 1, 2009 at 4:20 PM, Kevin Menard <ni...@gmail.com> wrote:
>>>>
>>>> What's the general policy on adding i18n strings? E.g., I'd like to
>>>> add a new one for TAP5-151, but I'm only going to be able to provide
>>>> an English translation to start.
>>>>
>>>> Should I keep the issue open until all translations are in? Should I
>>>> open a new issue requesting that string to be translated? Or is there
>>>> some other procedure to follow?
>>>>
>>>> --
>>>> Thanks,
>>>> Kevin
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
> --
> Andreas Andreou - andyhot@apache.org - http://blog.andyhot.gr
> Tapestry / Tacos developer
> Open Source / JEE Consulting
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: New i18n strings
Posted by Andreas Andreou <an...@di.uoa.gr>.
Framework messages were not translated in T3 & T4 either so I
guess developers are ok with english.
Of course, if someone wants to add translations, he can just create an issue..
so, Kevin, i feel you dont have to create an issue for translations yourself, if
it's just about framework messages (the way Ulrich just defined them)
On Tue, Feb 3, 2009 at 11:12 AM, Ulrich Stärk <ul...@spielviel.de> wrote:
> I just had a look at StructureStrings.properties and it appears that there
> is no translation whatsoever. The question is, should we really start to
> translate framework messages, i.e. messages that aren't presented to the
> user, into other languages? One could argue that a programmer should have
> enough english language skills to understand those...
>
> Uli
>
> Howard Lewis Ship schrieb:
>>
>> I think add it, and add a new issue requesting translations. The new
>> issue can be broken into tasks per supported language. As it annoys
>> people, they'll provide translations :-)
>>
>> On Sun, Feb 1, 2009 at 4:20 PM, Kevin Menard <ni...@gmail.com> wrote:
>>>
>>> What's the general policy on adding i18n strings? E.g., I'd like to
>>> add a new one for TAP5-151, but I'm only going to be able to provide
>>> an English translation to start.
>>>
>>> Should I keep the issue open until all translations are in? Should I
>>> open a new issue requesting that string to be translated? Or is there
>>> some other procedure to follow?
>>>
>>> --
>>> Thanks,
>>> Kevin
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
>>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Andreas Andreou - andyhot@apache.org - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: New i18n strings
Posted by Ulrich Stärk <ul...@spielviel.de>.
I just had a look at StructureStrings.properties and it appears that
there is no translation whatsoever. The question is, should we really
start to translate framework messages, i.e. messages that aren't
presented to the user, into other languages? One could argue that a
programmer should have enough english language skills to understand those...
Uli
Howard Lewis Ship schrieb:
> I think add it, and add a new issue requesting translations. The new
> issue can be broken into tasks per supported language. As it annoys
> people, they'll provide translations :-)
>
> On Sun, Feb 1, 2009 at 4:20 PM, Kevin Menard <ni...@gmail.com> wrote:
>> What's the general policy on adding i18n strings? E.g., I'd like to
>> add a new one for TAP5-151, but I'm only going to be able to provide
>> an English translation to start.
>>
>> Should I keep the issue open until all translations are in? Should I
>> open a new issue requesting that string to be translated? Or is there
>> some other procedure to follow?
>>
>> --
>> Thanks,
>> Kevin
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: New i18n strings
Posted by Howard Lewis Ship <hl...@gmail.com>.
I think add it, and add a new issue requesting translations. The new
issue can be broken into tasks per supported language. As it annoys
people, they'll provide translations :-)
On Sun, Feb 1, 2009 at 4:20 PM, Kevin Menard <ni...@gmail.com> wrote:
> What's the general policy on adding i18n strings? E.g., I'd like to
> add a new one for TAP5-151, but I'm only going to be able to provide
> an English translation to start.
>
> Should I keep the issue open until all translations are in? Should I
> open a new issue requesting that string to be translated? Or is there
> some other procedure to follow?
>
> --
> Thanks,
> Kevin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
Howard M. Lewis Ship
Creator Apache Tapestry and Apache HiveMind
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org