This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | lemburg |
|---|---|
| Recipients | belopolsky, docs@python, ezio.melotti, georg.brandl, lemburg, loewis, vstinner |
| Date | 2011年04月15日.17:10:33 |
| SpamBayes Score | 9.467871e-12 |
| Marked as misclassified | No |
| Message-id | <4DA87BFF.2070401@egenix.com> |
| In-reply-to | <1302884920.14.0.458657401187.issue10665@psf.upfronthosting.co.za> |
| Content | |
|---|---|
Ezio Melotti wrote: > > Ezio Melotti <ezio.melotti@gmail.com> added the comment: > > Alexander suggested on IRC to use the 'unicode' directive[0], but even if that works in the HTML (only outside code blocks), it still breaks the PDF. > Another alternative that might work is the 'raw' role[1]. > > [0]: http://docutils.sourceforge.net/docs/ref/rst/directives.html#unicode-character-codes > [1]: http://docutils.sourceforge.net/docs/ref/rst/roles.html#specialized-roles I don't think we should include Unicode code points as literals in Python source code examples, for much the same reason we don't want them in the stdlib source code. Why don't you use the standard literal escapes for the examples and annotate the code points with the code point names ? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011年04月15日 17:10:34 | lemburg | set | recipients: + lemburg, loewis, georg.brandl, belopolsky, vstinner, ezio.melotti, docs@python |
| 2011年04月15日 17:10:33 | lemburg | link | issue10665 messages |
| 2011年04月15日 17:10:33 | lemburg | create | |