- From: <bugzilla@jessica.w3.org>
- Date: Fri, 24 Jan 2014 16:16:30 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24384
Bug ID: 24384
Summary: Typos and link issues under fn:unparsed-text-lines(),
and relation with fn:unparsed-text-available()
Product: XPath / XQuery / XSLT
Version: Proposed Recommendation
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: XPath 3.0
Assignee: jonathan.robie@gmail.com
Reporter: abel.braaksma@xs4all.nl
QA Contact: public-qt-comments@w3.org
In the third paragraph of fn:unparsed-text-lines() [1], the text "The result is
a thus a sequence of strings", should probably read "The result is thus a
sequence of strings".
The links under the expressions in the second paragraph extend to the whole
expressions, as opposed to only the individual functions (tokenize,
unparsed-text etc). Perhaps this is a limitation of the build script, however,
if it is, I think it is more readable without the links.
Furthermore, since the function is now deterministic (as opposed to
non-deterministic from the streaming discussion a while ago), I think it is
good to allow fn:unparsed-text-available() to also apply to
fn:unparsed-text-lines(). Currently, there's no such relation between those
functions.
[1] http://www.w3.org/TR/xpath-functions-30/#func-unparsed-text-lines
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 24 January 2014 16:16:49 UTC