New turn in my case:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" >
<xsl:decimal-format name="foo" grouping-separator=" "/>
<xsl:template match="/">
<root>
<foo>1 488</foo>
<bar><xsl:value-of select="format-number(1488,
'# ###','foo')"/></bar>
</root>
</xsl:template>
</xsl:stylesheet>
outputs:
<?xml version="1.0"?>
<root><foo>1 488</foo><bar>1 � 488</bar></root>
So it seems that everything is ok with my console.
On 21 April 2010 12:04, Michael Kay <mike(_at_)saxonica(_dot_)com> wrote:
When xsl transformation is done, for a example, in my browser
- everything is ok.
But when I fire xsltproc via console - it outputs me
something corrupted.
It's not xsltproc that's corrupting it, it's your console. If you want to
output non-ascii characters, then you are going to have to use software that
can display them properly on your screen.
Regards,
Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--