[issue18177] Typo in Documents
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
New submission from icedream91: In library.pdf file(Release 3.3.2, June 09, 2013), I found a typo in page 149: I think the quotation marks are wrong in "datetime.isoformat(sep=âTâ)" sentence, they should both be "'". But it's right in online documents (http://docs.python.org/3/library/datetime.html#datetime.datetime.isoformat). Thanks. ---------- assignee: docs@python components: Documentation messages: 190882 nosy: docs@python, icedream91 priority: normal severity: normal status: open title: Typo in Documents versions: Python 3.3 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue18177> _______________________________________
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
A.M. Kuchling added the comment: Confirmed. I think this is a general typographic issue in the PDF documentation. If I cut-and-paste the datetime.isoformat(sep='T') line from the PDF, the single quotes are pasted as U+2019 RIGHT SINGLE QUOTE. Looking at the library.tex file built by "make pdflatex", it contains the ASCII single quotes, so LaTeX is responsible for turning the quotes into smart quotes. I don't know if this is worth fixing and can see arguments both ways. The smart quotes are readable and I doubt a reader will be confused and try to actually type them in their source code. OTOH it's annoying that cut-and-pasting code from the PDFs won't work. ---------- nosy: +akuchling _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue18177> _______________________________________
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
R. David Murray added the comment: I presume that tex doesn't do quote-transformation on code blocks (it is not really smart quotes, since IIRC in tex you actually have to specify ` and ' in the correct places yourself). So perhaps the problem is that the function headers &c aren't being properly marked up as code in the latex output engine of Sphinx? ---------- nosy: +r.david.murray _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue18177> _______________________________________
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
Changes by R. David Murray <rdmurray@bitdance.com>: ---------- title: Typo in Documents -> Incorect quote marks in code section-headers in PDF version of docs _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue18177> _______________________________________
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
Changes by Ezio Melotti <ezio.melotti@gmail.com>: ---------- nosy: +ezio.melotti type: -> enhancement versions: +Python 3.4 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue18177> _______________________________________
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
Changes by Tshepang Lekhonkhobe <tshepang@gmail.com>: ---------- nosy: +tshepang _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue18177> _______________________________________
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
Tshepang Lekhonkhobe added the comment: A work-around: http://stackoverflow.com/a/16164658/321731. ---------- versions: +Python 2.7 _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue18177> _______________________________________
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
Ezio Melotti added the comment: Should this be moved to the Sphinx bug tracker? ---------- nosy: +georg.brandl status: open -> pending _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue18177> _______________________________________
![](https://secure.gravatar.com/avatar/fa0f7819f1825f596b384c19aa7dcf33.jpg?s=120&d=mm&r=g)
Georg Brandl added the comment: Yes, there is already one or two issues there (e.g. number 1239). ---------- resolution: -> invalid status: pending -> closed _______________________________________ Python tracker <report@bugs.python.org> <http://bugs.python.org/issue18177> _______________________________________
participants (6)
-
A.M. Kuchling
-
Ezio Melotti
-
Georg Brandl
-
icedream91
-
R. David Murray
-
Tshepang Lekhonkhobe