xliff message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: RE: [xliff] Plural forms and XLIFF
- From: Steven R Loomis <srloomis@us.ibm.com>
- To: Yves Savourel <ysavourel@enlaso.com>
- Date: Tue, 10 Jan 2012 09:48:34 -0800
In the ICU implementation of plurals, ICU docs do not recommend using substrings (subflows) but separate translated elements. In the ICU version of ChoiceFormat, ChoiceFormat is officially deprecated. http://userguide.icu-project.org/formatparse/messages#TOC-Complex-Argument-Types
-s
Yves Savourel ---01/10/2012 09:29:05 AM---Hi Rodolfo, > The example you gave is not good for
From: Yves Savourel <ysavourel@enlaso.com>
To: <xliff@lists.oasis-open.org>,
Date: 01/10/2012 09:29 AM
Subject: RE: [xliff] Plural forms and XLIFF
Sent by: <xliff@lists.oasis-open.org>
Hi Rodolfo,
> The example you gave is not good for
> considering plural forms.
Yes, PO plural forms are different, but ChoiceFormat is about plural forms too (http://docs.oracle.com/javase/tutorial/i18n/format/choiceFormat.html).
And, I agree, it is also about sub-flows.
The question the SC has is: How would one represent this and does the inline codes need more than the simple subflows attribute to handle it? (or should one even uses sub-flows in this case? Maybe that makes thing just more complicated than they need to be).
Cheers,
-ys
---------------------------------------------------------------------
To unsubscribe, e-mail: xliff-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: xliff-help@lists.oasis-open.org
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]