http://play-perl.org/quest/5134cdc18e0a96450f000038
There was a discussion about this on #catalyst-dev and in general people seem to think its ok. Bill, are you up to giving the work a try? I'd be happy to mentor you. I don't think its killer work, but would really help John ----- Original Message ----- > From: ""Luis E. Muñoz"" <[email protected]> > To: John Napiorkowski <[email protected]>; The elegant MVC web framework > <[email protected]> > Cc: > Sent: Monday, March 4, 2013 11:38 AM > Subject: Re: [Catalyst] Backlog for proposed changes in next Catalyst release > > > On Mar 4, 2013, at 11:12 AM, John Napiorkowski wrote: > >> Bill, >> >> I'd be open to it, if it seems like we always just need to add this. > I'm not enough an expert of unicode to understand the drawbacks, or why this > was done as a plugin in the first place. Is there a drawback, for example to > having it core? >> >> I can see at the beginning having stuff like this as stand alone dists, > since it lets you be more agile in fixing issues with it, and all that but if > this is stable then I can see just making it core. > > Correctly understanding and handling character encodings can be tricky. It's > quite common to encounter applications that behave erratically when fed > non-ASCII input (with a last name that contains such characters, I would > know). > > That say, I cannot see how including that functionality in the core would be > a > bad thing. > > Best regards > > -lem >
_______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
