Message133854
| Author |
belopolsky |
| Recipients |
belopolsky, docs@python, ezio.melotti, georg.brandl, lemburg, loewis, vstinner |
| Date |
2011年04月15日.17:25:00 |
| SpamBayes Score |
1.7876721e-06 |
| Marked as misclassified |
No |
| Message-id |
<BANLkTik-+O1GWjE52Nh+MjK4TROSG772Mw@mail.gmail.com> |
| In-reply-to |
<4DA87BFF.2070401@egenix.com> |
| Content |
On Fri, Apr 15, 2011 at 1:10 PM, Marc-Andre Lemburg
<report@bugs.python.org> wrote:
>..
> Why don't you use the standard literal escapes for the examples
> and annotate the code points with the code point names ?
A am neutral on how to enter unicode characters in source reST. In
the previous discussions most people seemed to prefer WISIWYG. If
literal escapes solved the PDF issue, I would use it even at the
expense of loosing testability of the output displays.
Code point names as usually very long for exotic characters that
illustrate UCD features. I like presenting them, but in tables I'd
rather present more examples and still keep column width reasonable. |
|