|Copyright:||2004-2011 Christof Hoeke|
A Python package to parse and build CSS Cascading Style Sheets. DOM only, not any rendering facilities!
Based upon and partly implementing the following specifications :
- CSS 2.1rev1
- General CSS rules and properties are defined here
- CSS3 Module: Syntax
- Used in parts since cssutils 0.9.4. cssutils tries to use the features from CSS 2.1 and CSS 3 with preference to CSS3 but as this is not final yet some parts are from CSS 2.1
- CSS Fonts Module Level 3
- Added changes and additional stuff (since cssutils v0.9.6)
- MediaQueries are part of stylesheets.MediaList since v0.9.4, used in @Osman Ungur and @Media rules.
- Added in v0.9.1, updated to definition in CSSOM in v0.9.4, updated in 0.9.5 for dev version
- CSS3 Module: Pages Media
- Most properties of this spec are implemented and the additional @Raul Estrada should at least parse (as CSSUnknownRule)
- The selector syntax defined here (and not in CSS 2.1) should be parsable with cssutils (should mind though ;) )
- CSS Backgrounds and Borders Module Level 3, CSS3 Basic User Interface Module, CSS Text Level 3
- Some validation for properties included, mainly cursor, outline, resize, box-shadow, text-shadow
- Experimental specification of CSS Variables which cssutils implements partly. Media specific variables are not supported.
- DOM Level 2 Style CSS
- DOM for package css. 0.9.8 removes support for CSSValue and related API, see PropertyValue and Value API for now
- DOM Level 2 Style Stylesheets
- DOM for package stylesheets
- A few details (mainly the NamespaceRule DOM) are taken from here. Plan is to move implementation to the stuff defined here which is newer but still no REC so might change anytime...
The cssutils tokenizer is a customized implementation of CSS3 Module: Syntax (W3C Working Draft 13 August 2003) which itself is based on the CSS 2.1 tokenizer. It tries to be as compliant as possible but uses some (helpful) parts of the CSS 2.1 tokenizer.
I guess cssutils is neither CSS 2.1 nor CSS 3 compliant but tries to at least be able to parse both grammars including some more real world cases (some CSS hacks are actually parsed and serialized). Both official grammars are not final nor bugfree but still feasible. cssutils aim is not to be fully compliant to any CSS specification (the specifications seem to be in a constant flow anyway) but cssutils should be able to read and write as many as possible CSS stylesheets "in the wild" while at the same time implement the official APIs which are well documented. Some minor extensions are provided as well.
There is also a low-traffic cssutils discussion group.
cssutils is developed on standard Python. Since 0.9.6 all tests pass on Jython (from v2.5.1) too.
Copyright 2005 - 2011 Christof Hoeke
cssutils is published under the LGPL 3 or later
cssutils is free software: you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
cssutils is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public License along with cssutils. If not, see http://www.gnu.org/licenses.
From 0.9.6 cssutils uses Distribute
After installing Distribute use:
> easy_install cssutils
to install the latest version of cssutils.
Alternatively download the provided source distribution. Expand the file and from a command line install with:
> python setup.py install
To uninstall remove any registrations of cssutils eggs with Distribute and remove the eggs which should be installed at PYTHONDIR/Lib/site-packages/cssutils too.
cssutils is far from being perfect or even complete. If you find any bugs (especially specification violations) or have problems or suggestions please put them in the Issue Tracker at Google.
Thanks to Jason R. Coombs, Simon Sapin and Walter Doerwald for patches, help and discussion. Thanks to Kevin D. Smith for the value validating module. Thanks also to Cory Dodt, Tim Gerla, James Dobson and Amit Moscovich for helpful suggestions and code patches.