From: Neil Jerram <neil@ossau.uklinux.net>
To: Mike Gran <spk121@yahoo.com>
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Benchmarking queries
Date: Mon, 21 Sep 2009 23:38:04 +0100 [thread overview]
Message-ID: <871vlzc4ab.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <1253393643.24639.190.camel@localhost.localdomain> (Mike Gran's message of "Sat, 19 Sep 2009 13:54:03 -0700")
Mike Gran <spk121@yahoo.com> writes:
> On Sat, 2009-09-19 at 01:59 +0100, Neil Jerram wrote:
>
>> 1. The files with an Emacs "coding: latin-1" comment can only be
>> compiled if I add an extra comment "coding: latin1". In other words it
>> seems that Guile (=> libunistring) only understands latin1 without the
>> hyphen. Is this expected, and is there anything we can do about it?
>
> In the string_abstraction2 branch, I'd added functionality to translate
> some common EMACS names for encodings into the proper linunistring names
> for encodings, but, that hasn't made its way into master. For latin-1,
> the name libunistring expects is ISO-8859-1. So it was my bad for not
> changing latin-1 to iso-8859-1 when I merged it from string_abstraction2
> to master.
So do you mean that
;;; -*- mode: scheme; coding: iso-8859-1; -*-
should work for both Emacs and Guile? In any case
;;; coding: latin1 -*- mode: scheme; coding: latin-1; -*-
doesn't seem so bad, so I think I'll commit for the time being with
this.
> I haven't put the Emacs aliases into master yet because I want that list
> to be in scheme code in ice-9 instead of in C code. I haven't really
> thought through the details of how that should be done.
No problem; thanks for the explanation!
Neil
next prev parent reply other threads:[~2009-09-21 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 0:59 Benchmarking queries Neil Jerram
2009-09-19 20:54 ` Mike Gran
2009-09-21 22:38 ` Neil Jerram [this message]
2009-09-22 0:28 ` 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=871vlzc4ab.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--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).