Hi Antonio,
if you perform the transformation and send the output "To File"
rather than "To New Document", and then open the new file in
ExchangerXML, you will see that the characters are
displayed correctly. This implies there is an encoding problem in
ExchangerXML when trying to display the output from the
in-memory result, and that the transformation itself is not the
cause of the problem.
Regards,
Gabriel McGoldrick
www.exchangerxml.com
----- Original Message -----
From: "António Mota" <amsmota(_at_)gmail(_dot_)com>
To: <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
Sent: Wednesday, April 27, 2005 1:52 PM
Subject: Re: [xsl] Prob with encoding
Hi:
I'll check the result with other editors and if the problem occurs
only with yours i'll send it the samples.
Regards.
On 4/27/05, Gabriel McGoldrick <gmcgoldrick(_at_)exchangerxml(_dot_)com>
wrote:
Antonio,
Are you executing the transformation through the
debugger or directly in the editor?
It is more likely that the problem occurs when
trying to display the output in the editor, rather
than anything to do with the transformation itself.
Can you send on a sample input and xsl file so we
can help you track down the issue?
Regards,
Gabriel McGoldrick
www.exchangerxml.com
----- Original Message -----
From: "António Mota" <amsmota(_at_)gmail(_dot_)com>
To: <xsl-list(_at_)lists(_dot_)mulberrytech(_dot_)com>
Sent: Wednesday, April 27, 2005 12:31 PM
Subject: Re: [xsl] Prob with encoding
Well, if i put a xsl:output encoding="ISO-8859-1" it appears as
<Titulo>Caracteriza��o</Titulo>
and in some places the ?? apears as two little boxes, or squares.
I'm using Cladonia ExchangerXML, so i don't know who's doing the
serialization, but from the messages that appears i'll say it's Saxon
allright.
Thanks.
On 4/27/05, David Carlisle <davidc(_at_)nag(_dot_)co(_dot_)uk> wrote:
If i put a xsl:output encoding="ISO-8859-1" then the output
appears
with a ISO-8859-1 declaration but the chars are all wrong.
That doesn't give us much information.
posting what output you get from an input of <x>Caracterização"</x>
might give people a clue.
A system is allowed to ignore the encoding hint of xsl:output and do
its
own thing. Saxon desn't do this though so long as saxon is actually
doing the serialisation. If you are using a java API to pass some
in-memory output to some other process and it is that process that
is
writing the final file then it is quite likely that the encoing hint
on
xsl:output will be ignored.
David
________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a
proactive
anti-virus service working around the clock, around the globe,
visit:
http://www.star.net.uk
________________________________________________________________________
--~------------------------------------------------------------------
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>
--~--
--~------------------------------------------------------------------
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>
--~--