| 
 
Subject: RE: [xsl] using xsl:message with UTF-8 characters From: "Michael Kay" <mike@xxxxxxxxxxxx> Date: Mon, 23 Apr 2007 13:44:34 +0100  | 
OK, putting this all together, we seem to have a solution:
 
1. Trigger the unicode support for all pipe etc (default is 
cp1252 sometimes known as "ansi") with the command:
    cmd /u
2. Set the font of the console to one that has glyphs in the 
unicode range:
    - go to console system menu (Alt-Space)
    - select Properties > Font
    - select "Lucida Sans" (MS will automatically select 
"Lucida Sans Unicode" when it is needed and when it is 
available on your system)
3. Change the codepage of the console screen to use Unicode 
(default is IBM 437) with the command:
    chcp 65001
  
4. Call your commands *without* using a batch file (won't 
work anymore...). You can put your command in an environment 
variable for convenience.
5. Set the Java system property -Dfile.encoding=utf8 on the command line for
example
chcp 65001
java -Dfile.encoding=utf8 net.sf.saxon.Transform in.xml my.xsl
The Saxon patch I've issued in 
https://sourceforge.net/tracker/index.php?func=detail&aid=1705811&group_id=2
9872&atid=397617
isn't then needed: this only has the effect of giving better fallback
behaviour when the output destination doesn't support Unicode.
Thanks Abel and Andrew. You learn new things every day.
I'll copy this to the Saxon Wiki.
Michael Kay
http://www.saxonica.com/
| Current Thread | 
|---|
  | 
| <- Previous | Index | Next -> | 
|---|---|---|
| Re: [xsl] using xsl:message with UT, Abel Braaksma | Thread | Re: [xsl] using xsl:message with UT, Abel Braaksma | 
| Re: [xsl] using xsl:message with UT, Abel Braaksma | Date | Re: [xsl] using xsl:message with UT, Abel Braaksma | 
| Month |