Skip to content
This repository has been archived by the owner on Nov 15, 2022. It is now read-only.

Common syntax for abbreviations #34

Closed
kimburgess opened this issue Dec 11, 2020 · 3 comments · Fixed by #46
Closed

Common syntax for abbreviations #34

kimburgess opened this issue Dec 11, 2020 · 3 comments · Fixed by #46
Assignees

Comments

@kimburgess
Copy link
Contributor

Rather than defaulting to inline HTML <abbr> tags, it would be nice to define a common syntax for usage within doc content, which the parser will then transform to these.

A good option for this looks to be via remark-abbr.

This will also allow these to be checked via the the linter, rather than needing to add exception, or a blanket ignore rule.

Originally from #29 (comment)

@mghill mghill mentioned this issue Dec 18, 2020
@mghill
Copy link
Contributor

mghill commented Jan 11, 2021

Current thought on this: I think given our other choices for relatively-universal compatibility for display, just going with manual tags on the first instance of an acronym on a page could be our best bet. The remark-abbr is neat, and probably more friendly for our specific intended use, but only renders okay without the plugin. What's your thought?

Point back against: the <abbr> tags run afoul of #27 as the linter treats them like words in some instances. I'm back onside for remark-abbr

@kimburgess
Copy link
Contributor Author

Don't let bugs / limitations in linter config influence writing style. Anything that pops up there can be fixed (and ignored until then).

That being said, I do quite like the remark-abbr syntax. Using it seems inline with other decisions around keeping things markdown-esque (tabs annotations etc). It will also rewrite all occurrences in the doc to be wrapped in <abbr> elements.

@mghill
Copy link
Contributor

mghill commented Jan 12, 2021

Honestly I think I was still up in the air on this, rather than the linter changing my mind, it just made me look at it again. I like universal compatibility, but the endnote syntax is very unobtrusive and better in the long term.

@mghill mghill mentioned this issue Jan 12, 2021
@kimburgess kimburgess linked a pull request Jan 15, 2021 that will close this issue
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants