On Fri, 11 Jan 2002 [EMAIL PROTECTED] wrote:
I think we're going to need a better way of representing the
problem. Here's what your message looks like on a UNIX system. I
imagine similar problems exist on MacOS systems, which tend to display
the wrong characters when viewing MIME text (or even HTML pages in
some cases), though I guess it probably depends on the exact program
you're using and how it's configured:
> Unicode has this wonderfull method of representing, e.g., =F6 by "o =A8"=
> [0] as
> well as by just =F6. There are also characters you couldn't represent
> otherwise, like putting the =A8 above a q. This brings up several issues=
> :
>
> 1) Does "=F6" =3D "o=A8"? They display the same. They mean the same. Th=
> ey
> probably should.
> 2) What is char 1 of "o=A8", anyway?
> a) If it's "o=A8", then what's the chartonum of that?
> b) If it's "=F6", then what's char 1 of "q=A8"?
> 3) Should we automaticly convert "o=A8" to "=F6" in
>
> [0] Note that the umlaut here is not actually a unicode combining
> character. Otherwise, it would of been combined with the
> space(!).
Regards,
Scott
********************************************************
Scott Raney [EMAIL PROTECTED] http://www.metacard.com
MetaCard: You know, there's an easier way to do that...
_______________________________________________
Freecard-general mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freecard-general
