From: Noah Lavine <noah.b.lavine@gmail.com>
To: Kejia柯嘉 <w.kejia@gmail.com>
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: how to decode uri containing non-ascii characters?
Date: Fri, 2 Nov 2012 09:42:37 -0400 [thread overview]
Message-ID: <CA+U71=Pp+_uADAok=bSui-FOCKvBHHshsU03d-KpMKEDewnMtQ@mail.gmail.com> (raw)
In-Reply-To: <CALE-FfNZBPy1DA+txJxOTALyDZCb+MjnhB0wkofBc4z-bmWSYA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
It may be that Guile is decoding it correctly, but your terminal program is
unable to display the characters. At least, I often see '?' in place of
characters that my terminal can't display.
I'm not sure how to test this right now, though.
Noah
On Fri, Nov 2, 2012 at 8:43 AM, Kejia柯嘉 <w.kejia@gmail.com> wrote:
> hi balafonrut,
>
> no error message, it just restored to several '?'. thank you.
>
> 在 2012年11月1日星期四，nalaginrut 写道：
>
> On Thu, 2012-11-01 at 20:03 -0400, Kejia柯嘉 wrote:
>> > hi all,
>> >
>> > in an html textarea, i input some chinese text, and receive the text
>> from
>> > the http request body. i tried to use uri-decode to restore the text,
>> but
>> > failed:
>> > (display (uri-decode "%E5%B0%8F"))
>> >
>>
>> It's OK in my system.
>> --------------cut---------------
>> scheme@(guile-user)> (display (uri-decode "%E5%B0%8F"))
>> 小scheme@(guile-user)>
>> --------------end---------------
>>
>> Can you show the error message?
>>
>> > any suggestions?
>> >
>> > thanks a lot for your helps.
>> >
>> > kejia
>> >
>> > ☵☯☲
>>
>>
>>
>
> --
>
> ☵☯☲
>
>
[-- Attachment #2: Type: text/html, Size: 1772 bytes --]
next prev parent reply other threads:[~2012-11-02 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 0:03 how to decode uri containing non-ascii characters? Kejia柯嘉
2012-11-02 2:22 ` nalaginrut
2012-11-02 12:43 ` Kejia柯嘉
2012-11-02 13:42 ` Noah Lavine [this message]
2012-11-02 16:45 ` Mark H Weaver
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='CA+U71=Pp+_uADAok=bSui-FOCKvBHHshsU03d-KpMKEDewnMtQ@mail.gmail.com' \
--to=noah.b.lavine@gmail.com \
--cc=guile-user@gnu.org \
--cc=w.kejia@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).