./www/ruby-crass, CSS parser based on the CSS Syntax Level 3 spec

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 1.0.3, Package name: ruby24-crass-1.0.3, Maintainer: pkgsrc-users

Crass is a Ruby CSS parser that's fully compliant with the
CSS Syntax Level 3 specification.

Features
--------

* Pure Ruby, with no runtime dependencies other than Ruby 1.9.x or higher.

* Tokenizes and parses CSS according to the rules defined in the 14 November
2014 editor's draft of the [CSS Syntax Level 3][css] specification.

* Extremely tolerant of broken or invalid CSS. If a browser can handle it, Crass
should be able to handle it too.

* Optionally includes comments in the token stream.

* Optionally preserves certain CSS hacks, such as the IE "*" hack, which would
otherwise be discarded according to CSS3 tokenizing rules.

* Capable of serializing the parse tree back to CSS while maintaining all
original whitespace, comments, and indentation.


Required to run:
[lang/ruby24-base]

Required to build:
[pkgtools/cwrappers]

Master sites:

SHA1: e9f8499a8e0e84d93c9f3d5513b89dc0bfbf2d88
RMD160: c9de07bff4c5515a8a9adeffa1f26af6528d7821
Filesize: 90 KB

Version history: (Expand)


CVS history: (Expand)


   2018-05-06 04:25:43 by Takahiro Kambe | Files touched by this commit (2) | Package updated
Log message:
www/ruby-crass: update to 1.0.3

1.0.3 (2017-11-13)
------------------

* Added support for frozen string literals. (#3 - @flavorjones)
   2018-03-13 17:10:50 by Takahiro Kambe | Files touched by this commit (4)
Log message:
www/ruby-crass: add version 1.0.2 package

Crass is a Ruby CSS parser that's fully compliant with the
CSS Syntax Level 3 specification.

Features
--------

* Pure Ruby, with no runtime dependencies other than Ruby 1.9.x or higher.

* Tokenizes and parses CSS according to the rules defined in the 14 November
  2014 editor's draft of the [CSS Syntax Level 3][css] specification.

* Extremely tolerant of broken or invalid CSS. If a browser can handle it, Crass
  should be able to handle it too.

* Optionally includes comments in the token stream.

* Optionally preserves certain CSS hacks, such as the IE "*" hack, \ 
which would
  otherwise be discarded according to CSS3 tokenizing rules.

* Capable of serializing the parse tree back to CSS while maintaining all
  original whitespace, comments, and indentation.