Marc Höper wrote:
> OK. Then I have to convert the pages with another tool, or I hope that
> every user can use my encoding.
On UNIX like systems sablot links the iconv library, which supports almost
whatever encoding. On Windows you are limited to encoding supported by sablot
itself (e.g. utf-8, utf-16, iso-8859-1).
If an encoding of your choice is supported, all you need is to declare it in
input files
(<?xml version="1" encoding='xxx'?>).
The output encoding is specified via <xsl:output encoding="yyy"/> and when
using xml or html output methods it is also declared in output files (<?xml
version="1" encoding='xxx'?> or
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=yyy">)
automatically, so that other user have no problems with encoding of your
output.
Only if you run sablot on Windows and use an unsupported code page (? cp1252),
you have to convert your sources with an external tool. A good news: the range
of code pages supported without iconv should be extended in future.
Hope this help
Petr
--
Petr Cimprich
Ginger Alliance Ltd.
www.gingerall.com
