>>I think there must be a way of
converting this data into Unicode direct in SQL level. Or another better
solution?
Personally, my own "framework" still has to be CF5 and CFMX compatible,
depending on the customer's server.
The simplest way I found was to stick with ISO-8859-1 (or whatever you
need for turkish).
You just have to add this in your application.cfm:
<CFSET request.CFversion = listGetAt(server.coldfusion.productVersion, 1)>
<CFIF request.CFversion GT 5>
<CFSET request.CFversion = "MX">
<cfcontent type="text/html; charset=ISO-8859-1" RESET="no">
<cfset setEncoding("url","ISO-8859-1")>
<cfset setEncoding("form","ISO-8859-1")>
<CFELSE>
<CFSET request.CFversion = "5">
</CFIF>
--
_______________________________________
REUSE CODE! Use custom tags;
See http://www.contentbox.com/claude/customtags/tagstore.cfm
(Please send any spam to this address: [EMAIL PROTECTED])
Thanks.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 &
Flex 2.
Free Trial
http://www.adobe.com/products/coldfusion/flex2/
Archive:
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:270160
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4