On Mon, 2008-01-28 at 18:54 +0100, Francois Armand wrote: > I spoke to fast : it seems that in T5.0.9, even "slashes" are handled > correctly with utf-8 filter activated. This would be really great - then we should take the effort and upgrade...
Good luck to you, cheers, Martin On Mon, 2008-01-28 at 18:54 +0100, Francois Armand wrote: > Francois Armand wrote: > >> Are you sure this issue is solved in the latest version of T5? So that > >> you can even have slashes in your activation parameters? > >> > > Well, you are right : slashes are not supported. But spaces, "+", > > accented letters are well encoded/decoded > > > > I spoke to fast : it seems that in T5.0.9, even "slashes" are handled > correctly with utf-8 filter activated. > > My test (I hope it's relevant) : > * I create a page link with a context comporting all these nasty chars, > and a click to it write the good output. > * I wrote directly in the URL all these char but /, the output is what > expected. > > All in all, I can't switch to this version, there is far too others > behavior modification between the two :/ > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
