From: Stephen Compall <s11@member.fsf.org>
To: Mike Gran <spk121@yahoo.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: UTF-8 and new ports
Date: Thu, 14 Feb 2008 20:39:52 -0600 [thread overview]
Message-ID: <m2skzv0wp3.fsf@nocandy.dyndns.org> (raw)
In-Reply-To: <940333.54559.qm@web37904.mail.mud.yahoo.com> (Mike Gran's message of "Thu, 14 Feb 2008 13:40:35 -0800 (PST)")
Mike Gran <spk121@yahoo.com> writes:
> It seems that port types are inherently 8-bit, right?
> So to make this work, the ports will have to store and
> transmit characters as UTF-8 encoded data. The
> 'fill_input' function will have to convert UTF-32 to
> UTF-8 and then cache them, passing them 1 byte at a
> time as requested. The 'write' function will receive
> data 1 byte at a time and buffer it. It will only
> write the character when a complete UTF-32 codepoint
> has been received.
Alternatively, you could assume an 8-bit character set (either from
CTYPE, or force Latin-1), recode output to UTF-32, and either ignore
or deliver nulls or something else convenient (maybe space?) for
characters outside the 8-bit character set. This would be reasonable as
Guile characters are 8-bit anyway.
--
But you know how reluctant paranormal phenomena are to reveal
themselves when skeptics are present. --Robert Sheaffer, SkI 9/2003
next prev parent reply other threads:[~2008-02-15 2:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 21:40 UTF-8 and new ports Mike Gran
2008-02-15 2:39 ` Stephen Compall [this message]
2008-02-15 8:36 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2skzv0wp3.fsf@nocandy.dyndns.org \
--to=s11@member.fsf.org \
--cc=guile-user@gnu.org \
--cc=spk121@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).