Skip to content

kbd element not considered as raw text #112

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

Closed
denisdefreyne opened this issue Mar 17, 2014 · 6 comments
Closed

kbd element not considered as raw text #112

denisdefreyne opened this issue Mar 17, 2014 · 6 comments

Comments

@denisdefreyne
Copy link

kramdown.rb, line #184 specifies that the script, pre and code element have raw text, so that no smart typographical conversions are made (-- to en-dash etc).

I believe this list of elements should also include kbd. Otherwise, long-form commandline options (e.g. --version) need to be escaped:

Ruby may already be installed on your system. To check, open a terminal window
and type <kbd>ruby \--version</kbd>.

Without the backslash, the -- is turned into an en-dash.

@gettalong
Copy link
Owner

You are referencing the kramdown converter and not the parser - any specific reason?

@denisdefreyne
Copy link
Author

@gettalong Not sure. The only place where I could find where text is considered as “raw” was in that specific place.

@gpakosz
Copy link

gpakosz commented May 6, 2014

what gives?

@gettalong
Copy link
Owner

Not sure what to do about this... The HTML converter is the false place since by then the en-dash is already created as an element.

@denisdefreyne
Copy link
Author

@gettalong I am not sure where the fix should be, but I do know that the contents of the kbd element should be treated as raw, just like code, script etc.

@denisdefreyne
Copy link
Author

Awesome, thanks. 👍

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