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

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26549

--- Comment #2 from Michael Kay <mike@saxonica.com> ---
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.

Received on Sunday, 10 August 2014 19:48:41 UTC