-
Notifications
You must be signed in to change notification settings - Fork 200
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Move all remaining fixText() stuff (macros, curly aposes, and em dashes) into the parser. Manual test changes are now 100% expected. * Remove stray print() * Properly revert an unmatched macro to [] characters. * No need to check for a comment start, since that's already been parsed. * Fix the regex * Don't eagerly lowercase macros on parse. Recursively replace HTML-parsed macros. * Remove the zwsp from the em-dash, as browsers already allow a break opportunity there anyway. * Pipe previous token into the context, so apostrophe handling can be done after an element's end tag. * Pull out the 'turn metadata into properly-parsed text' into a function, invoke it on all the macros that need it. * Add parseTitle() for generating <title>-safe content, and use it (and parseText()) in more metadata. Add a printNodeTree() debugging tool. Rebase some tests, whose changes should all be known-good. * Actually create Doctype nodes, so I don't accidentally kick docs into quirks mode. * Rebase all the tests that look expected so far. * Whoops, restore header/footer addition. * Handle lists in HTML trees. * Correctly handle otherMetadata so it doesn't double-wrap with <dd> * update docs * Correct the line numbers downstream when I remove a newline while handling em-dashes. * rebase tests * Rebase tests that have expected changes * Switch parser functions to taking a ParseConfig * Whoops, give Note: paragraphs a line number. * Make multi-line start tags emit IncrementLineCountChar charaters, which increment the offset for Lines and are removed from the output. Switch em-dash line correction to use them. Store macro start/end chars as named constants, too. * Rather than eagerly adding ilccs, only generate them *on request when stringifying* if the reported line span (endLine - line) is different from the actual line span * Rebase tests with fixed line numbers * Add line-count test to exercise the errors more directly. * Add a test for accidental raw text line count * Parse char references in text (and properly escape text). * Instead of stripping comments for Markdown, replace them with a recognizable comment string. Then, if they're the only thing on the line, Markdown can just drop them. * rebase tests * Rebase more tests. Don't output escaped text, but do output char refs as the charref, not the underlying character. Explicitly handle whole-line comments in datablocks, now that I don't strip them early. * lint * Regen docs * rebase one final test
- Loading branch information
Showing
305 changed files
with
2,963 additions
and
2,188 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.