Thank you!
I checked your hints and answer after the respective positions.

>>>-----Ursprungliche Nachricht-----
>>>Von: Joerg Pietschmann [mailto:[EMAIL PROTECTED]] 
>>>Gesendet: Mittwoch, 9. Januar 2002 12:42
>>>An: FOP List
>>>Betreff: Re: Unicode interpretation
>>>Joerg Flotho <[EMAIL PROTECTED]>
>>>> We have different versions of interpretations regarding unicode:
>>>> (hexadecimal or decimal seems to make no difference).
>>>That's by design :-)
>>>> After passing XALAN some signs  were interpreted 
>>>wrong.(viewing in IE 
>>>> 5.0 as
>>>I suppose some characters are displayed as unexpected glyphs on the
>>>This may have rather different causes:
>>>- There is no appropriate font on the system for supplying  
>>>information how those characters are rendered.
>>>- The software has difficulties with the encoding of the  
>>>characters in a file and therefore interprets some 
>>>characters  as being other characters than originally meant.
>>>- There are typos in the character references in the XML 
>>>source  file. Your description doesn't make clear which of 
>>>these apply, maybe even all toghether. 

>>>1. Make sure the character references (&#160; and the like) in  the
source file are correct. 
Lower than 256 they are correct.
>>>2. Check whether the fonts on all relevant machines can map the
characters you use.
in principle the used characters are maped correctly. 
Checked in "word".

>>>In case of PDF, this may not only involve  the machine where the PDF
is generated but also the machines  on which the PDF is viewed.
is the same in this case.

>>> FOP must know about the fonts too.  This should be relevant 
>>>only if you use somewhat esoteric characters (for 
>>>middle-european cultures) like special  mathematical symbols.
>>>3. Be sure that the encoding in the XML declaration at the  
>>>beginning of your XML source file matches the actual 
>>>encoding.  This shouldn't be relevant if all characters 
>>>which aren't  US-ASCII are typed as character references 
>>>(like &#254;). If  in doubt, check whether there are any 
>>>non-ASCII characters  in the file, and replace all you find 
>>>by their corresponding  character reference. German umlauts, 
>>>non-breaking spaces and  typographic quotes are not ASCII.

We have only character references.
The encoding at the beginning of the xml.file was not beeing matched,
but the engine writes UTF-8 by itself.

>>>If this doesn't help, produce a minimal XML file with a 
>>>character reference whose rendering does not meet your 
>>>expectations, like  <?xml version="1.0"?>  
>>><char>&#1234;</char> and describe how you expect the 
>>>character to be rendered and what you get, and perhaps what 
>>>OS you run and what font you expect to be used for rendering 
>>>the character (which should of course be installed).

The copyright-symbol (x00A9) is interpreted correctly, I think 
because it's lower than 256.
Second example: a left-arrow (x2190). In it's displayed
correctly. In the pdf it appears as an angle.
The used font is Arial.
Using Arial Unicode MS makes no difference.(Maybe the syntax wasn't
correctly) Is white space allowed?

Is it a question of embedding fonts too?

>>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>>For additional commands, email: [EMAIL PROTECTED]

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to