summaryrefslogtreecommitdiffstats
path: root/scripts/scrape-spec.js
Commit message (Collapse)AuthorAgeFilesLines
* Update build scripts and dataMathias Bynens2016-04-041-7/+10
| | | | The spec changed the order of some listings here and there.
* Update spec URLsMathias Bynens2014-09-151-1/+1
|
* Minor cleanupMathias Bynens2014-08-311-1/+1
|
* Split scripts into separate files per exported valueMathias Bynens2014-05-241-1/+8
|
* Scrape the spec for more dataMathias Bynens2014-05-231-34/+59
| | | | | | Let’s also scrape the spec for the list of code points for symbols that cause parse errors when they occur in raw HTML source. Note: `invalid-character-reference-code-points.json` is identical to `invalid-raw-code-points.json` except U+000D (CR) is not included in the latter, because lone CR are converted to LF before tokenization. http://whatwg.org/html/parsing.html#preprocessing-the-input-stream
* Fix logic error in `scrape-spec.js`Mathias Bynens2013-08-041-7/+12
|
* data/decode-map-overrides: Filter keys mapping to themselvesMathias Bynens2013-08-021-16/+22
| | | | | | @fb55 pointed out that `decode-map-overrides.json` can be simplified: any code points that map to their respective symbols can be removed if they are included in `invalid-code-points.json`. Good catch! Closes #13.
* Tweak script that scrapes the specMathias Bynens2013-08-021-7/+6
|
* Update dependenciesMathias Bynens2013-07-271-1/+1
|
* Make sure code points are stored as numbersMathias Bynens2013-07-011-9/+14
|
* Generate an array of all code points that trigger a parse errorMathias Bynens2013-07-011-0/+99
Ref. #9.