credev wrote:
> well infact thats my xsl
not to nit pick but that's not the same code & you did
say it was "part". in any
case that xsl works. i output unicode hindi, arabic, thai,
japanese, etc. ok. so
it's not cf, your xml or xsl. see:
http://www.sustainablegis.com/unicode/xml/
using this code:
=====================
<cfprocessingdirective pageencoding="utf-8">
<cfquery name="getU" datasource="#dsn#">
SELECT uniText
FROM unicodeTest
ORDER BY uniLanguage
</cfquery>
<cfset
xslFile=getDirectoryFromPath(GetCurrentTemplatePath())&"test.xsl">
<cffile action="read" file="#xslFile#" variable="xslDoc"
charset="utf-8">
<cfxml variable="MyDoc">
<?xml version="1.0" encoding="utf-8"?>
<MyDoc>
<cfoutput query="getU">
<TagTR index="PK">
<TagTD libelle="Emballage">#uniText#</TagTD>
</TagTR>
</cfoutput>
</MyDoc>
</cfxml>
<cfset transformedXML = XmlTransform(mydoc, xslDoc)>
<table><cfoutput>#transformedXML#</cfoutput></table>
=====================
btw i don't like what the transform did to the vietnamese
(last row in the table).
what ver of cf? if you dump the data out of the database via
cf using utf-8
encoding, does it work? what encoding turns up in your
browser when you run your
cf page?