Ya, that's what it's currently doing to some extent but we also wanted
to allow for forced language selection via the url so that we can
distribute urls on printed materials and to allow other technologies
such as search engine spiders to find all languages since they may not
be using cookies as expected.
- Jeff
On 18-Apr-08, at 11:05 AM, Marcus Bointon wrote:
On 18 Apr 2008, at 15:09, Jeffrey Sambells wrote:
Internally the app is all localized properly and translates as
necessary so I'm just trying to figure out the easiest way to add
the URL feature but can't quite get it working. Is there a way I
could use setBaseUrl() or something so that I don't have to alter
all the existing routes? I've subclassed my routes and tried
automatically prefixing /:language to them but then that breaks the
no language case.
Why not use the language that the browser requests (in
$_SERVER['HTTP_ACCEPT_LANGUAGE']), then provide an on-page override
ability that stores their preference in a cookie? That way you
wouldn't need to touch the default URL scheme or expose your
language params.
Marcus
--
Marcus Bointon
Synchromedia Limited: Creators of http://www.smartmessages.net/
UK resellers of [EMAIL PROTECTED] CRM solutions
[EMAIL PROTECTED] | http://www.synchromedia.co.uk/
