* Make multi-line-string-body non-greedy
* Don't require string-character after quotes in multiline strings
* Prevent accidentally consuming triple quotes in multi-line-string-body
* Add test cases
since Kadlet is not maintained, I proposed adding KdlSharp for v2 users in a [discussion](https://github.com/kdl-org/kdl/discussions/550)
I also added the requirements in the note (from KdlSharp README.MD). I abbreviated them to fit in the width of the table.
I hope the style is fine
Just moving the `- disallowed-keyword-identifiers` up to the parent production so it catches all the ident productions, to make any similar mistakes impossible.
generally in {A,E}BNF, if one literal is a prefix of another,
the longer one is specified first, otherwise the shorter one
will always match, either causing a spurious error or a parsing
ambiguity, unless using a parser architecture which automatically
resolved local ambiguities by collecting alternatives.
this is something the rest of the KDL and KQL specs do well,
but it seems this case slipped through the cracks.
* Exclude hex above max Unicode Scalar Value
simplify surrogate regex to use ranges
* allow leading 0s, but still limit max length to 6
* Add explicit regex-set rules to hex unicode
document {1,3} ranges
* add space-separators between sets
* Make test fail *only* for length limits
Previously it failed due to specifying a codepoint past max *as well*, obscuring the intended fail condition.
---------
Co-authored-by: Tab Atkins Jr. <jackalmage@gmail.com>
Fixes: https://github.com/kdl-org/kdl/issues/461
* Initial conversion to Internet-Draft.
* Setup repository for draft-marchan-kdl2 using https://github.com/martinthomson/i-d-template
* Remove unnecessary changes.
* Tweak source to make the I-D build.
* Fix zkat's name. Guess at their preferred initials.
* Separate links where linking text equals the anchor.
This works around https://github.com/cabo/kramdown-rfc/issues/249.
* Replace horizontal rules with subsections.
RFCXML v3 doesn't include horizontal rules.
* Use ~~~kdl instead of `` for strings with significant whitespace.
That compiles to <sourcecode> which preserves sequences of spaces.
* Give breadcrumbs to the RFC format definitions.
* Point contributors to https://author-tools.ietf.org/.
For if installing the dependencies is inconvenient.
* Separate a code block from adjacent text.
* Remove a workflow that overwrites customized files.
* Remove the 'archive' workflow.
* Use "Term ({{term}})" uniformly instead of just when the term matches the anchor.
* Fix the instructions for preserving the RFCXML.
* Remove the default copyright notice until the spec is relicensed.
* Take the IETF licensing details out of CONTRIBUTING.md.
* Support empty multiline strings
Per <https://github.com/kdl-org/kdl/discussions/481>, the grammar doesn't actually allow the first and last newline in a multiline string to be the same (indicating an empty string). This looks like the minimal fix for it.
* Add tests for empty multilines
* remove accidental newline