From owner-freebsd-hackers Mon Jan 19 11:37:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09321 for hackers-outgoing; Mon, 19 Jan 1998 11:37:23 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09313 for ; Mon, 19 Jan 1998 11:37:17 -0800 (PST) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.8/8.8.8) id MAA00783; Mon, 19 Jan 1998 12:37:15 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpd000759; Mon Jan 19 12:37:08 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id MAA05333; Mon, 19 Jan 1998 12:37:06 -0700 (MST) From: Terry Lambert Message-Id: <199801191937.MAA05333@usr08.primenet.com> Subject: Re: Wide characters on tcp connections To: daniel_sobral@voga.com.br Date: Mon, 19 Jan 1998 19:37:06 +0000 (GMT) Cc: louie@TransSys.COM, hackers@FreeBSD.ORG In-Reply-To: <83256591.0040AFF0.00@papagaio.voga.com.br> from "daniel_sobral@voga.com.br" at Jan 19, 98 08:50:36 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > > This is similar to asking if the UNIX filesystem has provisions > > for storing "wide characters in files"; the FS doesn't care > > what's inside it's files. > > Though that's technically right, one might feel the need for a standard if > the files he writes are going to be read by other people's programs. Of > course TCP, by itself, provides all support you need to send the > characters, but ignoring the practical problems would be akin to keeping to > IP (vs TCP or UDP) because that's all you _really_ need... The issue is one of stream synchronization. This is my main problem with UTF over non-error-checked links. If you have an implicit value boundry, then you are guaranteed a synchronized stream. Re: the FS example: a better example is to perhaps ask if a UNIX FS has provisions for storing "wide characters" (or preferrably, 16bit wchar_t values from ISO10646 aka Unicode) in *directory entries* (the current answer is "no, namei is too stupid"). Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.