From: Mike Gran <spk121@yahoo.com>
To: guile-devel@gnu.org
Subject: Re: Wide strings
Date: Wed, 28 Jan 2009 08:44:15 -0800 (PST) [thread overview]
Message-ID: <591698.58378.qm@web37905.mail.mud.yahoo.com> (raw)
In-Reply-To: 87ljswk21l.fsf@gnu.org
Hi,
Let's say that one possible goal is to add wide strings
* using Gnulib functions
* with minimal changes to the public Guile API
* where chars become 4-byte codepoints and strings are internally
either UTF-32 or ISO-8859-1
Since I need this functionality taken care of, and since I have some
time to play with it, what's the procedure here? Should I mock
something up and submit it as a patch? If I did, it would likely be
a big patch. Do we need to talk more about what needs to be
accomplished? Do we need a complete specification? Do we need
a vote on if it is a good idea?
Pragmatically, I see that this can be broken up into three steps.
(Not for public use. Just as a programming subtasks.)
1. Convert the internal char and string representation to be
explicitly ISO 8859-1. Add the to/from locale conversion functionality
while still retaining 8-bit strings. Replace C library funcs with
Gnulib string funcs where appropriate.
2. Convert the internal representation of chars to 4-byte
codepoints, while still retaining 8-bit strings.
3. Convert strings to be a union of 1 byte and 4 byte chars.
Thanks,
Mike Gran
next prev parent reply other threads:[~2009-01-28 16:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 21:15 Wide strings Mike Gran
2009-01-25 22:31 ` Ludovic Courtès
2009-01-25 23:32 ` Neil Jerram
2009-01-26 20:24 ` Ludovic Courtès
2009-01-26 0:16 ` Mike Gran
2009-01-26 15:21 ` Mike Gran
2009-01-26 21:40 ` Ludovic Courtès
2009-01-27 5:38 ` Mike Gran
2009-01-27 5:52 ` Mike Gran
2009-01-27 9:50 ` Andy Wingo
2009-01-27 18:59 ` Ludovic Courtès
2009-01-28 16:44 ` Mike Gran [this message]
2009-01-28 18:36 ` Andy Wingo
2009-01-29 0:01 ` Ludovic Courtès
2009-01-30 0:15 ` Neil Jerram
2009-01-28 20:44 ` Clinton Ebadi
2009-01-28 23:49 ` 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=591698.58378.qm@web37905.mail.mud.yahoo.com \
--to=spk121@yahoo.com \
--cc=guile-devel@gnu.org \
/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).