| 1 |
Starting a new thread because this is getting way off topic (both |
| 2 |
re: gentoo or re: the topic under discussion in the other thread) |
| 3 |
|
| 4 |
On Sun, Dec 21, 2008 at 11:25:12PM -0600, Penguin Lover ??Q?? squawked: |
| 5 |
> On Sun, 21 Dec 2008 23:05:58 -0600 |
| 6 |
> Steven Susbauer <stupendoussteve@×××××××.com> wrote: |
| 7 |
> |
| 8 |
> > Some mail readers convert *asterisks* as bold statements. I believe it |
| 9 |
> > is the generally accepted way to make a section stand out when dealing |
| 10 |
> > with plain text. |
| 11 |
> |
| 12 |
> Yes. The other two kinds of conventional pseudo-markup are /slashes/ |
| 13 |
> for italics and _underscores_ for underlining. Even with clients that |
| 14 |
> don't use them to change rendering, they're easy to pick up by eye when |
| 15 |
> reading the plain text. |
| 16 |
> |
| 17 |
|
| 18 |
Okay, my tongue was firmly in my cheek in the hypothetical question I |
| 19 |
just posted in the old thread. But now seriously: is there anyway of |
| 20 |
telling the recipient client to NOT change rendering, other than telling |
| 21 |
the recipient to turn off rendering changes in the mail client? I feel |
| 22 |
that this is a more legitimate question because it is quite possible |
| 23 |
that the answer to some question posted on a linux mailing list |
| 24 |
invoves a one-line sed command, or even a directory listing. Is it |
| 25 |
possible to tell clients which change rendering that, yes, I really |
| 26 |
mean /root/.rev* and not <em>root</em>.rev* ? |
| 27 |
|
| 28 |
W |
| 29 |
-- |
| 30 |
Chocolate has many preservatives. Preservatives make you look younger. |
| 31 |
Sortir en Pantoufles: up 745 days, 4:30 |
Archives