RE: New release of CSS Validator

We don't discuss in mobileOK how to determine the character encoding of a CSS file. We specifically don't discuss using the BOM for XHTML files, so I wonder if this is introducing a slight inconsistency.

Jo


> -----Original Message-----
> From: public-mobileok-checker-request@w3.org [mailto:public-mobileok-
> checker-request@w3.org] On Behalf Of Dominique Hazael-Massieux
> Sent: 13 March 2008 13:22
> To: public-mobileok-checker
> Subject: Re: New release of CSS Validator
> 
> 
> Le jeudi 13 mars 2008 à 05:32 -0400, Yves Lafon a écrit :
> > > It appears that there is now a dependency of the validator on the
> > > org.apache.velocity package, even when not using the HTML output of
> the
> > > validator:
> > >        java.lang.NoClassDefFoundError:
> org/apache/velocity/io/UnicodeInputStream
> > >        at
> org.w3c.css.css.StyleSheetParser.parseStyleElement(StyleSheetParser.java:2
> 58)
> > >        at
> org.w3c.mwi.mobileok.basic.CSSUtils.getStylesheet(CSSUtils.java:84)
> > >
> > > Can you confirm this is a new and intended dependency?
> >
> > Yes, in fact the dependency is on one class from velocity 1.5, used to
> > read the BOM in a document and set the charset parameter accordingly.
> > (see http://www.w3.org/Bugs/Public/show_bug.cgi?id=4828 )
> > It won't force you to use the whole velocity template engine, just this
> > class.
> 
> As a result, I have added velocity-1.5.jar to our lib directory
> (accompanied with its -LICENSE file), and updated the css-validator.jar
> with the new release.
> 
> Dom
> 
>

Received on Thursday, 13 March 2008 14:42:13 UTC