[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[JDEV] encoding
In reply to your message from the not too distant future: next Friday AD
Reply-to: belg4mit@mit.edu
Return-receipt-to: belg4mit@mit.edu
Organization: a) Discordia b) none c) what's that?
Content-Typo: gibberish, charset=ascii-art
Date: Fri, 30 Jul 1999 15:00:09 EDT
From: belg4mit
>What I'm really wondering here is, this is just character encodings,
>correct? I mean, all the same characters are still there in ANY
>encoding(unless it's a severly restricted one), they are just encoded
>differently. If it's all UTF-8 you can still do all of the korean,
>japanese, english, etc, characters just fine, they are just encoded in
>UTF-8. It's just a language and font display issue at that point. So
>what is the problem with using the XML-forced UTF-8 encoding?
This is more or less how I see it. I think we (should) all agree by nomw
that as long as the XML parser knows it's getting 8-bit (eg; UTF) it comes
down to your case. I see the discussion now as how to tell the client what
it needs to do to display the data, hence my directive view for encoding.
--
Please take the time to answer the simple survey at:
http://www.pthbb.org/cgi.bin/survey/
* __ * .
\ | / . . . . . ((_
_____ . . .
-- / \ -- . . . + . . _/\
oooooooooo. | * . . . * / ;M\_ .
.oooooooooooo.oo. . . . . /\ . / :IMM\
..oooooooooooo..oo. Jerrad Pierce /\ / \ / ;IIWMM
..oooooooooo....... 209 North Street + / \ / \ . / ;IIIIWM
...ooooooooo....... Randolph, MA 02368 / \ \ ___/ :;IIIIIWM
....ooo....o....... / \ \ / :: ;;IIIMI
.....ooo......... http://www.pthbb.org / \ \ : :::;IIIM
..ooooooo.... __________________________ || || ::.....::::::
MOTD on Sweetmorn, the 65th of Confusion, in the YOLD 3165:
Born Free. . . . .Taxed to Death