Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] Encoding of strings in stylesheet parameters

From: Josh Canfield <joshcanfield@--------->
To:
Date: 9/2/2004 4:14:00 PM
This is more appropriate for the Xalan mailing list, as it really has
nothing to do with XSL.

But....
In Java (and likely the C version, I just haven't used it) the
encoding of the file is only needed to parse the file. The String data
will be stored in memory as UTF-16. If you are passing parameters
using the Java API then your strings too will be UTF-16, unless you
are going to pass an array of bytes that represents the text in some
other encoding.

If that doesn't help then please take the question to the Xalan
mailing list that can be found at:
http://xml.apache.org/mail.html#xalan-j-users

Josh

On Thu, 2 Sep 2004 09:40:09 -0500, Murthy, Ganesh <gmurthy@xxxxxxx> wrote:
> 
> I am using stylesheet parameters to pass values to be displayed in the
> final html.
> 
> Does Xalan support multi-byte encodings in stylesheet parameters, and if
> it does, which encoding does it expect - Does it expect parameter to be
> in the encoding of the input XML document, or of the input XSL document?
> Or is it based on the host machine?
> 
> My Input XSL is ISO-8859-1. Input XML is determined by database encoding
> (may be ISO-8859-1 or any other). Output is UTF-8 by default.
> 
> Appreciate any info.
> 
> Thanks,
> Ganesh.


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent