Re: Output Encoding via <xsl:result-document>

Hi Don,

it seems that Oxygen is applying fallback character encoding which, by
default, is CP-1252 (check Preferences > Encoding). Usually, fallback
character encoding is triggered when source documents are non-XML or encoding
is not determined by the file type. So maybe you should check your source
document first.



Detlef



De: Don Smith dsmith_lockesmith@xxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Enviado el: viernes, 14 de abril de 2023 23:57
Para: XSLT <xsl-list@xxxxxxxxxxxxxxxxxxxxxx>
Asunto:  Output Encoding via <xsl:result-document>



I've inherited a XSLT 2.0 transformation that outputs a CSV file using the
result-document instruction like so:



<xsl:result-document href="blah.xml" method="text">



On my computer, the @method setting resulted in a text document encoded in
CP-1252 (according to the Oxygen XML Editor). But the source document for the
transform is XML in UTF-8 and I'm getting reports of unsupported characters in
CP-1252. I want to change the encoding to UTF-8 to support all characters. So
I changed the result-document instruction to be:



<xsl:result-document href="blah.xml" method="xml" encoding="UTF-8"
omit-xml-declaration="yes">



And according to Oxygen the output encoding is STILL CP-1252 and it won't open
the file due to unsupported characters. I've checked the encoding with various
other apps (like NotePad++) and they say the encoding is UTF-8.



Something weird is going on that I don't understand. Why isn't the encoding
instruction encoding="UTF-8" having effect?



Thanks,



Don

XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>

EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/2507674>  (by
email <> )