[Bug 26549] New: [f+o 3.1] Non-ascii character in spec rendered incorrectly

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 26549] New: [f+o 3.1] Non-ascii character in spec rendered incorrectly

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26549

            Bug ID: 26549
           Summary: [f+o 3.1] Non-ascii character in spec rendered
                    incorrectly
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators 3.1
          Assignee: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]

In section 5.5 of the 3.1 specification at
http://www.w3.org/TR/xpath-functions-31, the character "a umlaut" in "Jäger" is
incorrectly rendered as "square root, section sign" in my browser. It is
correctly rendered in the 3.0 version of the spec.

--
You are receiving this mail because:
You are the QA Contact for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug 26549] [f+o 3.1] Non-ascii character in spec rendered incorrectly

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26549

--- Comment #1 from Michael Kay <[hidden email]> ---
Another corruption occurs in 9.8.4.1 (format-date) where the width modifier
syntax appears as

   ","  min-width ("-" max-width)?

and another in 9.8.5 where the German for 31st is given as

einunddreißigste

However, pi and theta appear correctly in the specs of math functions, and the
Islamic and Thai dates in 9.8.5 also appear correct, as do the Arabic-Indic
digits and the Italian ordinal indicators in 4.6.1.

--
You are receiving this mail because:
You are the QA Contact for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug 26549] [f+o 3.1] Non-ascii character in spec rendered incorrectly

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26549

--- Comment #2 from Michael Kay <[hidden email]> ---
Looking at the CVS log, it seems the corruptions go back to the first version
of the 3.1 xpath-functions.xml, which was apparently copied incorrectly from
the 3.0 version of the document. (But it's hard to be sure, because my CVS
client has a compare utility that is itself not showing these characters
correctly). The corruptions moreover appear to be in some sense cumulative, in
that different CVS commits show different variations of the character.

Probably the best solution is to replace all non-ASCII characters in the source
by character references or entity references, to reduce the risk of further
corruption if someone uses a non-UTF-8 editor to edit the file.

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

Reply | Threaded
Open this post in threaded view
|

[Bug 26549] [f+o 3.1] Non-ascii character in spec rendered incorrectly

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26549

--- Comment #3 from Michael Kay <[hidden email]> ---
The non-ASCII characters in the xpath-functions.xml file are in the following
sections:

namespace-prefixes - mdash, OK.
defining-decimal-format - per mille sign - seems OK
uca-collations - wrong (strength) A=a=√Ç=√¢, should be A=a=Â=â
substring.functions - Jaeger should contain "a umlaut" (several times)
date-time-duration-conformance - mdash, codepoint 8212 (twice), in deleted
text.
date-picture-string -    ","  min-width ("-" max-width)? should use NBSP
formatting-timezones - uses NBSP twice, written as entity ref, OK.
date-time-examples - German example einunddreißigste Dezember is wrong, but
the Hebrew, Arabic and Thai examples look OK.
casting-to-float - wrong, √ó should be <=
casting-to-double - wrong, √ó should be <=
ISO10967 - mdash, OK.
ISO15924 - mdash, OK.
ISO15924_register - mdash, OK.

--
You are receiving this mail because:
You are the QA Contact for the bug.
Reply | Threaded
Open this post in threaded view
|

[Bug 26549] [f+o 3.1] Non-ascii character in spec rendered incorrectly

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26549

--- Comment #4 from Michael Kay <[hidden email]> ---
Correction, the symbol in casting-to-float and -double should be a
multiplication sign.

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

Reply | Threaded
Open this post in threaded view
|

[Bug 26549] [f+o 3.1] Non-ascii character in spec rendered incorrectly

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26549

Michael Kay <[hidden email]> changed:

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

--- Comment #5 from Michael Kay <[hidden email]> ---
These problems have been fixed by use of entities defined in the DTD.

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