-archive.com/catalyst@lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
--
Knut-Olav Hoven
Systemutvikler mob: +47 986 71 700
Linpro AShttp://www.linpro.no/
signature.asc
Description: This is a digitally signed message part
/
--
Knut-Olav Hoven
Systemutvikler mob: +47 986 71 700
Linpro AShttp://www.linpro.no/
signature.asc
Description: This is a digitally signed message part.
___
List: Catalyst@lists.scsys.co.uk
Listinfo: http
,
without res. just get $c-model and $c-cache like?
I don't want this $c to load any Controller modules or View modules.
anyway, Catalyst is a great framework. it ease our development a lot.
Thanks for all your work, Catalyst Team!
--
Knut-Olav Hoven
Systemutvikler mob: +47 986
On Friday 28 December 2007 17:56:45 Andrew Rodland wrote:
On Monday 24 December 2007 07:58:34 am Knut-Olav Hoven wrote:
I wasn't very clear on this, sorry.
Check my å is not inside the code, it comes from my po/mo-files
(i18n).
It looks actually more like this:
$c-redirect(
$c
msgstr Check my å
2007/12/21, Knut-Olav Hoven [EMAIL PROTECTED]:
The solution to my last problem (attached) brought up a new problem
regarding
UTF-8.
= Problem =
The following code:
$c-redirect(
$c::uri_for(
'/login',
{error_msg = Check my å
=1 is needed for somebody, this should definitely be a configurable
option.
Patch attached
--
Knut-Olav Hoven
Systemutvikler mob: +47 986 71 700
Linpro AShttp://www.linpro.no/
Index: lib/Catalyst/Plugin/I18N.pm
On Friday 21 December 2007 19:31:09 Brian Cassidy wrote:
Knut-Olav Hoven wrote:
There are some problems when translating with Catalyst::Plugin::I18N
using special unicode characters like æøå.
It got printed (both in console/debugging) and in web browser) as
unprintable characters
?
- Shouldn't URI::Escape be enough?
--
Knut-Olav Hoven
Systemutvikler mob: +47 986 71 700
Linpro AShttp://www.linpro.no/
---BeginMessage---
There are some problems when translating with Catalyst::Plugin::I18N using
special unicode characters like æøå.
It got
On Friday 21 December 2007 20:10:28 Brian Cassidy wrote:
Knut-Olav Hoven wrote:
That seems like an odd solution...
The Decode parameter is used to decode unicode characters, while the
Unicode plugin is encoding to unicode...?
This tutorial was never complete, and it's getting a little