|
From: | Ivan Raikov |
Subject: | Re: [Chicken-users] [Q] uri-common has problem with UTF-8 uri. |
Date: | Thu, 17 Jan 2013 09:35:36 +0900 |
OK, I took some time to investigate and I pinpointed this problem.
This appears to happen due to the use of core srfi-14 and srfi-13 in
uri-generic; its char-set operations simply don't deal with anything
beyond ASCII. Only by switching to the UTF versions utf8-srfi-14,
utf8-srfi-13 and unicode-char-sets this works:
Without patch:
$ csi -R uri-generic -P '(uri-encode-string "삼계탕")'
"�%82%BC�%B3%84�%83%95"
With patch:
$ csi -R uri-generic -P '(uri-encode-string "삼계탕")'
"%EC%82%BC%EA%B3%84%ED%83%95"
Ivan, what do you think about adding the UTF8 dependency, as per the
attached patch (against trunk)?
[Prev in Thread] | Current Thread | [Next in Thread] |