- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 03 Sep 2004 01:07:13 +0000
- To: www-validator-cvs@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=861 Summary: &is_xml() and $File->{Type} use deprecated conf/type.cfg Product: Validator Version: 0.7.0 Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P2 Component: Types Registry AssignedTo: link@pobox.com ReportedBy: link@pobox.com QAContact: www-validator-cvs@w3.org The &is_foo() (e.g. &is_xml()) functions, and the $File->{Type} attribute, make use of the data (and accompanying logic) from the deprecated conf/type.cfg. This should be ripped out and replaced with something making use of the new Types Registry, but it needs to be done carefully since this logic is hairy and determines XML vs. SGML mode using heuristics and DWIMery. It's likely the Type Registry needs to be unraveled to provide a Content-Type -> Parse Mode (XML vs. SGML) mapping, or to compute it on the fly. Possibly this wants a third "UNDETERMINED" state for ambigious cases like "text/html" where we may be parsing XHTML or MathML (which need XML mode and not SGML mode as the Content-Type alone would indicate). ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
Received on Friday, 3 September 2004 01:07:13 UTC