[Bug 27618] [XSLT30] Defining Decimal Formats Permits Only Single Characters [I18N-ISSUE-398]


--- Comment #2 from Michael Kay <mike@saxonica.com> ---
(For those who don't know, 20E3 is a "combining enclosing keycap". So this
would allow you to format a number with each digit in a box that looks like a
key on a keyboard.)

Initial reaction: horror. Why is a digit in bold or italic the same character,
but a digit in a rectangular box with rounded corners a different character?
Surely this should be done at the level of choosing a font for the digits?

(Mind you, the same is true for a digit in a circle, which isn't even a
modifier, it's a completely separate character. What a mess.)

But if they've done it, they've done it, and we can't change it.

A difficulty here is that we use one property in the decimal-format to indicate
a set of ten strings used to represent digits. Using 0 to represent 0,1,2,3...9
works algorithmically because the Unicode sequences are contiguous. Using *0*
to represent *0*, *1*, *2*, ... gets more problematical. Is the rule that the
string must contain exactly one digit character? Or that it must contain a
digit followed optionally by modifiers?

The rules for grouping positions also become more complicated. Are we counting
digits or characters?

I'm inclined to think that the requirement is sufficiently specialized that we
can leave people to handle it by post-processing the formatted number using the
replace() function.

You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 23 January 2015 09:56:13 UTC