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

Update configuration-markup.md: remove ambiguity #2872

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

vadcx
Copy link

@vadcx vadcx commented Feb 7, 2025

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.

Add double quotes around the names, otherwise I read it twice as a verb there.
Copy link
Member

@jmooring jmooring left a 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:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

vadcx added 2 commits February 7, 2025 18:40
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.
@vadcx
Copy link
Author

vadcx commented Feb 7, 2025

Thanks for explaining, I have applied your exact suggestion. I've also grepped the docs (extension|feature|subscript|superscript|delete|insert|extra|passthrough) and noticed similar changes were appropriate for passthrough.md. I believe this is complete now?

PS: The link references like [label name] are case-insensitive, I had to test this :)

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. Enable the Hugo Goldmark Extras Delete extension
1. Enable the Hugo Goldmark Extras "delete" feature

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

Successfully merging this pull request may close these issues.

2 participants