{"issue":{"title":"The Lucius parser isn't CSS compliant","user":{"login":"dflemstr","id":56029,"url":"https://api.github.com/users/dflemstr","avatar_url":"https://secure.gravatar.com/avatar/202ecb437d8bbd442d093a3a35c67a04?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"202ecb437d8bbd442d093a3a35c67a04"},"created_at":"2011-12-26T06:04:42Z","milestone":null,"labels":[],"state":"open","updated_at":"2011-12-28T08:18:00Z","id":2656957,"closed_at":null,"html_url":"https://github.com/yesodweb/hamlet/issues/34","pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"body":"The CSS syntax uses [a strict syntax specification](http://www.w3.org/TR/CSS2/syndata.html). The Lucius parser is very different from the standard parser, and there are numerous issues with it that lead to errors when parsing CSS files, especially when it comes to escape sequences.\r\n\r\nSince the CSS specification describes the full syntax lexeme tree in detail, it wouldn't be difficult to develop a compliant parser.","number":34,"url":"https://api.github.com/repos/yesodweb/hamlet/issues/34","comments":7,"assignee":null},"comment":{"user":{"login":"snoyberg","id":49415,"url":"https://api.github.com/users/snoyberg","avatar_url":"https://secure.gravatar.com/avatar/71596bb1ca3ba3aa4400c3f407baec9f?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"71596bb1ca3ba3aa4400c3f407baec9f"},"created_at":"2011-12-28T08:18:00Z","updated_at":"2011-12-28T08:18:00Z","id":3288945,"body":"If that's the case, I'll hold off on any patches for #31 and #32 and wait to see your new parser. I'm looking forward to it, thanks!","url":"https://api.github.com/repos/yesodweb/hamlet/issues/comments/3288945"},"action":"created"}