Message155179
| Author |
sandro.tosi |
| Recipients |
eric.araujo, ezio.melotti, sandro.tosi, tshepang |
| Date |
2012年03月08日.20:45:20 |
| SpamBayes Score |
2.6789057e-05 |
| Marked as misclassified |
No |
| Message-id |
<CAPdtAj0H+WX-pLyDNhY81yG=5-VQAHbXr5pXjOUbREeKyrcTCA@mail.gmail.com> |
| In-reply-to |
<1331238883.61.0.78823389297.issue14218@psf.upfronthosting.co.za> |
| Content |
eheh yeah it seems so :)
What I think Tshepang wants is this:
- the devguide contains the description of how to document python
- that documentation is about a set of ReST coding commands that
generate the desired output
- currently the devguide reports only the ReST code block without,
right below to that block, the resulting highlitening.
-> add the resulting "visual" output right below the description of
the code to use.
so something like
blablabla you have to use ``word`` to have the word in bold (or
whatever it generates, I'm too lazy to check :) ) for example:
<insert here the visual output of a ReST doc where ``word`` is used>
Tshepang: did I get it correctly? Éric: is it (at least a bit) clearer? |
|