- From: <bugzilla@jessica.w3.org>
- Date: Sat, 23 Nov 2013 16:22:40 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20275
Abel Braaksma <abel.braaksma@xs4all.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |abel.braaksma@xs4all.nl
--- Comment #2 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
There seems to be a fix out for Mercurial in the form of an extension that
should be installed on the serverside. The particular files with non-ASCII
characters will have to be submitted again to fix the issue.
This is not a Windows, or Linux issue per se. It's caused by the choice of the
Mercurial developers. For instance, on Windows they use the non-Unicode file
API functions, which results in this mess, on Linux there are other issues. On
their Encoding information page, they state that the best solution is either to
have all filenames in ASCII-only, or to make sure clients and servers run on
the same system (windows server, then only windows clients, linux server, then
only linux clients etc). See [2].
For us, that's all bad news. It may be that the fix works, but I doubt whether
W3C can, or will install it. The plugin is not supported by Mercurial and is
still in beta.
My suggestion is that we add a feature to create a file, of which the contents
can be inlined, which becomes part of the prerequisites of a test. From what
I've read, that seems to be the only sure-fire way of fixing this.
[1] http://mercurial.selenic.com/wiki/FixUtf8Extension
[2] http://mercurial.selenic.com/wiki/EncodingStrategy
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 23 November 2013 16:22:42 UTC