(This might be a silly question..) In the dev stdlib reference there are lots of pages in which all text is in italics. Such as all chapters after chapter 18. Is it supposed to be that way? It looks quite ugly. -- mvh Björn
BJörn Lindqvist schrieb:
(This might be a silly question..)
In the dev stdlib reference there are lots of pages in which all text is in italics. Such as all chapters after chapter 18.
Certainly not. In today's copy (8.3.07, 13:30 GMT), this starts between 18.17 and 18.17.1. However, looking at the tex, I cannot find anything suspicious. texcheck complains about a missing ), which I added, but it only was a problem of the text, not of the markup. Some tex guru will have to figure this out; please submit a bugreport (if you can't figure it out yourself). Regards, Martin
On Thursday 08 March 2007 08:42, Martin v. Löwis wrote:
Certainly not. In today's copy (8.3.07, 13:30 GMT), this starts between 18.17 and 18.17.1. However, looking at the tex, I cannot find anything suspicious. texcheck complains about a missing ), which I added, but it only was a problem of the text, not of the markup.
This doesn't seem to be a problem any more, so I'm going to presume Martin fixed it. ;-) -Fred -- Fred L. Drake, Jr. <fdrake at acm.org>
On 3/29/07, Fred L. Drake, Jr. <fdrake@acm.org> wrote:
On Thursday 08 March 2007 08:42, Martin v. Löwis wrote:
Certainly not. In today's copy (8.3.07, 13:30 GMT), this starts between 18.17 and 18.17.1. However, looking at the tex, I cannot find anything suspicious. texcheck complains about a missing ), which I added, but it only was a problem of the text, not of the markup.
This doesn't seem to be a problem any more, so I'm going to presume Martin fixed it. ;-)
The docs for atexit in py3k [1] are mostly (though not all) in italics; I can't figure out why, and I'd appreciate if anyone with stronger latex-foo could take a look. Thanks, Collin Winter [1] - http://docs.python.org/dev/3.x/lib/module-atexit.html
Collin Winter schrieb:
On 3/29/07, Fred L. Drake, Jr. <fdrake@acm.org> wrote:
On Thursday 08 March 2007 08:42, Martin v. Löwis wrote:
Certainly not. In today's copy (8.3.07, 13:30 GMT), this starts between 18.17 and 18.17.1. However, looking at the tex, I cannot find anything suspicious. texcheck complains about a missing ), which I added, but it only was a problem of the text, not of the markup.
This doesn't seem to be a problem any more, so I'm going to presume Martin fixed it. ;-)
The docs for atexit in py3k [1] are mostly (though not all) in italics; I can't figure out why, and I'd appreciate if anyone with stronger latex-foo could take a look.
This is still the same error as in the trunk; the fix hasn't been forward-ported yet. Georg
On 3/29/07, Georg Brandl <g.brandl@gmx.net> wrote:
Collin Winter schrieb:
The docs for atexit in py3k [1] are mostly (though not all) in italics; I can't figure out why, and I'd appreciate if anyone with stronger latex-foo could take a look.
This is still the same error as in the trunk; the fix hasn't been forward-ported yet.
In the interest of expanding the general level of latex fu, the difference stems from \em version \emph: \em switches the current font to emphasized in the current scope, whereas \emph is a command that formats its argument emphasizedly. Thus {\em ... } and \emph{...} achieve similar results, but \em{ ... } switches the top-level font, which is followed by a grouping {} (which likley does nothing). -Mike
On Thursday 29 March 2007 17:48, Collin Winter wrote:
The docs for atexit in py3k [1] are mostly (though not all) in italics; I can't figure out why, and I'd appreciate if anyone with stronger latex-foo could take a look.
This is now fixed in Py3K, and there are no further occurrances of \em on the trunk of in Py3K. The online build will catch up when the automated build runs again. -Fred -- Fred L. Drake, Jr. <fdrake at acm.org>
participants (6)
-
"Martin v. Löwis" -
BJörn Lindqvist -
Collin Winter -
Fred L. Drake, Jr. -
Georg Brandl -
Mike Klaas