Hi,
I'm getting this behavior:
$ gsi Gambit v4.7.2
#\à
*** ERROR IN (console)@1.1 -- Invalid '#' name: "\303\240"
is that a misconfiguration on my part somehow?
Marijn
Afficher les réponses par date
Yes, you need to -:t8 for Gambit terminal IO to go UTF8, see docs.
2014-05-16 13:06 GMT+02:00 Marijn Schouten (hkBst) hkbst@gentoo.org:
Hi,
I'm getting this behavior:
$ gsi Gambit v4.7.2
#\à
*** ERROR IN (console)@1.1 -- Invalid '#' name: "\303\240"
is that a misconfiguration on my part somehow?
Marijn _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
This comment makes me wonder if ISO-8859-1 is the right default for ttys. Perhaps it would be less surprising if UTF-8 was the default.
Does anyone know of a way to autodetect the tty’s character encoding? It would be nice if xterm could be forced to send a BOM so that Gambit would autodetect the character encoding (if ttys were started with the ___CHAR_ENCODING_UTF_FALLBACK_ISO_8859_1 character encoding mode). But I see no way of doing this after a quick look at xterm’s source code.
There is a certain consistency in using ISO-8859-1 as the default for all I/O ports, so that may still be the “least surprising” default.
Thougths about this?
Marc
On May 16, 2014, at 7:28 AM, Mikael mikael.rcv@gmail.com wrote:
Yes, you need to -:t8 for Gambit terminal IO to go UTF8, see docs.
2014-05-16 13:06 GMT+02:00 Marijn Schouten (hkBst) hkbst@gentoo.org: Hi,
I'm getting this behavior:
$ gsi Gambit v4.7.2
#\à
*** ERROR IN (console)@1.1 -- Invalid '#' name: "\303\240"
is that a misconfiguration on my part somehow?
Marijn _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
On Fri, May 16, 2014 at 08:12:50AM -0400, Marc Feeley wrote:
This comment makes me wonder if ISO-8859-1 is the right default for ttys. Perhaps it would be less surprising if UTF-8 was the default.
Does anyone know of a way to autodetect the tty’s character encoding? It would be nice if xterm could be forced to send a BOM so that Gambit would autodetect the character encoding (if ttys were started with the ___CHAR_ENCODING_UTF_FALLBACK_ISO_8859_1 character encoding mode). But I see no way of doing this after a quick look at xterm’s source code.
There's always the environment variable LANG. On my machine env tell me LANG=en_CA.utf8 and the .utf8 on the en_CA clues me in.
-- hendrik
There is a certain consistency in using ISO-8859-1 as the default for all I/O ports, so that may still be the “least surprising” default.
Thougths about this?
Marc
On May 16, 2014, at 8:56 AM, Hendrik Boom hendrik@topoi.pooq.com wrote:
On Fri, May 16, 2014 at 08:12:50AM -0400, Marc Feeley wrote:
This comment makes me wonder if ISO-8859-1 is the right default for ttys. Perhaps it would be less surprising if UTF-8 was the default.
Does anyone know of a way to autodetect the tty’s character encoding? It would be nice if xterm could be forced to send a BOM so that Gambit would autodetect the character encoding (if ttys were started with the ___CHAR_ENCODING_UTF_FALLBACK_ISO_8859_1 character encoding mode). But I see no way of doing this after a quick look at xterm’s source code.
There's always the environment variable LANG. On my machine env tell me LANG=en_CA.utf8 and the .utf8 on the en_CA clues me in.
Is there a simple way to parse the LANG environment variable to determine the preferred character encoding?
Marc
On Fri, May 16, 2014 at 09:18:21AM -0400, Marc Feeley wrote:
On May 16, 2014, at 8:56 AM, Hendrik Boom hendrik@topoi.pooq.com wrote:
On Fri, May 16, 2014 at 08:12:50AM -0400, Marc Feeley wrote:
This comment makes me wonder if ISO-8859-1 is the right default for ttys. Perhaps it would be less surprising if UTF-8 was the default.
Does anyone know of a way to autodetect the tty’s character encoding? It would be nice if xterm could be forced to send a BOM so that Gambit would autodetect the character encoding (if ttys were started with the ___CHAR_ENCODING_UTF_FALLBACK_ISO_8859_1 character encoding mode). But I see no way of doing this after a quick look at xterm’s source code.
There's always the environment variable LANG. On my machine env tell me LANG=en_CA.utf8 and the .utf8 on the en_CA clues me in.
Is there a simple way to parse the LANG environment variable to determine the preferred character encoding?
Last time I looked at the list of languages for Debian (I think that was in the installer somewhere) just about every language appeared in two forms -- one with the suffix utf8 anen one without it, So I'd guess it would be useful to just test whether the LANG variable ended with utf8.
There might be exceptions to this, but if so we could wait to hear abbout them.
-- hendrik
Can't the LANG variable be of quite arbitrary content also.
It would be of value for the Gambit code to be able to know the max Unicode char it can output just as not to run into IO exceptions .. or wait, the ISO-8859-1 does not map to a linear sequence of Unicode chars, or how is it? - anyhow how avoid?
2014-05-16 15:45 GMT+02:00 Hendrik Boom hendrik@topoi.pooq.com:
On Fri, May 16, 2014 at 09:18:21AM -0400, Marc Feeley wrote:
On May 16, 2014, at 8:56 AM, Hendrik Boom hendrik@topoi.pooq.com
wrote:
On Fri, May 16, 2014 at 08:12:50AM -0400, Marc Feeley wrote:
This comment makes me wonder if ISO-8859-1 is the right default for
ttys. Perhaps it would be less surprising if UTF-8 was the default.
Does anyone know of a way to autodetect the tty's character encoding?
It would be nice if xterm could be forced to send a BOM so that Gambit would autodetect the character encoding (if ttys were started with the ___CHAR_ENCODING_UTF_FALLBACK_ISO_8859_1 character encoding mode). But I see no way of doing this after a quick look at xterm's source code.
There's always the environment variable LANG. On my machine env tell
me
LANG=en_CA.utf8and the .utf8 on the en_CA clues me in.
Is there a simple way to parse the LANG environment variable to
determine the preferred character encoding?
Last time I looked at the list of languages for Debian (I think that was in the installer somewhere) just about every language appeared in two forms -- one with the suffix utf8 anen one without it, So I'd guess it would be useful to just test whether the LANG variable ended with utf8.
There might be exceptions to this, but if so we could wait to hear abbout them.
-- hendrik _______________________________________________ Gambit-list mailing list Gambit-list@iro.umontreal.ca https://webmail.iro.umontreal.ca/mailman/listinfo/gambit-list
-
Hendrik Boom -
Marc Feeley -
Marijn Schouten (hkBst) -
Mikael