URIs can be UTF-8 with standard URL %-escaping - most browsers will
decode (and encode) that automatically and show the unicode string in
the address bar. That is especially important for languages with a
non-latin character set: without this URLs are horrible for them.
It would be awesome
Previously Mark Ramm wrote:
URIs can be UTF-8 with standard URL %-escaping - most browsers will
decode (and encode) that automatically and show the unicode string in
the address bar. That is especially important for languages with a
non-latin character set: without this URLs are horrible
On Jan 2, 2009, at 1:43 PM, Mark Ramm wrote:
URIs can be UTF-8 with standard URL %-escaping - most browsers will
decode (and encode) that automatically and show the unicode string in
the address bar. That is especially important for languages with a
non-latin character set: without this URLs
unicode strings. This
contradicts the routes manual
(http://routes.groovie.org/manual.html#unicode) which appears to say
this should work fine.
Is anyone using unicode routes succesfully? Is there a trick that I'm
missing somewhere?
Wichert.
--
Wichert Akkerman wich...@wiggy.netIt is simple
routes authors think about using encoding
prediction function from feedparser.
Is anyone using unicode routes succesfully? Is there a trick that I'm
missing somewhere?
It works fine. E.g.:
http://blog.sandbox.lt/lt/Atsitiktin%C4%97s%20mintys-Pabamb%C4%97jimai
If you will copy-paste this link
Previously Dalius Dobravolskas wrote:
Hello,
(see http://routes.groovie.org/trac/routes/ticket/85)
The first impression about this ticket is that non unicode and non
utf-8 encoded string was passed to routes. Most probably string was in
some local encoding. That's only my impression. I
) and incoming requests
data is return as ASCII strings, not decoded unicode strings. This
contradicts the routes manual
(http://routes.groovie.org/manual.html#unicode) which appears to say
this should work fine.
Is anyone using unicode routes succesfully? Is there a trick that I'm
missing somewhere
