Hi Steven,
Check the current draft for XLIFF 2.0 and you will see that we don’t plan to use subflows inside a segment. A mechanism for representing subflows in their own units/segments has been designed.
Some time ago we voted against having an equivalent to the old <sub> element in XLIFF 2.0
Regards,
Rodolfo
--
Rodolfo M. Raya rmraya@maxprograms.com
Maxprograms http://www.maxprograms.com
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Steven R Loomis
Sent: Tuesday, January 10, 2012 3:49 PM
To: Yves Savourel
Cc: xliff@lists.oasis-open.org
Subject: RE: [xliff] Plural forms and XLIFF
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