Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Clarify 'time zone' in a Specific words section #1352

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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 18, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Clarify 'time zone' in a Specific words section
  • Loading branch information
nedbat committed Jul 15, 2024
commit cbcd2538f45f27885bde62588f73f570553abfda
16 changes: 13 additions & 3 deletions 16 documentation/style-guide.rst
Original file line number Diff line number Diff line change
Expand Up @@ -54,10 +54,15 @@ starting it with a lowercase letter should be avoided.
Many special names are used in the Python documentation, including the names of
operating systems, programming languages, standards bodies, and the like. Most
of these entities are not assigned any special markup, but the preferred
spellings are given here to aid authors in maintaining the consistency of
presentation in the Python documentation.
spellings are given in :ref:`glossary` to aid authors in maintaining the
consistency of presentation in the Python documentation.

Other terms and words deserve special mention as well; these conventions should
.. _glossary:

Specific words
==============
Copy link
Member

Choose a reason for hiding this comment

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

I predict this will confuse me, shall we have the same name for both the link and the title?

Copy link
Member

@ezio-melotti ezio-melotti Jul 16, 2024

Choose a reason for hiding this comment

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

The link might also be confused with the glossary directive.

Copy link
Member Author

Choose a reason for hiding this comment

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

I changed the reference to specific words.


Some terms and words deserve special mention. These conventions should
be used to ensure consistency throughout the documentation:

C API
Expand All @@ -79,6 +84,11 @@ reST
used to produce Python documentation. When spelled out, it is
always one word and both forms start with a lowercase 'r'.

time zone
Spell out as two words when talking about the real-world concept.
Only spell as one word when referring to a Python term like a module,
class, or argument.
Copy link
Member

Choose a reason for hiding this comment

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

Shouldn't they have markup like :mod: or similar in this case?
If that's the case, "timezone" should never appear in plain text.
Not sure if it's worth clarifying this.

Copy link
Contributor

Choose a reason for hiding this comment

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

Not sure if it's worth clarifying this.

Anyone reading the devguide style guide will probably already know how to mark up classes, so I'm not sure it's worth complicating the current wording.

Copy link
Member

Choose a reason for hiding this comment

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

What I meant is:

  • talking about the concept? Always use two words and no markup.
  • talking about the module/class/arg? Always use one word and the appropriate markup.

This implies that "timezone" will never appear in plain text and "time zone" will never appear within markup.

IOW, the fact that you are using markup or not already determines whether to use one or two words, without having to think if you are referring to a module/class/argument or not.

Copy link
Contributor

Choose a reason for hiding this comment

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

Sure, if it does not clutter the wording too much, I'm fine with such a change.

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
Spell out as two words when talking about the real-world concept.
Only spell as one word when referring to a Python term like a module,
class, or argument.
When referring to a Python term like a module, class, or argument
it is always spelled as one word and surrounded by the appropriate markup
(for example, ``:mod:`timezone```).
When talking about the real-world concept it is spelled as two words.

Copy link
Member Author

Choose a reason for hiding this comment

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

I added a modified version of this text.


Unicode
The name of a character coding system. This is always written
capitalized.
Expand Down
Loading
Morty Proxy This is a proxified and sanitized view of the page, visit original site.