String with hyphen followed by a number renders as an en-dash
// Please enter a detailed description of the issue // Description of the issue:
A string with a hyphen followed by a number renders as an en-dash
// Please enter a list of steps required to reproduce the issue // Steps to reproduce: A string like:
a-b-007.example.com
renders as:
a-b–007.example.com
The second hyphen is actually an en-dash
// If applicable please attach a sample document that causes the issue for you.
// Configuration (do not edit) Marked 2 1007 (Direct)
macOS Version: 10.15.7
additionalMathJaxConfig:
allowPageBreakInCode: YES
bookTxtIsLeanpub: NO
summaryMdIsGitBook: NO
codeIsPoetry: NO
codeCanWrap: YES
collapsibleHeadlines: NO
convertGithubCheckboxes: YES
convertYAMLToMMD: NO
defaultMathJaxConfig: TeX-AMS-MML_HTMLorMML
defaultPreviewStyle: 3
defaultProcessor: MultiMarkdown
enableMiniMap: NO
excludeBlockQuotesFromCounts: NO
excludeFootnotesFromCounts: NO
excludeVerbatimFromCounts: NO
excludeCaptionsFromCounts: NO
folderPreviewExtensionsArray: md, markdown, txt, mdown, html, opml
githubNewlines: NO
h1IsPageBreak: NO
h2IsPageBreak: NO
hrIsPageBreak: NO
includeMathJax: NO
includeKatex: NO
limitTextWidth: NO
minimalJavaScript: NO
outlineModeExtensions:
permissionGranted: NO
printHeaderBottomLeft:
printHeaderBottomRight:
printHeaderFirstPage: NO
printFooterFirstPage: NO
printHeaderTopLeft:
printHeaderTopRight:
processHTMLFiles: YES
removeMetadataForPreview: NO
removeYAMLHeaders: NO
scrollToEdit: YES
shouldDetectCritic: YES
shouldHighlightMarkupErrors: NO
shouldLoadCritic: NO
syntaxHighlight: YES
syntaxHighlightOnlyLang: NO
useCustomMarkdownProcessor: NO
customMarkdownProcessor:
useCustomPreprocessor: NO
customPreprocessor:
useFirstH1AsPrintTitle: YES
- test_hyphen.md 179 Bytes
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Brett on 13 Oct, 2020 09:52 PM
This is standard typographic conversion for numeric spans. Uncheck typographically correct punctuation under Preferences->Style to disable the conversion. You can also switch to the GFM processor, which does less thorough typographic conversions.
- Brett
2 Posted by Michael Burk on 15 Oct, 2020 04:29 PM
Hi Brett, thank you for the quick response!
I'm probably being typographically geeky here, but I searched for rules and
examples of using the en dash.
Everyone agrees on using one in a numeric span, as you said, and I always
use that.
I couldn't find any examples matching my case. The closest I found is a
date range like June 30–July 7, where the dash separates a number and a
letter.
It seems that my example is an edge case, and it seems non-intuitive to me
to use the en dash when it's a string of numbers and letters like this. I
would prefer that the style be preserved in this case. However, it's
probably very hard to recognize this case programmatically.
This is a great program, and I appreciate your thoroughness!
— Michael
Support Staff 3 Posted by Brett on 15 Oct, 2020 04:52 PM
I don't disagree. These are features built into the processors, in this
case MultiMarkdown, and the finer points are beyond my control. As a
side note, you can manually prevent the typographic substitution by
escaping the hyphen with a backslash, e.g. `Word\-9`.
-Brett
4 Posted by Michael Burk on 15 Oct, 2020 04:57 PM
I see. Thanks for the explanation and tip!