Skip to content

Language names, again #318

Closed
Closed
@cabo

Description

@cabo

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:
https://www.w3.org/TR/2014/REC-html5-20141028/infrastructure.html#set-of-space-separated-tokens

So language-русский is as valid as is language-c++ or language-asn.1.
This is not theoretical: It comes up in
https://tools.ietf.org/html/draft-iab-xml2rfc-03#section-2.48.4
which will soon be a standard that kramdown-rfc2629 is targeting.

Is there a reason the syntax for languages in fenced code blocks is restricted?
Shouldn't it be [^\s]+?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions