sub lang : Chained('/') CaptureArgs(1) PathPart(''){
my ($self, $c, $lang) = @_;
# need to check that $lang is valid and handle that here
if (valid($lang)) {
} else {
}
}
sub doit : Chained('lang') Args(0) {
my ($self, $c) = @_;
}
this now matches /*/doit, and doit needs to be able
* Daniel McBrearty [EMAIL PROTECTED] [2006-08-25 12:10]:
in fact there are a number of ways the language can be
detected. For me, these are (highest priority first) ... :
1. the uri
2. the session (maybe, i'm thinking about this ... the argument
is that the user shouldn't have to manually
that's what I'm thinking AP. cheers.
lang Chained('/) looks in the uri. If it succeeds, it sets
stash/session too. If it fails it redirects to /default which checks
session and redirects, or browser then set session and redirect. If
all else fails show a chooser page.
On 8/25/06, A. Pagaltzis
Hello All,
I've just put out a new release of the ConfigLoader plugin. Nothing on
the surface has changed. Underneath, however, the guts of the config
file loading has been extracted out into a separate module: Config::Any.
Hopefully other apps and/or modules will find this new package useful.
I have my content-type header set to ISO-8859-1 because I'm dealing with
legacy data from a latin1 encoded MySQL database (otherwise data from the
database is not displayed correctly in the browser). There's a form on my
site for searching users by attribute. Now here's the problem:
Doing a
What happens if you 'use encoding iso-8859-1' at the top of the script
that accepts this data?
BTW my suggestion is to not send latin-1 to the browser. Use the
Encode module to convert from latin-1 bytes to perl characters, and
then use the C::P::Unicode module to send UTF-8 to the browser.
