Get rid of (prefix|postfix)@noparse RBNF variants

Description

Deleted Component: other

In the last CLDR release, John removed the (prefix|postfix)@noparse variants of Arabic RBNF due to the inherent testing problems. The other languages didn't get their @noparse variants removed, like Hebrew and Maltese. These @noparse variants existed to address the possibility that they may be used in a sentence where the number moves around. Positionally variant numbers should '''not''' be handled at the RBNF level. They can only be handled at the MessageFormat level in order to get the spacing correct in the entire sentence.

We should get rid of the remaining variants.

It looks like the problem appeared because the LDML conversion tool stopped handling @noparse correctly. Rather than fix the tool, the undesirable data should be removed.

xpath

None

locale

None

Activity

Show:
TracBot
May 10, 2019, 3:52 AM
Trac Comment description.1 by kent.karlsson14@0885cc00c95d6cd9—2012-11-19T01:13:45.266Z

Replying to in

In the last CLDR release, John removed the (prefix|postfix)@noparse variants of Arabic RBNF due to the inherent testing problems. The other languages didn't get their @noparse variants removed, like Hebrew and Maltese. These @noparse variants existed to address the possibility that they may be used in a sentence where the number moves around. Positionally variant numbers should '''not''' be handled at the RBNF level. They can only be handled at the MessageFormat level in order to get the spacing correct in the entire sentence.

 

We should get rid of the remaining variants.

 

It looks like the problem appeared because the LDML conversion tool stopped handling @noparse correctly. Rather than fix the tool, the undesirable data should be removed.

Except that that would be the wrong thing to do (i.e the data is not undesirable...). In particular for Irish (and possibly other Celtic languages too), where some numbers are spelled out BOTH with a part before the noun AND a part after the noun. And there are not just a few exceptions that are like this: for N (the natural numbers) there is an infinite number of such numbers in Irish (ga). (Not sure if this phenomenon will turn up in some other languages too, like Semitic languages when vetted more thoroughly.)

Because of this I designed it as "-prefix(part)" and "-postfix(part)", knowing that the parts by themselves cannot roundtrip. Yes, there is an issue with spaces, but then that should be solved by looking for empty strings, or collapsing multiple spaces to a single space. (Actually, for the current ga.xml (Irish) RBNF rules, the additional space is included in the postfix part (which thus should be output without an external space before its result).

TracBot
May 10, 2019, 3:52 AM
Trac Comment 2 by —2012-11-30T07:48:15.348Z

#5473 will handle ga.xml to differentiate between the format and standalone formats. The numbers are split around a noun. The Semitic languages are not split. They completely move around the noun. So a format number type does not help with making message formatting any easier for Semitic languages.

Priority

minor

Assignee

George Rhoten

Reporter

George Rhoten

Reviewer

John Emmons

Labels

None

Components

None

Fix versions

Phase

None