W3C home > Mailing lists > Public > www-validator-cvs@w3.org > May 2004

[Bug 755] New: Fatal errors are always declared to be us-ascii

From: <bugzilla@wiggum.w3.org>
Date: Sat, 29 May 2004 02:26:16 +0000
To: www-validator-cvs@w3.org
Message-Id: <E1BTtY8-0000Oe-Se@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=755

           Summary: Fatal errors are always declared to be us-ascii
           Product: CSSValidator
           Version: CSS Validator
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Other
        AssignedTo: ot@w3.org
        ReportedBy: bjoern@hoehrmann.de
         QAContact: www-validator-cvs@w3.org


Fatal errors like

  % HEAD -H "Accept-Language: de" \
     http://jigsaw.w3.org/css-validator/validator

  Cache-Control: no-cache
  Connection: close
  Date: Sat, 29 May 2004 02:20:57 GMT
  Pragma: no-cache
  Server: Jigsaw/2.2.2 W3C_CSS_Validator_JFouffa/2.0
  Content-Language: en
  Content-Length: 918
  Content-Type: text/html; charset=us-ascii
  ...

always declare us-ascii encoding even though localized error messages as the 
Validator would use in this example might not be us-ascii encoded. It might be 
possible to extract the proper charset from the property files, but that does 
not work currently, see Bug #162. It might be best to switch to UTF-8 for all 
output.

The responsible code here is org.w3c.css.servlet.CssValidator.handleError().



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Friday, 28 May 2004 22:26:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:02:06 UTC