unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: Richard Shann <richard.shann@virgin.net>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>,
	"denemo-devel@gnu.org" <denemo-devel@gnu.org>
Subject: Re: Problem with wide characters on upgrading to guile 2.x
Date: Thu, 22 Aug 2013 14:50:15 +0200	[thread overview]
Message-ID: <CAMFYt2bVe_YhPMAxGG2CS9AozcTPM_2JEv+6ijFhW_Ft_cudoA@mail.gmail.com> (raw)
In-Reply-To: <1377171663.19958.15.camel@DebianBox.loc>

[-- Attachment #1: Type: text/plain, Size: 844 bytes --]

2013/8/22 Richard Shann <richard.shann@virgin.net>

> GNU/Denemo has a number of guile scripts in which wide characters are
> embedded in strings. These used to work in guile 1.8 but with guile 2.0
> I am seeing the following error message trying to use a string with "
> "
> in it (if that string will get through the email software)
>
> (format #t "~%=> ~A~%""  ")
> ; the throw arguments are
>
> (scm_to_stringn cannot convert wide string to output locale 84 #f #f)
>
> what is "locale 84" and how can I return to the desired behavior?
>
>
I don't know much about the internal details, but did you try
to set the locale of the environment to e.g. C.UTF-8 like that

 $ LC_ALL="C.UTF-8" guile # or your particular script

(the list of possible values can be obtained by typing "locale -a"
on modern unix systems)

[-- Attachment #2: Type: text/html, Size: 1391 bytes --]

  reply	other threads:[~2013-08-22 12:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-22 11:41 Problem with wide characters on upgrading to guile 2.x Richard Shann
2013-08-22 12:50 ` Panicz Maciej Godek [this message]
     [not found]   ` <CAMFYt2bVe_YhPMAxGG2CS9AozcTPM_2JEv+6ijFhW_Ft_cudoA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-08-22 17:09     ` Richard Shann
2013-08-22 18:10     ` Richard Shann
2013-08-22 18:45       ` Mike Gran
     [not found]         ` <1377197140.53328.YahooMailNeo-l7sgct7Iq2sbWpotXP+qY5OW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2013-08-22 19:00           ` Richard Shann
2013-08-22 19:14             ` Mike Gran
     [not found]               ` <1377198842.66709.YahooMailNeo-l7sgct7Iq2vuQS8rMknbopOW+3bF1jUfVpNB7YpNyf8@public.gmane.org>
2013-09-02  8:48                 ` Richard Shann
2013-09-02 20:01                   ` Ludovic Courtès
2013-09-03 17:53                     ` Thien-Thi Nguyen
     [not found]                       ` <874na1eqq8.fsf-FWB4FqPBZRxW9Xa+q8QyZg@public.gmane.org>
2013-09-04  8:02                         ` Richard Shann
2013-09-04 16:17                           ` [Denemo-devel] " Mark H Weaver
     [not found]                             ` <87y57cy31q.fsf-oEj8245dElT/PtFMR13I2A@public.gmane.org>
2013-09-04 16:37                               ` Richard Shann
2013-09-07  9:07                   ` Andy Wingo
     [not found]                     ` <87r4d1xanl.fsf-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
2013-09-11 16:36                       ` Richard Shann
2013-08-23 12:10 ` 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=CAMFYt2bVe_YhPMAxGG2CS9AozcTPM_2JEv+6ijFhW_Ft_cudoA@mail.gmail.com \
    --to=godek.maciek@gmail.com \
    --cc=denemo-devel@gnu.org \
    --cc=guile-user@gnu.org \
    --cc=richard.shann@virgin.net \
    /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).