unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: Guile Devel <guile-devel@gnu.org>
Subject: Unicode-capable srfi-14 charsets (f49dbcadf...)
Date: Thu, 27 Aug 2009 08:20:30 -0700	[thread overview]
Message-ID: <1251386430.17414.11.camel@localhost.localdomain> (raw)

Hi-

I pushed the commit for Unicode-capable srfi-14.  Of all parts necessary
for Unicode, this patch has the largest amount of new code and is most
likely to cause compilation problems.

Since the default charsets such as char-set:lower-case are much larger
in the Unicode scenario, I had to change both the underlying structures
that hold them as well as the print format.  I also had to pregenerate
them, since it was too slow to create them at startup.  So this is also
the part of this project where I've taken the greatest liberties.

Let me know what you think.

-Mik





             reply	other threads:[~2009-08-27 15:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27 15:20 Mike Gran [this message]
2009-08-27 21:23 ` Unicode-capable srfi-14 charsets (f49dbcadf...) Andy Wingo
2009-08-27 21:32 ` Andy Wingo
2009-08-27 23:19 ` 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=1251386430.17414.11.camel@localhost.localdomain \
    --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).