From: "Stanislav Ievlev" <stanislav.ievlev@gmail.com>
To: guile-devel@gnu.org
Subject: Re: Printing utf8 strings
Date: Wed, 10 Dec 2008 11:16:44 +0300 [thread overview]
Message-ID: <c5318fd90812100016j13d74ecdiad816565514b4d1a@mail.gmail.com> (raw)
In-Reply-To: <49dd78620812091417q4e3f9387idd4019593422ff9c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
10 декабря 2008 г. 1:17 пользователь Neil Jerram
<neiljerram@googlemail.com>написал:
> 2008/12/8 Stanislav Ievlev <stanislav.ievlev@gmail.com>:
> >
> > I think this is a bug, because different symbols has different external
> > representation ;)
>
> Not sure I'm understanding you. Clearly lack of Unicode/UTF-8 support
> is an important missing feature; are you saying something other than
> that?
Current (write) implementation "quote" random subset of non-ascii symbols,
but not all non-ascii symbols.
Are you planning to add unicode strings in next big release?
>
> >
> > Well, How to output string "as is" to terminal in example bellow?
> >
> > --
> > (define a (gettext "string" "dictionary" "ru_RU.UTF8"))
> > (write a) ;; ???
>
> Using `display', as your previous example showed. But really it's
> just luck that this works.
Please, save this "feature" in 1.8.x, otherwise it's impossible to use
guile in real applications ;)
[-- Attachment #2: Type: text/html, Size: 1690 bytes --]
prev parent reply other threads:[~2008-12-10 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 15:20 Printing utf8 strings Stanislav Ievlev
2008-12-08 15:25 ` Stanislav Ievlev
2008-12-08 15:27 ` Stanislav Ievlev
2008-12-08 15:48 ` Neil Jerram
[not found] ` <c5318fd90812080754m1f5351fbi83cef5f478bbd924@mail.gmail.com>
[not found] ` <49dd78620812091417q4e3f9387idd4019593422ff9c@mail.gmail.com>
2008-12-10 8:16 ` Stanislav Ievlev [this message]
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=c5318fd90812100016j13d74ecdiad816565514b4d1a@mail.gmail.com \
--to=stanislav.ievlev@gmail.com \
--cc=guile-devel@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).