-
Notifications
You must be signed in to change notification settings - Fork 320
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
Don't convert ascii to unicode in URLs #10042
Comments
Notably, my workaround is format-agnostic (because it produces an actual @machow If you need 1.5 to ship pristine URLs across metadata, and you know that they're URLs, you can use that syntax. We should have a transparent mechanism for this, but the |
Re-posting below for context the explanation regarding why Pandoc does convert to en-dash. This is all due to Pandoc Markdown reader when So we could also opt-out this extension in our qmd reader ( Though it would have other impact on content output (especially for TeX ligatures in LaTeX pdf output) From #10021 (comment) How smart extension causes -- to be read as unicode by markdown reader
Just want to add additional information on this. This is Pandoc. It has a
This extensions is activated by default and impact how things are written in output. HTML is among the format where en-dash are used
Note the two dashes without smart enabled. This all happens in the Markdown reader !
Why does it happens with metadata field ? Because they are parsed as Markdown values by Pandoc
Related issue in the past where internally using the new |
If |
This happens in metadata, but it's likely that it also happens in other parts.
Repro:
(This is, ultimately, the same bug that caused us to have to reimplement shortcodes:
{{< foo https://pr-350--quartodoc.netlify.app >}}
would destroy the URL in the past.)The text was updated successfully, but these errors were encountered: