Thanks for your reply...
There is an actual '?' in the html source, so It would appear that the
XSLT has transformed some other character from the XML to make question
marks.
We can contact the provider of the XML to ask them what character they
entered, I just thought that somebody on this list might have seen this
problem, or something similar to it, before. And that there might be a
piece of code which will use the same HTML encoding as seemed to work on
the none XSLT page.
Alex.
Jarno(_dot_)Elovirta(_at_)nokia(_dot_)com wrote:
Hi,
Oner of our XSLT pages has been outputing a question mark
where a bullet
would have been expected.
Are you sure it really is a QUESTION MARK, or is it a bullet character and the
program you use to view the document either uses the wrong encoding, e.g. UTF-8
vs. ISO-8859-1, or could it be that the font you use doesn't have a glyph for
the bullet character and displays it as a question mark.
I say a bullet would have been expected because we have another page
which was showing the bullet snd not the question mark, and that page
doesn't use XSLT for the transformation.
As it is dificult to determine which characters might get
input in the
XML is there a way of handling symbols at least as accurately as the
straight HTML page?
I don't understand the question. Does accuracy mean using entitiy references?
If determing which characters you have in your input XML documents, you should
probably get an editor/viewer that loads the document using the correct
character encoding and also can display non-ASCII characters correctly.
Cheers,
Jarno - Delerium: Koran
--+------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
You are subscribed as: alexscott(_at_)lineone(_dot_)net
To unsubscribe, go to:
http://lists.mulberrytech.com/unsub.php/xsl-list/alexscott(_at_)lineone(_dot_)net
or e-mail:
<mailto:xsl-list-unsubscribe-alexscott=lineone(_dot_)net(_at_)lists(_dot_)mulberrytech(_dot_)com>
--+--