Re: Those Darn Email Character Mappings
Re: Those Darn Email Character Mappings
- Subject: Re: Those Darn Email Character Mappings
- From: Philip Stripling <email@hidden>
- Date: Thu, 4 Jan 2001 13:48:35 -0800 (PST)
From: Paul Berkowitz <email@hidden>
Date: Thu, 04 Jan 2001 11:10:01 -0800
I don't understand why Apple insists on using a server for their mailing
lists which can't understand Macintosh key-mapping. Are they trying to tell
us that we'd all be better off if we used Windows? That's definitely how it
comes across, using a list server that insists on converting our characters
to Windows-mapping. (I presume that's what it's doing, anyway. Is this
wrong?)
I won't speak for why Apple makes its choices. However, there are more
computers in the world than Macs and Windows. And much of the Internet is
run on some flavor of UN*X or other. It is possible that the Apple servers
are screwing up, but it may also be that intervening switches, routers, and
computers are seeing characters that make no sense and that they are either
converting them or escaping them. We all know what URL encoding is.
I read my email on a FreeBSD server using emacs, so I won't see Apple
characters anyway. I see plain old ASCII. And saving the emails and ftp'ing
them to my Mac breaks the Apple characters.
If there really are no decent servers that understand Mac key-mappings,
wouldn't it be a good service to the Mac community - and maybe good business
for someone - to develop some translation software? Apple could either do it
themselves and sell it, or commission some company to do it. Surely this
mailing list is not the only potential customer for such a thing?
Maybe it is. :-> If there were a need, the market would have met it. Right?
I'm certainly no expert, but I don't think the Apple servers are the only
issue in email sent across the Internet. Servers are not the only issues.
Phil