Hi,
> Now every umlaut is always displayed as a
> questionmark, no matter if I use
> DateFormat/LSDateFormat - still for
> formatting a date that has nothing to do with
> the garbled text - or skip it.
the way CFMX handles a file usually depends on teh BOM (Byte Order Mark). It is
a tiny signature set by the editor, that tells CF whether the file is encoded
in UTF-8, ISO-something, cp1252, etc.
The only way to overcome this is to use <cfprocessingdirective
pageencoding="your_charset_here">
BUT... this has to be in _every_single_ cfm file. It won't work in
Application.cfm and it won't be downhanded to cfincludes.
The definitely best way to handle special characters (and especially Umlaut-
problems) is to use UTF-8.
First, make sure that your editor is saving the file as UTF-8 encoded. (E.g. in
Eclipse go to File - Properties - Text file encoding and set it to UTF-8
(not(!) inherited).
Then, in your Application.cfm you should make sure form and url variables are
seen as UTF-8:
<cfset setEncoding("url", "utf-8")>
<cfset setEncoding("form", "utf-8")>
Last, in your datasource settings in CF-Admin make sure MySQL is UTF-8 enabled
by adding the following parameters as connection string in the advanced
datasource settings:
useUnicode=true&characterEncoding=utf-8
There still may be problems with umlauts in cfmail. To resolve those, use the
'charset="utf-8"' attribute in cfmail tag.
Best,
Chris
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Message: http://www.houseoffusion.com/lists.cfm/link=i:4:231401
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
