W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2014

[Bug 24384] [FO30] Typos and link issues under fn:unparsed-text-lines(), and relation with fn:unparsed-text-available()

From: <bugzilla@jessica.w3.org>
Date: Wed, 19 Feb 2014 09:06:25 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-24384-523-J6H6dgwg1H@http.www.w3.org/Bugs/Public/>

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Michael Kay <mike@saxonica.com> ---
Discussed by the WG, closed with the following action:

1. "is a thus a". Fixed in both 3.0 and 3.1.

2. The generation of links to functions is automated and I agree it's very
clumsy. However, it's been unchanged for a long time (since pre-2.0) and
there's no immediate urgency, so not fixing this right now.

3. We believe that unparsed-text-available() does indeed apply to
unparsed-text-lines(). The linkage is there, but is indirect: the specification
of unparsed-text-lines makes clear that it fails under exactly the same
circumstances as unparsed-text, and these are exactly the circumstances under
which unparsed-text-available returns false. I have added a statement to this
effect as a Note in both 3.0 and 3.1:

"Since the function <function>unparsed-text-lines</function> succeeds or fails
under exactly the same circumstances as <function>unparsed-text</function>, the
<function>unparsed-text-availabl</function> function may equally be used to
test whether a call on <function>unparsed-text-lines</function> would succeed."

4. The mismatched parentheses in the code example have been fixed (in 3.0 and

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 19 February 2014 09:06:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:46 UTC