Actually I can't find a browser that encodes the 'é' incorrectly...
Tested chrome dev, firefox stable, ie8...
What browser does this for you?
--
Eisenberger Tamás ta...@eisenberger.hu
On Sun, 2011-03-13 at 14:46 +, ryan lauterbach wrote:
The %E9 is what the browsers change the character
://wiki.catalystframework.org/wiki/tutorialsandhowtos/using_unicode
--
Eisenberger Tamás ta...@eisenberger.hu
On Fri, 2011-03-11 at 23:50 +, ryan lauterbach wrote:
Hi,
I've read some threads about unicode, utf8 and query parameters but I
don't understand it enough to fix on my own, so
of C::P::U::E because
it should be the first getting the input!
--
Eisenberger Tamás ta...@eisenberger.hu
On Sat, 2011-03-12 at 11:32 +, Ryan Lauterbach wrote:
So utf8::is_utf8 means that the string has multiple bytes in one
character.
Of course $enc-decode() fails to decode
encoding of the ISO-8859-1 encoding of Kévyn. Therefore the
correct RFC 3986 compliant URI-encoding for Kévyn would be K%C3%
A9vyn.
--
Eisenberger Tamás ta...@eisenberger.hu
On Sat, 2011-03-12 at 22:05 +, ryan lauterbach wrote:
On 12 March 2011 22:04, ryan lauterbach r...@radianit.com wrote:
2011
review your test, or explain a real word
situation of the problem you facing?
I actually use utf8 strings in url's now without problems :)
--
Eisenberger Tamás ta...@eisenberger.hu
On Thu, 2011-03-03 at 21:33 -0800, Bill Moseley wrote:
Does this help?
On Thu, Mar 3, 2011 at 2:38 PM, Erik Wasser
Yeah :) Absolutely agree :D
--
Eisenberger Tamás ta...@eisenberger.hu
On Fri, 2010-04-23 at 00:29 +0200, Aristotle Pagaltzis wrote:
* Oleg Pronin syber@gmail.com [2010-04-21 18:40]:
Guys, is Catalyst a senior system ?
I think that creator of Moose, and some similar shit
Hy!
I think your problem is that there is a difference between how an url
dispatched to an action, and how forward finds the action to forward to...
so for example, if you have a controller (YourApp::Controller::Foo) with
an index method you can access it with the url path /foo, but you should
