- From: Olivier Thereaux via cvs-syncmail <cvsmail@w3.org>
- Date: Mon, 28 Apr 2008 03:42:46 +0000
- To: www-validator-cvs@w3.org
Update of /sources/public/validator/share/templates/en_US
In directory hutz:/tmp/cvs-serv14629/share/templates/en_US
Modified Files:
warnings.tmpl
Log Message:
Trying to solve the headache of the default fallback character encoding,
when different specs suggest different encodings, and we try to promote utf-8
as the best practice. This patch tried to go around the issue by trying, in sequence,
a fallback of utf8, win-1252, then iso-8859-1 - in sequence.
Index: warnings.tmpl
===================================================================
RCS file: /sources/public/validator/share/templates/en_US/warnings.tmpl,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -d -r1.41 -r1.42
--- warnings.tmpl 13 Mar 2008 17:16:20 -0000 1.41
+++ warnings.tmpl 28 Apr 2008 03:42:44 -0000 1.42
@@ -72,6 +72,11 @@
encoding was used to read the content and attempt to perform the validation,
but this is likely to fail for all non-trivial documents.
</p>
+ <TMPL_IF NAME="W04_also_tried">
+ <p>Before defaulting to <code><TMPL_IF NAME="W04_charset"><TMPL_VAR NAME="W04_charset" ESCAPE="HTML"><TMPL_ELSE>UTF-8</TMPL_IF></code>
+ the validator also tried to read the content with the following encoding(s), without success:
+ <code><TMPL_VAR NAME="W04_also_tried" ESCAPE="HTML"></code>.</p>
+ </TMPL_IF>
</TMPL_IF>
<TMPL_IF NAME="opt_verbose">
<p>The sources used to find encoding information include:</p>
Received on Monday, 28 April 2008 03:43:18 UTC