Skip to content

Add a note to the style guide about abbreviations#1844

Draft
sirosen wants to merge 2 commits into
python:mainfrom
sirosen:add-abbreviations-to-style-guide
Draft

Add a note to the style guide about abbreviations#1844
sirosen wants to merge 2 commits into
python:mainfrom
sirosen:add-abbreviations-to-style-guide

Conversation

@sirosen

@sirosen sirosen commented Jun 26, 2026

Copy link
Copy Markdown
Contributor

Hat tip to @hugovk for this! Not only the issue (#1824), but also his comments preceding it made this easy to write.

This as a draft because it conflicts with #1828, which is already approved and should ideally merge first.
Once that's done, the exact positioning of this content in the page may change.

Open question: should this be converted to be a subsection of "Use simple language" or "Specific words"?


resolves #1824

After the section on specific terms, but before "simple language", add a section that explains that documentation should spell out acronyms, preferring the "<full-spelling> (<acronym>)" format.

resolves python#1824

After the section on specific terms, but before "simple language", add a
section that explains that documentation should spell out acronyms,
preferring the "<full-spelling> (<acronym>)" format.
@read-the-docs-community

read-the-docs-community Bot commented Jun 26, 2026

Copy link
Copy Markdown

Documentation build overview

📚 CPython devguide | 🛠️ Build #33327755 | 📁 Comparing 3b5d5b5 against latest (0164145)

  🔍 Preview build  

3 files changed
± versions/index.html
± documentation/markup/index.html
± documentation/style-guide/index.html

@StanFromIreland

Copy link
Copy Markdown
Member

Hi Stephen, this issue was originally specific to :abbr:, but I like your expanded approach. I would however suggest a little move.

  • We have a section for Sphinx roles, which is where I think the role-specific guidance should go.
  • Spelling out acronyms can be moved to "Use simple language" (which, as I think about it now, would be better if it was named "Use accessible language," but that's for another day ;-).

@sirosen

sirosen commented Jun 26, 2026

Copy link
Copy Markdown
Contributor Author

Oh, I hadn't even thought to put it in the role usage docs! 🤦
That seems obvious now.

I want to keep some explanation of the rationale. I'll move things as you suggest, and I think the "some assistive technology" note will end up with the roles.


Edit done! LMK if it needs more tuning.

The role is documented in with other sphinx roles. In order for the rst
to read easily, one line of non-semantic whitespace was added to a list.

The acronym usage note is moved to the end of "Use simple language"
@sirosen

sirosen commented Jun 26, 2026

Copy link
Copy Markdown
Contributor Author

"Use simple language" (which, as I think about it now, would be better if it was named "Use accessible language," but that's for another day ;-).

Maybe... I like "Use simple language". It has two virtues:

  1. It is a simpler word for the idea of "accessibility", more familiar to more readers -- to a large degree they are equivalent here
  2. In the measure that the two words are not equivalent, "simple" is good general advice for writing well

I could probably be convinced, but we can discuss outside of this PR. 😁

@StanFromIreland

StanFromIreland commented Jun 26, 2026

Copy link
Copy Markdown
Member

As I said, that's for another day ;-) I also have to catch up on the Discord discussion.

Thanks for the changes, it's what I had in mind.

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.

Recommend avoiding abbr role

2 participants