Hello,
I've asked this question on StackOverflow the other day, but the topic
seems more complex, so I'll repeat the question here.
I'm introducing translations to an existing Catalyst project. One of
requirements is to use standard gettext .po file format, since we want
to reuse all the existing
On Sat, Jan 31, 2009 at 8:29 AM, Nikolai Prokoschenko
wrote:
> Hello,
>
> I've asked this question on StackOverflow the other day, but the topic
> seems more complex, so I'll repeat the question here.
>
> I'm introducing translations to an existing Catalyst project. One of
> requirements is to use
On Sat, Jan 31, 2009 at 8:29 AM, Nikolai Prokoschenko
b. is wrong semantically, since plural form count is different in
different languages and the position of a word can differ depending on
the number (this is one reason why gnu recommends translating complete
sentences)
I didn't know that. Do
On Sun, Feb 1, 2009 at 12:42 AM, Octavian Rasnita wrote:
>> On Sat, Jan 31, 2009 at 8:29 AM, Nikolai Prokoschenko
>>>
>>> b. is wrong semantically, since plural form count is different in
>>> different languages and the position of a word can differ depending on
>>> the number (this is one reason
Hello,
>>> b. is wrong semantically, since plural form count is different in
>>> different languages and the position of a word can differ depending on
>>> the number (this is one reason why gnu recommends translating complete
>>> sentences)
>
> I didn't know that. Do you say that in some language
In data 31 gennaio 2009 alle ore 17:29:39, Nikolai Prokoschenko
ha scritto:
Locale::Maketext::Lexicon, which C::P::I18n bases on, doesn't support
standard plural forms.
I worked on implementing i18n/l10n for a fairly big non-catalyst
web site, and that's based on Locale::Maketext.
When I r
On 02/02/2009, at 5:04 AM, J. Shirley wrote:
On Sun, Feb 1, 2009 at 12:42 AM, Octavian Rasnita
wrote:
On Sat, Jan 31, 2009 at 8:29 AM, Nikolai Prokoschenko
b. is wrong semantically, since plural form count is different in
different languages and the position of a word can differ
dependin
On 2/1/09 3:31 PM, Cosimo Streppone wrote:
> In data 31 gennaio 2009 alle ore 17:29:39, Nikolai Prokoschenko
>> An example: if I wanted to translate the string
>> "I have $x apples" I would write using gettext: ngettext("I have %d
>> apple", "I have %d apples", $x). Thus xgettext would produce:
>
From: "J. Shirley"
Most east-Asian languages don't have the same concept of plurals. You
don't add the "s", so it would just be "I have 1 apple" or "I have 10
apple".
This is not an issue, because for the japanese translation, the string could
be something like:
"I have [quant,_1,apple,app
John Siracusa wrote:
I believe some languages have a different form for "dual" as well.
That is correct. My native language (Slovenian) is one of them.
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/ca
From: "Kieren Diment"
In indonesian, to pluralise you just say the word twice, or in writing
put a 2 after it.
I have two apples:
Saya ada dua appel appel.
or:
Saya ada dua appel2
"Saya ada [quant,_1,appel,appel appel]."
But it doesn't do a perfect translation this way, because instead of
On Sun, Feb 1, 2009 at 1:27 PM, Octavian Rasnita wrote:
> From: "Kieren Diment"
>>
>> In indonesian, to pluralise you just say the word twice, or in writing put
>> a 2 after it.
>>
>> I have two apples:
>> Saya ada dua appel appel.
>> or:
>> Saya ada dua appel2
>>
>
> "Saya ada [quant,_1,appel,ap
From: "Felix Antonius Wilhelm Ostmann"
>i run into the same problem with german phrases
> [quant,_1,message has,messages have] been sent.
>
> but in german:
>
> singular: Es wurde 1 Nachricht gesendet.
> plural: Es wurden 10 Nachrichten gesendet.
>
> So i cant build that with normal quant ...
i run into the same problem with german phrases
[quant,_1,message has,messages have] been sent.
but in german:
singular: Es wurde 1 Nachricht gesendet.
plural: Es wurden 10 Nachrichten gesendet.
So i cant build that with normal quant ... and i was thinking about a
quantf :)
Es [quantf,_1
14 matches
Mail list logo