1 |
b.n. wrote: |
2 |
> Willie Wong ha scritto: |
3 |
> |
4 |
>> Starting a new thread because this is getting way off topic (both |
5 |
>> re: gentoo or re: the topic under discussion in the other thread) |
6 |
>> |
7 |
>> On Sun, Dec 21, 2008 at 11:25:12PM -0600, Penguin Lover ??Q?? squawked: |
8 |
>> |
9 |
>>> On Sun, 21 Dec 2008 23:05:58 -0600 |
10 |
>>> Steven Susbauer <stupendoussteve@×××××××.com> wrote: |
11 |
>>> |
12 |
>>> |
13 |
>>>> Some mail readers convert *asterisks* as bold statements. I believe it |
14 |
>>>> is the generally accepted way to make a section stand out when dealing |
15 |
>>>> with plain text. |
16 |
>>>> |
17 |
>>> Yes. The other two kinds of conventional pseudo-markup are /slashes/ |
18 |
>>> for italics and _underscores_ for underlining. Even with clients that |
19 |
>>> don't use them to change rendering, they're easy to pick up by eye when |
20 |
>>> reading the plain text. |
21 |
>>> |
22 |
>>> |
23 |
>> Okay, my tongue was firmly in my cheek in the hypothetical question I |
24 |
>> just posted in the old thread. But now seriously: is there anyway of |
25 |
>> telling the recipient client to NOT change rendering, other than telling |
26 |
>> the recipient to turn off rendering changes in the mail client? I feel |
27 |
>> that this is a more legitimate question because it is quite possible |
28 |
>> that the answer to some question posted on a linux mailing list |
29 |
>> invoves a one-line sed command, or even a directory listing. Is it |
30 |
>> possible to tell clients which change rendering that, yes, I really |
31 |
>> mean /root/.rev* and not <em>root</em>.rev* ? |
32 |
>> |
33 |
> |
34 |
> My client -Thunderbird- solves it quite elegantly. It keeps the |
35 |
> rendering characters AND renders. |
36 |
> |
37 |
> That is, *something* is rendered as [bold]*something*[/bold] and not as |
38 |
> [bold]something[/bold]. |
39 |
> |
40 |
> So when there is some /directory-path/ stuff I see it funnily in italic |
41 |
> but I also see the slashes, and everyone's happy. |
42 |
> |
43 |
> Don't know about other mail readers, but it seems such an obvious |
44 |
> solution that I'd be amazed if Thunderbird hasn't just copied it from |
45 |
> other clients. |
46 |
> |
47 |
> m. |
48 |
> |
49 |
> |
50 |
> |
51 |
|
52 |
I get the same here but couldn't figure out how to explain it. LOL I |
53 |
use Seamonkey as I think I mentioned earlier. |
54 |
|
55 |
Dale |
56 |
|
57 |
:-) :-) |