W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2016

[Bug 29615] roman and max-width year

From: <bugzilla@jessica.w3.org>
Date: Mon, 09 May 2016 18:10:45 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29615-523-IJbnO815pG@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29615

Liam R E Quin <liam@w3.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |liam@w3.org

--- Comment #4 from Liam R E Quin <liam@w3.org> ---
On the whole people working with Roman numerals and fixed-width fields are in
for a hard time, and will probably use string processing to do what they need.
It seems specialist enough that I've no clue how to predict a "majority" use
case.

Josh's result - apply the width in decimal before conversion - and Benito's -
apply the width in characters after conversion - both seem plausible and I
don't see any reason to prefer one over the other in general.

Benito, when you opened this bug you didn't say that anything was wrong, nor
what goes wrong, nor what you think ought to happen. Is anything wrong with the
spec here?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 9 May 2016 18:10:47 UTC

This archive was generated by hypermail 2.3.1 : Monday, 9 May 2016 18:10:48 UTC