> So do you mean that
>
> ;;; -*- mode: scheme; coding: iso-8859-1; -*-
>
> should work for both Emacs and Guile?
Yes. In http://www.iana.org/assignments/character-sets the names
of encodings labeled as "preferred MIME name" are likely to be
understood by libunistring. There is some overlap wi
Mike Gran 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
>> h
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, a
I had to make some changes to the benchmark code, to persuade
benchmark-guile to run to completion within a reasonable time. Full
patch is below for review; there are 3 particular points/queries.
1. The files with an Emacs "coding: latin-1" comment can only be
compiled if I add an extra comment "
