Marcus Brinkmann <[EMAIL PROTECTED]> writes: > > For the multibyte issue, console already knows all about the characters. > > So it can naturally dtrt if the term functionality is built in via > > libtermserver. That seems like the righter thing. > > The console does not know about single characters written to term. It > just converts the UTF-8 stream from the client via an iconv into the local > encoding, and outputs that.
Why is it utf8 from the client? I would have expected unicode to be the "native" language of the console (you already understand it for output)? How many different multibyte charsets are there? I think it is a reasonable rule to assume that any random eightbit charset is a unibyte charset, i.e. one byte = one character = one glyph (modulo control characters). And then make utf8 an exception to that rule, and perhaps one could handle one or two additional charsets as exceptional. /Niels _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd
