Hi Peter.

Peter Davis:
> I'm no expert on character-encoding issues, but did you try looking at the 
> output in a Hex editor?  Make sure that the sequence for the '?' is actually 
> 0x3f before blaming Xalan.

Yep, I checked.  I opened the output file in vim.  It definitely was an
actual '?' character.  If it was the &#4E00; character, there should've
been the three bytes E4 BD A0 in there (that's the UTF-8 encoding of
4E00).

> Since you are using a character entity in the source doc, it seems unlikely 
> that your text editor for the source could be the cause, and since the output 
> encoding is UTF-8 it seems unlikely that the character is lost on output.  My 
> guess is that the editor you are using to view the output either just doesn't 
> understand UTF-8 or doesn't have a font that includes the offending 
> characters.

Wish it was such a simple error on my part.

Thanks,

Cameron

-- 
Cameron McCormack
  // [EMAIL PROTECTED]
  // http://www.csse.monash.edu.au/~clm/
  // icq 26955922

Reply via email to