So the list knows this problem has been resolved... -----Original Message----- From: Robert Taylor [mailto:[EMAIL PROTECTED] Sent: Thursday, April 22, 2004 2:53 PM To: Josh Canfield Subject: RE:   getting converted into �
Josh, thanks for the reply. Ironically I've been on http://www.dpawson.co.uk several times for other XSL questions but as mentioned in the article, when searching for nbsp; or #160 you can get a conglomeration of results which don't actually pertain to the question. Anyhow, thanks for the link. It's exactly the information I needed. robert > -----Original Message----- > From: Josh Canfield [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 22, 2004 2:19 PM > To: Robert Taylor > Subject: RE:   getting converted into � > > > This is most likely a character encoding problem. The serializer is > outputting the unicode character for  . When > read by a system that believes you are using a single byte encoding you will > get the accent A. > > http://www.dpawson.co.uk/xsl/sect2/nbsp.html#d6353e246 > > -----Original Message----- > From: Robert Taylor [mailto:[EMAIL PROTECTED] > Sent: Thursday, April 22, 2004 7:14 AM > To: [EMAIL PROTECTED] > Subject:   getting converted into � > > > Greetings again, > > I've run into a strange problem when transforming an XML document into HTML. > I have an XSL style sheet where I use the ASCII equivalent for ,  . > > I'm using JDOM which inturn relies on TrAX to perform the transformation. > I've configured JDOM to use Xalan: > org.apache.xalan.processor.TransformerFactoryImpl. > > After transforming the XML document, the resulting document replaces each >   with an invisible binary character which is rendered as � when > using the XMLOutputter to output the document. > > I've searched Google, JDOM, and Xalan archives. I've also reviewed the > relavent > FAQ's and haven't come up with any answers. > > I'm sure that I'm searching using the wrong criteria (nbsp; #160, etc...) > because this seems like a configuration issue. > > Any ideas? > > robert > >
