I'm sorry this is coming up again and again, but language names need to be even more flexible.
In the end, they turn up in an HTML5 class name, and the syntax for class names is extremely flexible:
Is there a reason the syntax for languages in fenced code blocks is restricted?
The text was updated successfully, but these errors were encountered:
common mark seems to agree with русский:
But indeed few other implementations do. Hmm.
(Note that I would require a space before the
@cabo Thanks for bringing this up.
In the kramdown specification I did exactly specify of what characters an ID name may be specified but didn't do the same for class names.
Keeping that in mind not allowing any character in class names would actually be a bug. However, the two characters I would not include are the dot and hash sign so as to make chaining class and ID names in attribute lists still possible.
Any thoughts on this?
And what do you mean by this:
…ntax This change modifies how kramdown handles class names that are defined by using the special shortcut syntax in attribute lists or when adding a language name to a fenced code block. * When defining a language name for a fenced code block, any non-whitespace character except the question mark is accepted. The question mark separates the language name itself from URL-like options. * In attribute lists a class name may be defined by using any non-whitespace character except the dot and hash characters since those are used for chaining together ID and class names without whitespace. Fixes #318
Just tried it -- great!
(My comment about requiring a space was that maybe
should not be recognized as a code block start. But then, the
(If you really need a
Looking forward for a release, so I can start referencing the new version from kramdown-rfc2629.