| you use an html authoring tool and write or copy/paste your text
| and set the page encoding to utf-8. no magic.
At the moment, H T T P servers are conventionally set up to serve
files with extension ".txt" as plain text (e g, by prepending a
header "Content-Type: text/plain; charset = ascii"); and with ".html"
or ".htm" as H T M L (e g, "Content-Type: text/html; charset =
Don't we need some conventional file extensions for both plain
text and H T M L encoded in U T F 8, U T F 16, etc? E g
".utf" => text/plain; charset = utf-8
".uni" => text/plain; charset = utf-16
".utfml" => text/html; charset = utf-8
".uniml" => text/html; charset = utf-16
(So the server really can serve the pages with "no magic"!)
Why don't we see this kind of thing on the web at the moment? Am I
o o o (_|/
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:01 EDT