-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Document formatting strings in the docs #15379
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
79c1c56
to
476a03e
Compare
@@ -410,6 +410,12 @@ Use simple single or double quotes when giving string values, e.g. | |||
|
|||
If 'tight', try to figure out the tight bbox of the figure. | |||
|
|||
No ``'extra'`` literal quotes. |
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.
Was this meant to be a title instead of part of the code block?
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.
No, this is intentional. Originally, I tried to put this in an inline lieteral:
The use of extra literal quotes around the text (````'extra'````) is discouraged.
However, it appears that four backticks followed by a single-quote or double-quote character are not interpreted correctly by Sphinx/ReST (in contrast followed by a letter works, e.g. ````literal````
further above).
I would like to have the negative example shown somewhere, but did not manage to write it as an inline literal. So I just added it it to the block literal.
476a03e
to
8c7d0e9
Compare
Although this is a doc change, I don't think we need to pull it back to the 3.1 branches. |
…379-on-v3.2.x Backport PR #15379 on branch v3.2.x (Document formatting strings in the docs)
PR Summary
Clarification motivated by #15375 (comment).
Based on #10225 (section
String values
).Plus a minor wording fix in one of the examples.