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

Support namespaces in tag names #341

Closed
ioquatix opened this issue May 19, 2020 · 7 comments
Closed

Support namespaces in tag names #341

ioquatix opened this issue May 19, 2020 · 7 comments

Comments

@ioquatix
Copy link
Contributor

It can be useful to embed tags with namespaces and have them pass through correctly.

Some parsers already support this:

irb(main):002:0> Kramdown::Document.new("<foo:bar>\nbaz\n</foo:bar>").to_html
=> "<foo:bar>\nbaz\n</foo:bar>\n"

Tag names and attribute names should be allowed to contain :.

Further discussion:

@ioquatix
Copy link
Contributor Author

Other parsers don't support it:

irb(main):005:0> CommonMarker.render_doc("<foo:bar>\nbaz\n</foo:bar>").to_html
=> "<p><a href=\"foo:bar\">foo:bar</a>\nbaz\n&lt;/foo:bar&gt;</p>\n"

@movermeyer
Copy link

movermeyer commented May 19, 2020

Edit: Please ignore. I'm a dummy


Some parsers already support this

It doesn't matter what Kramdown does, since it is a Markdown renderer, not a Commonmark renderer.

The whole point of Commonmark is that there is one spec. Not a collection of Markdown extensions that people implement in their parsers

@ioquatix
Copy link
Contributor Author

The point is to show that it's feasible/possible and that some implementations do it already. It's useful to have a point of reference when considering how we evolve the spec (or not).

@movermeyer
Copy link

movermeyer commented May 19, 2020

@ioquatix I am soooo sorry. I'm in the wrong repo...

Sorry, sorry, sorry...

@ioquatix
Copy link
Contributor Author

@movermeyer is there a better place to make issues regarding changes to the spec?

@jgm
Copy link
Member

jgm commented May 19, 2020

This is for cmark, the C implementation of the spec.
To raise issues regarding changes to the spec, you should start at https://talk.commonmark.org. There is also a repo commonmark/commonmark-spec, but it is better to discuss on the forum first.

@jgm jgm closed this as completed May 19, 2020
@ioquatix
Copy link
Contributor Author

@jgm I made a topic for discussion and added a PR to the spec here: commonmark/commonmark-spec#648

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants