Add Glossary

[avivace]

I think a preliminary section mentioning some jargon and commonly used acronyms (e.g. LSB, MSB) could be helpful. It could also introduce some of the standards and rules we adopt in the document, adding some clarifications (e.g. units, bases)

Please see further in the thread for particular sticking points.

[ISSOtm]

As per #287, "dots" is introduced twice.

[brainard52]

@avivace requested that I make a new issue, but I'll just hijack this one.

I think a glossary with links to each section the terms appear in would be great. It could additionally include definitions that appear on mouse-over of the term when the main body of the document (maybe with a delay).

[ISSOtm]

I can try adding markup for that as part of #292.

[brainard52]

I can try adding markup for that as part of #292.

Nice. If you have a plaintext release of pandoc, I can extract a list of words that aren’t typically in an english dictionary for you

[ISSOtm]

Does this Markdown render do the job?

[brainard52]

That’s great. If this works, we might even be able to integrate the glossary generation into the build.

[avivace]

To add: "CGB mode"

[ISSOtm]

Markup possibilities:
https://github.com/commonmark/commonmark-spec/wiki/Deployed-Extensions#abbreviation
https://github.com/commonmark/commonmark-spec/wiki/Deployed-Extensions#definition-list

[avivace]

Needs to be added to the Glossary: #350 (comment)

[avivace]

Needs to be added to the Glossary: #534 (review)