These need to be executed on every request (put in your
Application.onRequestStart() for example):
setEncoding( url, utf-8 );
setEncoding( form, utf-8 );
Make sure your DB connection is set to handle UTF-8.
If you have any accented characters or such in your templates, make
sure they have this:
cfprocessingdirective pageencoding=utf-8/
Look into Paul Hastings' i18n stuff - for formatting dates etc and
maybe resource bundles (or do everything from the DB). Using standard
Java locales and you can use this code to convert a standard locale to
a localized display name (in the locale's default language):
cfset displayLocale = REReplace( getLocaleDisplayName(
siteLocales.locale ), ' \(.*\)', '' ) /
That strips the parenthesized sub-locale so it's easier to read.
On my current project, users can choose their language and it's set
for their session (so nothing special in the URL).
Hope that helps?
Ping me off-list (sean at corfield dot org) if you need more details.
If other folks have questions on the list, I'm happy to share.
Sean
On Mon, Aug 9, 2010 at 9:37 PM, Steve Onnis st...@cfcentral.com.au wrote:
How do people handle the URLs for this? Do you have a different URL for the
different language? If so how do you deal with special language characters
in the URL string? For example i am doing some french stuff atm and they
use a lot of accented characters and as i am using SES URLs i am wondering
whats the best way to do this.
Steve
--
You received this message because you are subscribed to the Google Groups
cfaussie group.
To post to this group, send email to cfaus...@googlegroups.com.
To unsubscribe from this group, send email to
cfaussie+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/cfaussie?hl=en.
