[racket] Writing UTF-16 to a socket/file

From: Robby Findler (robby at eecs.northwestern.edu)
Date: Sat Feb 12 15:39:56 EST 2011

You can work at the bytes level when you communicate on the port and
use converters to turn the bytes into strings when you want to
actually do things like match regexps or examine characters or


On Sat, Feb 12, 2011 at 2:35 PM, Gregory Woodhouse <gregwoodhouse at me.com> wrote:
> Is it possible to ensure that data written to a socket or file is encoded as UTF-16? I ask because Health Level 7 (HL7) 2.5.1 allows messages to use UTF-16 as opposed to US-ASCII, but it has to be a fixed width encoding.
> _________________________________________________
>  For list-related administrative tasks:
>  http://lists.racket-lang.org/listinfo/users

Posted on the users mailing list.