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

[Bug 29971] [FO31] Strange sentence under "Implementation defined features" checklist

From: <bugzilla@jessica.w3.org>
Date: Tue, 01 Nov 2016 15:46:08 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29971-523-Jb4b6RqGIi@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29971

--- Comment #1 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
Actually, this happens more often:

35. ...the format token n, N, or Nn, indicating that the value of the component
is to be output by name, in lower-case, upper-case, or title-case respectively.
Components that can be output by name include (but are not limited to) months,
days of the week, timezones, and eras. If the processor cannot output these
components by name for the chosen calendar and language then it must use an
·implementation-defined· fallback representation. (See The picture string.)

36. ...indicates alphabetic or traditional numbering respectively, the default
being ·implementation-defined·. This has the same meaning as in the second
argument of fn:format-integer. (See The picture string.)

49. ...the processor may use ·implementation-defined· heuristics to determine
the likely encoding, otherwise... (See fn:unparsed-text.)

So thinking a bit about this, perhaps it is intentional.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 1 November 2016 15:46:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:58:02 UTC