-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Update configuration-markup.md: remove ambiguity #2872
base: master
Are you sure you want to change the base?
Conversation
Add double quotes around the names, otherwise I read it twice as a verb there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pointing this out. I think this was written during development of the subscript/superscript/mark/delete/insert capabilities, where each was a separate extension. At some point we bundled these features into one extension: Extras.
So I think when we refer to an extension it should be capitalized, but quote a feature (see my suggestion). Or maybe place within backticks.
@@ -104,10 +104,10 @@ Superscript|`1^st^`|`1<sup>st</sup>` | |||
[subscript]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/sub | |||
[superscript]: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/sup | |||
|
|||
To avoid a conflict when enabling the Hugo Goldmark Extras subscript extension, if you want to render subscript and strikethrough text concurrently you must: | |||
To avoid a conflict when enabling the Hugo Goldmark Extras "subscript" extension, if you want to render subscript and strikethrough text concurrently you must: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To avoid a conflict when enabling the Hugo Goldmark Extras "subscript" extension, if you want to render subscript and strikethrough text concurrently you must: | |
To avoid a conflict when enabling the Hugo Goldmark Extras "subscript" feature, if you want to render subscript and strikethrough text concurrently you must: |
|
||
1. Disable the Goldmark strikethrough extension | ||
1. Enable the Hugo Goldmark Extras delete extension | ||
1. Disable the Goldmark "strikethrough" extension |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. Disable the Goldmark "strikethrough" extension | |
1. Disable the Goldmark Strikethrough extension |
1. Disable the Goldmark strikethrough extension | ||
1. Enable the Hugo Goldmark Extras delete extension | ||
1. Disable the Goldmark "strikethrough" extension | ||
1. Enable the Hugo Goldmark Extras "delete" extension |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. Enable the Hugo Goldmark Extras "delete" extension | |
1. Enable the Hugo Goldmark Extras "delete" feature |
@@ -126,7 +126,7 @@ enable = true | |||
|
|||
{{< new-in 0.122.0 />}} | |||
|
|||
Enable the passthrough extension to include mathematical equations and expressions in Markdown using LaTeX markup. See [mathematics in Markdown] for details. | |||
Enable the "passthrough" extension to include mathematical equations and expressions in Markdown using LaTeX markup. See [mathematics in Markdown] for details. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Enable the "passthrough" extension to include mathematical equations and expressions in Markdown using LaTeX markup. See [mathematics in Markdown] for details. | |
Enable the Passthrough extension to include mathematical equations and expressions in Markdown using LaTeX markup. See [mathematics in Markdown] for details. |
jmooring: > I think this was written during development of the subscript/superscript/mark/delete/insert capabilities, where each was a separate extension. At some point we bundled these features into one extension: Extras. > So I think when we refer to an extension it should be capitalized, but quote a feature (see my suggestion). Or maybe place within backticks.
Thanks for explaining, I have applied your exact suggestion. I've also grepped the docs PS: The link references like |
1. Disable the Goldmark strikethrough extension | ||
1. Enable the Hugo Goldmark Extras delete extension | ||
1. Disable the Goldmark Strikethrough extension | ||
1. Enable the Hugo Goldmark Extras Delete extension |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. Enable the Hugo Goldmark Extras Delete extension | |
1. Enable the Hugo Goldmark Extras "delete" feature |
Add double quotes around the names, otherwise I read it twice as a verb there.
Although a couple paragraphs above the names are capitalized (if you care about consistency) I decided not to change them, because capitalization is appropriate there.