From owner-freebsd-hackers Mon Jan 12 07:33:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA18622 for hackers-outgoing; Mon, 12 Jan 1998 07:33:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA18610 for ; Mon, 12 Jan 1998 07:33:40 -0800 (PST) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id KAA21371; Mon, 12 Jan 1998 10:32:16 -0500 (EST) Date: Mon, 12 Jan 1998 10:32:16 -0500 (EST) From: John Fieber Reply-To: John Fieber To: daniel_sobral@voga.com.br cc: hackers@FreeBSD.ORG Subject: Re: Wide characters on tcp connections In-Reply-To: <8325658A.005211D4.00@papagaio.voga.com.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk On Mon, 12 Jan 1998 daniel_sobral@voga.com.br wrote: > I'd like to know if there is any provision on TCP protocol for > wide-character tcp streams. I don't know the specific answer, but the definition of a wide character itself is pretty vague. For example ISO10646 (~Unicode) has specification for both 16 and 32 bit characters, both of which would be considered "wide". Unix wide character implementations generally define "wide" as large enough to handle any locale the vendor plans to support, and it may vary from implementation to implementation. For network communications using ISO10646/Unicode, byte encodings such as UTF-7 or UTF-8 make things such as wide-character tcp streams irrelevant, and they head off endian debates in the process. -john