On 16 Feb 2007, at 15:58, Richard Jolly wrote:
To reply to myself...
Jonathan Rockway wrote:
Also, read http://www.catalystframework.org/calendar/2006/21
for unicode details.
Thanks again for this.
The encoding::warnings pragma is great, though I'm a little shocked at
how many warnings
Jason Kohles wrote:
On Feb 16, 2007, at 6:19 AM, Dave Howorth wrote:
Jonathan Rockway wrote:
Also, read
http://www.catalystframework.org/calendar/2006/21 for
unicode
details.
Nice page, thanks. I'm puzzled by one sentence:
$1, in this example,
Jonathan Rockway wrote:
Also, read http://www.catalystframework.org/calendar/2006/21
for unicode details.
The encoding::warnings pragma is great, though I'm a little shocked at
how many warnings it's uncovered.
Other questions: C::P::Unicode encodes the body in the finalize method.
That makes
Hi,
The crux of this question is what is best practice for a catalyst/DBIC
app to have it fully unicode aware.
We've got:
MySQL with charset defined as UTF8
DBIC with on connect do SET NAMES and SET CHARSET and UTF8Columns
Catalyst::Plugin::Unicode
End actions specify content type as
On 23 Jan 2007, at 18:43, Adam Jacob wrote:
On Jan 23, 2007, at 5:41 AM, Adam Sjøgren wrote:
On Sun, 14 Jan 2007 19:01:00 -0800, Adam wrote:
Personally, I wrote my own model to Xapian.
I started with Catalyst::Model::Xapian, but by now I've rewritten
everything to suit. It got me
Hi,
I've been playing with Catalyst::Model::Xapian. Works nicely, but it
seems to hide some functionality. I'd like to get information on the
match percentage, and that seems to available in Search::Xapian::MSet -
but C::M::X uses S::X::Mset::Tied, which hides it.
Unless I'm missing
On 3 May 2006, at 12:14, Chisel Wright wrote:
On Wed, May 03, 2006 at 01:04:42PM +0200, Jesper Krogh wrote:
I guess that's an issue I need to pursue further myself (getting an
up-to-date CPANPLUS package would be nice, but dh-make-perl barfs
quite
early in the process).
On which module?
