From: Daniel Krueger <keenbug@googlemail.com>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: guile-user@gnu.org, Sunjoong Lee <sunjoong@gmail.com>
Subject: Re: I'm looking for a method of converting a string's character encoding
Date: Sat, 28 Apr 2012 20:29:22 +0200 [thread overview]
Message-ID: <CAAh5vOP=ZDsPMSxV49r6uxomr6D3D2-8wP-9OcMQrCzWTE5Sew@mail.gmail.com> (raw)
In-Reply-To: <87obqbwykh.fsf@gnuvola.org>
Hi,
i think there shouldn't be any transcoding of guile's strings, as
strings are internal representation of characters, no matter how they
are encoded. So the only time when encoding matters is when it passes
it's `internal boundarys', i mean if you write the string to a port or
read from a port or pass it as a string to a foreign library. For the
ports all transcoding is available, and as said, the real
representation of guile strings internally is as utf8, which can't be
changed. The only additional thing i forgot about are bytevectors, if
you convert a string to an explicit representation, but afaik there
you also can give the encoding to use.
Am I wrong?
- Daniel
On Sat, Apr 28, 2012 at 7:33 PM, Thien-Thi Nguyen <ttn@gnuvola.org> wrote:
> () Sunjoong Lee <sunjoong@gmail.com>
> () Sun, 29 Apr 2012 01:38:28 +0900
>
> http-get is innocent but I need encoding converter yet.
>
> It sounds like a good exercise (that would flush out bugs and
> raise confidence in the infrastructure) would be to implement
> an iconv-workalike program in Scheme. Maybe one already exists?
>
next prev parent reply other threads:[~2012-04-28 18:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 21:13 I'm looking for a method of converting a string's character encoding Sunjoong Lee
2012-04-28 1:40 ` Sunjoong Lee
2012-04-28 16:38 ` Sunjoong Lee
2012-04-28 17:33 ` Thien-Thi Nguyen
2012-04-28 18:29 ` Daniel Krueger [this message]
2012-04-28 19:54 ` Thien-Thi Nguyen
2012-04-28 20:55 ` Eli Zaretskii
2012-04-28 22:42 ` Sunjoong Lee
2012-04-29 0:25 ` Sunjoong Lee
2012-04-30 10:18 ` Daniel Krueger
2012-04-30 12:21 ` Eli Zaretskii
2012-05-03 22:34 ` Ludovic Courtès
2012-05-02 3:57 ` Daniel Hartwig
2012-05-03 5:14 ` Sunjoong Lee
2012-05-03 22:31 ` 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='CAAh5vOP=ZDsPMSxV49r6uxomr6D3D2-8wP-9OcMQrCzWTE5Sew@mail.gmail.com' \
--to=keenbug@googlemail.com \
--cc=guile-user@gnu.org \
--cc=sunjoong@gmail.com \
--cc=ttn@gnuvola.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).