On Mon, Apr 21, 2008 at 10:03:53PM +0300, Roumen Petrov wrote: > Vincent Lefevre wrote: > > On 2008-04-21 10:19:25 -0400, Daniel Veillard wrote: > >> On Tue, Apr 15, 2008 at 01:28:45PM +0200, Vincent Lefevre wrote: > > [...] > [SNIP] > > This really depends on where the arguments come from. If the encoding > > of the arguments is regarded as fixed (to UTF-8) by xsltproc and the > > user types the arguments, then this will work under UTF-8 locales, > > but not under ISO-8859-1 locales, for instance. So, the process is > > non-predictable in this case too. That's why I suggested an option. > > > > If the call to xsltproc appears in a shell script and the user wants > > predictability, then the script should switch to fixed locales at the > > beginning, in general C or POSIX locales. As 8-bit characters aren't > > defined in such locales, accepting UTF-8 encoded strings could be OK > > in these locales (there would be no clash with what the user types). > > > > If I remember well xsltproc program code don't call setlocale and in > this case program run in "C" locale :-/ (Now I don't have time to check > program code).
Certainly true. None of the libxml2 or libxslt code ever touch the locale. And I intent to keep it that way, Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ [EMAIL PROTECTED] | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ _______________________________________________ xslt mailing list, project page http://xmlsoft.org/XSLT/ [email protected] http://mail.gnome.org/mailman/listinfo/xslt
