From: Linas Vepstas <linasvepstas@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guile-user@gnu.org, guile-devel@gnu.org
Subject: Re: GNU Guile 1.9.2 released (alpha)
Date: Mon, 17 Aug 2009 13:29:27 -0500 [thread overview]
Message-ID: <3ae3aa420908171129y3d3548bclb3193c740effc74@mail.gmail.com> (raw)
In-Reply-To: <87iqgpkyzv.fsf@gnu.org>
2009/8/15 Ludovic Courtès <ludo@gnu.org>:
> ** Incomplete support for Unicode characters and strings
>
> Internally, strings are now represented either in the `latin-1'
> encoding, one byte per character, or in UTF-32, with four bytes per
> character.
Will this eventually move to UTF8? European languages typically
use only a small handful of non-latin symbols, typically just misc
punctuation. I recent dump of voice-of-america radio broadcasts
I ran through guile used misc UTF8 punctuation ... backwards-facing
double-quotes, ellipsis, etc. I'd hate to see this common case
blow up to 32-bits per char just to accommodate stray punctuation.
--linas
next prev parent reply other threads:[~2009-08-17 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 13:06 GNU Guile 1.9.2 released (alpha) Ludovic Courtès
2009-08-17 18:29 ` Linas Vepstas [this message]
2009-08-17 19:19 ` Mike Gran
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=3ae3aa420908171129y3d3548bclb3193c740effc74@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=ludo@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).