-
-
Notifications
You must be signed in to change notification settings - Fork 859
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
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
@@ -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 | ||||||||||||||
============== | ||||||||||||||
|
||||||||||||||
Some terms and words deserve special mention. These conventions should | ||||||||||||||
be used to ensure consistency throughout the documentation: | ||||||||||||||
|
||||||||||||||
C API | ||||||||||||||
|
@@ -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. | ||||||||||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Shouldn't they have markup like There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
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. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What I meant is:
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. There was a problem hiding this comment. Choose a reason for hiding this commentThe 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. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe 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. | ||||||||||||||
|
There was a problem hiding this comment.
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?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
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.There was a problem hiding this comment.
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
.