From owner-freebsd-hackers Mon Jan 19 18:41:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18426 for hackers-outgoing; Mon, 19 Jan 1998 18:41:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from whizzo.TransSys.COM (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18401 for ; Mon, 19 Jan 1998 18:41:20 -0800 (PST) (envelope-from louie@whizzo.TransSys.COM) Received: from whizzo.TransSys.COM (localhost.transsys.com [127.0.0.1]) by whizzo.TransSys.COM (8.8.8/8.7.3) with ESMTP id VAA20667; Mon, 19 Jan 1998 21:40:33 -0500 (EST) Message-Id: <199801200240.VAA20667@whizzo.TransSys.COM> X-Mailer: exmh version 2.0.1 12/23/97 To: daniel_sobral@voga.com.br cc: hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Wide characters on tcp connections References: <83256591.0040AFF0.00@papagaio.voga.com.br> In-reply-to: Your message of "Mon, 19 Jan 1998 08:50:36 -0300." <83256591.0040AFF0.00@papagaio.voga.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 19 Jan 1998 21:40:32 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk > 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... What? While you might agree to implement your own transport protocol directly on IP or using UDP to do multiplexing with your own reliable transport, none of this makes it any easier to move multibyte characters between machines. If you're looking for a standard way to move multibyte characters, then choose any one of a number of encodings already used to store multibyte characters in files. louie