Re: TECH: RFC 1345 (was Re: TECH: Testing again, no new on-topic content (was Re: "Language Creation" in your conlang))
|From:||Paul Bennett <paul-bennett@...>|
|Date:||Tuesday, November 18, 2003, 19:30|
On Tue, 18 Nov 2003 13:34:56 -0500, John Cowan <jcowan@...>
> Paul Bennett scripsit:
>> My newest wish is that applications would openly and easily import and
>> export character sets in RFC 1345 format, so that I could create my own
>> bit encoding (or we could create a pan-Conlang-L 8-bit encoding?) that
>> could be imported into the email clients and browers of interested
> It's hard to get these things to interoperate, because there is such a
> variety of mail clients in use.
GAAAAAAAHHHHHH! ARRR EFFFFF SEEEEEEEE! A method for transferring encodings
has been standardised. Why, then, does it make sense to willfully ignore
This isn't directed at anyone here, btw, but I felt the need to vent.
> Better to push for clean UTF-8 paths
> through listservs and UTF-8-aware clients. Most people are using closed
> clients and have two choices: wait until the vendor fixes things (if
> ever), or move to a more reasonable client such as Mozilla Thunderbird.
Well, given my druthers, I'd post entirely in UTF-8 and leave it up to any
interested party to upgrade themselves, but that strikes me as somewhat
impolite, plus prone to being mangled by the listserv. Who actually runs
the listserv itself, by the way? Is there a chance that the A0 -> 20
conversion is a configurable option in the listserv software?