James G. Sack (jim) wrote:
This is a test to explore display of non-ascii in email clients.
These are all the printable special characters known to the latin1
(iso8859-1) encoding scheme.
==> BUT: I am composing and transmitting this as utf8.
In utf8 encoding, non-ascii has multi-byte values; the latin1 subset of
the full unicode has byte-pairs with the first byte being 0xC2 or 0xC3
and the second byte something greater than 0x7F.
¡¢£¤¥¦§¨©ª«¬Â®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÃ�ÂÃÄÅÆÇÈÉÊËÌÃ�ÃŽÃ�Ã�ÑÒÓÔÕÖ×ØÙÚÛÜÃ�ÞßÃ
áâãäåæçèéêëìÃîïðñòóôõö÷øùúûüýþÿ
Your email client may re-encode the incoming characters, per client and
your settings. If your email client has trouble (re-encoding or)
displaying some of these characters, it may replace the troublesome ones
with something which should at least catch the eye. I'm not sure what
replacement method is used by what client. Unicode does have a special
character signifying "unknown" -- a black-diamond with white question mark.
Regards,
..jim
Thanks for these tests. I set tBird to show in Western encoding, default
to send in Western also. Your first email displayed these characters
properly. But this one doesn't unless I go View => Character Encoding =>
Unicode (UTF-8)
I wouldn't mind letting UTF-8 display as UTF-8. I just would like it to
use a better font. But it seems that tBird doesn't offer such
fine-tuning. At least I haven't been able to find it in Preferences. :(
--
Ralph
--------------------
A hundred welfare programs, spending more and more billions, lead to
chronic budget deficits, which lead to increase paper-money issues,
which lead to higher prices.
--Henry Hazlitt
--
KPLUG-List@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
