This is looking like the right path. I'm getting tons of warnings like
Bytes implicitly upgraded into wide characters as iso-8859-1, which
should lead me to a solution. :)
Thanks!
encoding::warnings might be for your help. Not sure if it works
actually, but the documentation would be a great
Yup, here's a script that confirms the damage:
#!perl
use Template;
#use utf8;
my $foo = q{The モーニング娘。 are cool.};
print Print says: $foo\n;
my $tt = Template-new;
$tt-process(\*DATA, { foo = $foo });
__DATA__
[% foo %] urlencodes to [% foo | uri %]
__END__
If you run it with use utf8
It's stylistic. Please see page 18 of Perl Best Practices for details.
Rodney Broom wrote:
Another thing to watch out for :) is 80 (or 78) column lines.
Is this a functional thing, or stylistic? I'm not seeing anything in the
manual related to width.
--
Regards,
Jonathan
Sorry for spamming the list with this, but it turns out the bug is fixed
in TT 2.15b :)
http://www.template-toolkit.org/pipermail/templates/2006-May/008648.html
For some reason I thought that 2.15 came out *after* YAPC::NA (and
therefore that 2.15b was older). However, I was wrong :)
Regards,
August R. Wohlt wrote:
Hiya Justin et al,
I used to use TT2 about 5 years ago, but switched to mason about 3 years
ago. One of the better choices I've made IMHO. For catalyst, its setup
is straightforward:
Oh wow. That's evil, but very, very neat. I'm not a fan of the Mason way of
Rodney Broom wrote:
The reason for -u diffs...
Aha, -u. New patches atached.
Right, since we ended up about 15 messages deep in a thread, can you re-post
this as a diff -urP to a fresh thread so we can discuss it properly?
The reason for the 80 char limit is effectively stylistic right up
you mean to get as many chat windows as poss ;-)
On 8/13/06, Matt S Trout [EMAIL PROTECTED] wrote:
Rodney Broom wrote:
The reason for -u diffs...
Aha, -u. New patches atached.
Right, since we ended up about 15 messages deep in a thread, can you re-post
this as a diff -urP to a
Rodney Broom wrote:
From: Matt S Trout [EMAIL PROTECTED]
Rodney Broom wrote:
The reason for -u diffs...
Aha, -u. New patches atached.
Right, since we ended up about 15 messages deep in a thread, can you re-post
this as a diff -urP to a fresh thread so we can discuss it properly?
The
Rodney Broom wrote:
This is a fix to Catalyst::Utils::ensure_class_loaded() and the call to it
that was causing classes to always get reloaded.
I have no specific test cases. My testing was to add debugging while tracking
other problems and see that load was always happening, even when
Ok, being stupid today
I have a simple controller named directory. It has a default method.
So things named
http://localhost:3000/directory
should go to it. Now I want to capture
http://localhost:3000/directory/other/things/...
that is, I want this controller to handle
Joe Landman wrote:
Ok, being stupid today
I have a simple controller named directory. It has a default method.
So things named
http://localhost:3000/directory
should go to it. Now I want to capture
http://localhost:3000/directory/other/things/...
that is, I want this
I have an idea for a great Catalyst based project that can really show
the power of Catalyst and spawn some extra projects from this and give
Catalyst some coverage.
The idea is to build a framework for User Generated Content type of
websites. All of those website usually have many features in
Solution... see below ...
Matt S Trout wrote:
Joe Landman wrote:
Ok, being stupid today
I have a simple controller named directory. It has a default method.
So things named
http://localhost:3000/directory
should go to it. Now I want to capture
Joe Landman wrote:
Solution... see below ...
The hint I needed was that the regex'es are passed in via
$c-request-snippets. This controller definition works nicely.
sub base : Regex('^directory(.*)$') {
my ( $self, $c ) = @_;
my ($rest);
$rest =
Matt S Trout wrote:
Yes, but you still don't need to use a regex action.
sub base :Path {
my ($self, $c, @parts) = @_;
my $rest = join('/', @parts);
...
}
If you're using a Regex action, always first ask yourself is there an
easier way to do this?. The answer is almost always
Joe Landman wrote:
Matt S Trout wrote:
Yes, but you still don't need to use a regex action.
sub base :Path {
my ($self, $c, @parts) = @_;
my $rest = join('/', @parts);
...
}
If you're using a Regex action, always first ask yourself is there an
easier way to do this?. The answer
Kevin Old wrote:
In the actual Mason view treat it just like any other Mason page.
The $c object is available and the stash can be called like %
$c-stash %.
Its even easier.. $c-stash-{name} directly matches:
%args
$name
/%args
No need to fiddle around with $c for that.
Jesper
--
Jesper
I'm working on something right now for a client with this. He is okay with me
returning code to the community that is not part of his core business, so stuff
like wiki's, forums, moderation (voting and karma), tagging, lightweight CMS,
etc he is cool with. However I've already been working on
18 matches
Mail list logo
