From: Ken Raeburn <raeburn@raeburn.org>
To: Mike Gran <spk121@yahoo.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: frozen!
Date: Sat, 10 Oct 2009 10:43:13 -0400 [thread overview]
Message-ID: <A601BE10-0E83-4D3B-8C26-DF953D5B8736@raeburn.org> (raw)
In-Reply-To: <92B05ECF-EEE9-41B9-BE0F-C25778E10067@raeburn.org>
On Oct 9, 2009, at 03:54, Ken Raeburn wrote:
> The code in regexp.test tries the suffixes ".ISO-8859-1" and
> ".iso88591" when selecting locale names. I take it that means
> there's inadequate standardization on the naming of encodings across
> systems? Well, when I make it try ".ISO8859-1", most of the tests
> pass on Mac OS X. The "string of all chars" ones still fail; I'm
> looking into those.
The "string of all chars" test calls setbinary before performing the
test. The documentation for setbinary says it sets the encoding for
current input, output and error streams to ISO-8859-1, as well as
making it the default for new ports. Is that supposed to affect make-
regexp and regexp-exec as well?
If I replace the call with a call to set-latin-1 (modified to try
".ISO8859-1", as described above), which sets the locale, the test
passes on the Mac.
Ken
next prev parent reply other threads:[~2009-10-10 14:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 19:47 frozen! Andy Wingo
2009-10-06 21:00 ` frozen! Neil Jerram
2009-10-06 21:35 ` frozen! Mike Gran
2009-10-06 21:45 ` frozen! Ludovic Courtès
2009-10-06 22:07 ` frozen! Ken Raeburn
2009-10-06 22:25 ` frozen! Ludovic Courtès
2009-10-09 7:54 ` frozen! Ken Raeburn
2009-10-10 14:43 ` Ken Raeburn [this message]
2009-10-12 13:56 ` frozen! Mike Gran
2009-10-12 17:31 ` setbinary Ludovic Courtès
2009-10-18 10:27 ` frozen! Andy Wingo
2009-10-06 21:49 ` frozen! Ludovic Courtès
2009-10-18 10:33 ` frozen! Andy Wingo
2009-10-18 13:54 ` frozen! 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=A601BE10-0E83-4D3B-8C26-DF953D5B8736@raeburn.org \
--to=raeburn@raeburn.org \
--cc=guile-devel@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).