From: "Игорь Гайсин" <igor.gajsin@tts.tv>
To: "Dima" <dima@minignu.minidns.net>
Cc: guile-user@gnu.org
Subject: Re:unicode support
Date: Mon, 31 Mar 2014 12:19:58 +0400 [thread overview]
Message-ID: <87fvly230x.fsf@WS-IT-19-15.tts.loc> (raw)
In-Reply-To: <20140331051838.E1F5413FB97@raspberrypi>
Hi, dmitriy. Try to add this line to head your scripts
(setlocale LC_ALL "")
(set-port-encoding! (current-input-port) "utf-8")
(set-port-encoding! (current-output-port) "utf-8")
Dima <dima@minignu.minidns.net> writes:
> Hi.
> Did something change from guile 1.8.x to 2.0 with regards to unicode support.
>
> I have a script that has strings written on russian without much care, and it does not work on 2.0.
>
> I want to make sure whether there are changes in guile or something else.
>
> Thanks, regards,
> Dima.
--
Игорь Гайсин
Email: igor.gajsin@tts.tv
Телефон: 8-499-967-77-97 (4096)
Должность: Системный администратор ООО "Бриллианит"
next prev parent reply other threads:[~2014-03-31 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 5:18 unicode support Dima
2014-03-31 8:19 ` Игорь Гайсин [this message]
2014-03-31 12:36 ` Ludovic Courtès
2014-03-31 21:41 ` Mark H Weaver
2014-04-02 7:48 ` Nala Ginrut
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=87fvly230x.fsf@WS-IT-19-15.tts.loc \
--to=igor.gajsin@tts.tv \
--cc=dima@minignu.minidns.net \
--cc=guile-user@gnu.org \
/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).