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 It is simple to make things.
n. Maybe 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
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 impress
cket/85) 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 th
gt; this should work fine.
> >
> > Is anyone using unicode routes succesfully? Is there a trick that I'm
> > missing somewhere?
>
> Well, I've solved similar problem using iri_to_uri function from
> webhelpers before fetching Unicode data to redirect_to:
>
> 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 awesom
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 ho
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 are
