views:

208

answers:

2

In opposite to most other CSS parsers, no regular expressions are used and thus CSSTidy has full CSS2 support and a higher reliability.

I wonder why CSSTidy built their own parser and not utilized the official SAC API (which also includes support for the new CSS3)? Is there any technical or practical reason for not using SAC and writing your own parser? Infact, there're NO css tools right now that use SAC, I wonder why?

+3  A: 

The latest release of CSSTidy is July 19, 2007. I bet the SAC-API is much newer. I'd like to see someone do a PHP port of SAC-API.

anarkhos
The Java implementation download link is http://www.w3.org/2002/06/sacjava-1.3.zip — So its as old as 06.2002, no?
Nimbuz
oh, I see. Hmm... then ignore my comment.
anarkhos
the W3C Note on SAC <http://www.w3.org/TR/SAC/ > is even dated 28 July, 2000 ...
ax
+2  A: 

Tools like CSSTidy need to be able to handle the non-compliant code that shows up in the real world. Official standards implementations usually aren't very good at that.

Tom Clarkson
API doesn't help? Really? Can you please elaborate?
Nimbuz