Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spec doesn't state whether fifth and successive chars in delimited block markers must match fourth char #145

Open
scouten opened this issue Oct 28, 2024 · 0 comments
Labels
spec clarity AsciiDoc language specification is unclear

Comments

@scouten
Copy link
Owner

scouten commented Oct 28, 2024

In Summary of structural containers, the spec shows the initial (typically four) characters of the delimited block (i.e. ==== for an example block).

In the subsequent section Nesting blocks, it says:

When nesting a delimited block that uses the same structural container, it’s necessary to vary the length of the delimiter lines …

It does not say whether the extra characters used to alter the length can be arbitrary or must match the last specified character.

In other words, would ====xyz be valid as an example block delimiter or only ==== plus any number of = characters?

Working assumption

The extra characters must match the last character specified in the delimiter.

@scouten scouten added the spec clarity AsciiDoc language specification is unclear label Oct 28, 2024
scouten added a commit that referenced this issue Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec clarity AsciiDoc language specification is unclear
Projects
None yet
Development

No branches or pull requests

1 participant