From: Sunjoong Lee <sunjoong@gmail.com>
To: Daniel Hartwig <mandyke@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: I'm looking for a method of converting a string's character encoding
Date: Thu, 3 May 2012 14:14:29 +0900 [thread overview]
Message-ID: <CAK93xhpL-ktiNpPWc-q3_FY_mMf60=4mtOyNE_h1+v8t931oBg@mail.gmail.com> (raw)
In-Reply-To: <CAK93xhpSbFQM-FuPAhQVKJgtZHZKO7b2yO--ciNZPenQA_3xkg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
Hi, Daniel;
2012/4/28 Daniel Hartwig <mandyke@gmail.com>
>
> Can you provide us with a couple of sites where http-get or
> decode-string does not work properly? Or was something else at play
> here? This would help to investigate what the issue is. (I am lazy
> today to find some, I think you must know of a few :-)
>
To cut a long story short, http-get is innocent; I had misunderstood it,
sorry.
I had summarized some issues of http-get in the post,
http://lists.gnu.org/archive/html/guile-user/2012-05/msg00005.html . With
"Example 1 - working", my problem was resolved mostly. "Example 3 - not
working" is an unsolved issue but is not an encoding problem; I think it
may be a design issue of declare-uri-header! or string->uri.
Thank you for comments.
[-- Attachment #2: Type: text/html, Size: 1206 bytes --]
next prev parent reply other threads:[~2012-05-03 5:14 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
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 [this message]
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='CAK93xhpL-ktiNpPWc-q3_FY_mMf60=4mtOyNE_h1+v8t931oBg@mail.gmail.com' \
--to=sunjoong@gmail.com \
--cc=guile-user@gnu.org \
--cc=mandyke@gmail.com \
/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).