David Bertoni wrote:
If you're using the XalanTransformer class, you can call
XalanTransformer::setOmitMETATag(eOmitMETATagYes) to accomplish this.
If you're using the command line executable, you can use the -m
command line option.
I am using the XalanTransformer class, and when I call this
Ivanova wrote:
Hi. I want to transform XML to HTML using Xalan-C++ 1.10.
And I have such xml (fragment):
текст
And after XSL transformation, attribute values (written in russian
language) become coded into HTML escape sequence:
текст
Well, that's probably a bug, although it's hard to say
Hi. I want to transform XML to HTML using Xalan-C++ 1.10.
And I have such xml (fragment):
текст
And after XSL transformation, attribute values (written in russian
language) become coded into HTML escape sequence:
текст
But text, inside attribute stayed unchanged (and that's right).
How
Björn Tietjens wrote:
Hello,
i am trying to do the following with xalanc:
xalan -t -v -e iso-8859-5 -o outfile xmlfile xslfile
and the encoding of the xmlfile is UTF-8
that is I want to make a transformation and safe the output in
iso-8859-5 encoding.
The transformation works fine but for
Hello,
i am trying to do the following with xalanc:
xalan -t -v -e iso-8859-5 -o outfile xmlfile xslfile
and the encoding of the xmlfile is UTF-8
that is I want to make a transformation and safe the output in
iso-8859-5 encoding.
The transformation works fine but for some reason the new
.
> Btw, what is the reason XalanTransformer is designed to use UTF-8 as the
> default (for output encoding) but XalanDOMString uses UTF-16 (for input
> encoding)?
I don't understand this comment. XalanTransformer has not been designed
to use UTF-8 as the default. Rather, the
parameter=="true"
then do this). Isn't that true? Is there a workaround in that case?
Btw, what is the reason XalanTransformer is designed to use UTF-8 as the
default (for output encoding) but XalanDOMString uses UTF-16 (for input
encoding)?
Thanks,
Ganesh.
-Original Message---
> I am using stylesheet parameters to pass values to be displayed in the
> final html.
>
> Does Xalan-C 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 d
Hi,
I am using stylesheet parameters to pass values to be displayed in the
final html.
Does Xalan-C 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
he method depends on the initial output
element
2. If an invalid/unsupported output encoding is specified then UTF-8 is used
So to be absolutely right, you still need to have a
getLastOutputEncoding()/Method(), because this information is only really
available after the transformation has taken plac
Hi Mark,
> > One thing we could do would be to put another accessor on
XalanTransformer
> to return the actual encoding of the last transformation. If that sounds
> > reasonable to you, please file a bugzilla request for an enhancement.
> Yes, that's about the only reas
> One thing we could do would be to put another accessor on XalanTransformer
> to return the actual encoding of the last transformation. If that sounds
> reasonable to you, please file a bugzilla request for an enhancement.
Yes, that's about the only reasonable way that I could
exist, but it is the pair to
> setOutputEncoding AFAICT -- which overrides what's specified in the
> stylesheet, rather than reporting the actual encoding used during the
(last)
> transformation. Would there be any (reasonably easy, preferably!) way to
> eek this information out?
ir to
setOutputEncoding AFAICT -- which overrides what's specified in the
stylesheet, rather than reporting the actual encoding used during the (last)
transformation. Would there be any (reasonably easy, preferably!) way to
eek this information out?
Thanks,
Mark
PM
To: [email protected]
Subject: RE: encoding="?!?"
For input documents, you will need to ensure they are in an encoding
supported by the transcoding system of that platform. The alternative is
to build Xerces-C with the ICU as its transcoder. You would need to get
Does anyone know which version at most of the ICU Libs is compatible to
Xerces-C 2.1 ?
ICU 2.6 is not.
Best regards,
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 01, 2003 7:27 PM
To: [email protected]
Subject: RE: encoding
For input documents, you will need to ensure they are in an encoding
supported by the transcoding system of that platform. The alternative is
to build Xerces-C with the ICU as its transcoder. You would need to get a
compatible version of ICU and build that, then rebuild Xerces-C. Take a
Does this mean that I should not experience any problems with exotic
encodings?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, September 12, 2003 5:17 PM
To: [email protected]
Subject: Re: encoding="?!?"
Xalan-C supports
Xalan-C supports different encodings on different platforms. If an
encoding is not supported, you will get UTF-8 instead. On some supported
encodings, Xalan-C will write numeric character references for characters
that are supported in the encoding, rather than writing the character. It
Hi,
has anybody tried xalan-c with outputing other characters than latin? e.g.
japanese, cyrillic, etc.? And if yes, were there any peculiarities?
Best regards,
> Hi,
> I need to set the encoding parameter of xsl:output dynamically. I think
this is
> definately possible.
No, such a feature is not currently available.
> I am aware of the XalanTransformer::setStylesheetParam() function but it
doesn't
> seem to work for me.
Hi,
I need to set the encoding parameter of xsl:output dynamically. I think this is definately possible.
I am aware of the XalanTransformer::setStylesheetParam() function but it doesn't seem to work for me. Am I using the wrong function and is there some other function I should use ?
I am
hi.
I have question about encoding problem(in XPath Processing).
I did compile XPathWrapper sample successfully
in Xalan-C++(~xml-xalan/c/samples/XPathWrapper/).
also, It works no problem on sample xml file.
But, I tried another xml file that encoded "euc-kr", It didn't work. :-(
N Bertoni/CAM/Lotus [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 24, 2002 9:24 PM
To: [email protected]
Subject: RE: Xalan-C + ICU: windows-1251 encoding troubles
Hi Dmitry,
Just to be clear, are you saying there's something wrong with file? What I
mean is, are we writing in
Chernyshov" To:
<[EMAIL PROTECTED] cc:
n.ru> Sub
I see...
Well, it's not so urgent - fortunately we can still use KOI8...
However, it would be very nice to have win-1251 support, 'cause it's the
most popular encoding for Russian language.
Thanks for explanation though!
Best,
Dimitry Chernyshov,
Technology Group Managing Directo
cc: (bcc: David N
Bertoni/CAM/Lotus)
n.ru> Subjec
Hi!
After I re-built Xalan-c1_3 + Xerces-c1_6_0 + ICU 2.0, Xalan works good with
different encodings.
Though, I've encountered one pretty strange problem.
If an XSL file has xsl:output encoding set to "windows-1251" () while transforming some XML, the
result contains character c
special Unicode class, in all other cases in a string case.
In the first step, I just want to detect the character wide (but I don't
know how!).
In the second step, I would like to send the transformation's result via a
HTTP layer, so I must know the exact character encoding if I want fill
I don't think I understand your question. There is no data in an
XSLTResultTarget. The processor chooses an output encoding as follows:
1. If there is an xsl:output element in the stylesheet, and it has an
encoding attribute, and the processor supports that encoding, the
seria
Hi everybody,
Does someone knows how to get
the character encoding of the XSLTResultTarget returned by
XalanTransformer.transform (…).
I would like to know if the
data are ISO-8859-1 or UTF-16 inside the XSLTResultTarget.
I believe that the getEncoding () is
just returning the value
31 matches
Mail list logo
