* Daniel S. Haischt; <[EMAIL PROTECTED]> on 04 Oct, 2002 wrote:
>but saxon should support the unicode representation
>of extended characters, shouldn't it?
>
>and according to my unicode table &#160; is equivalent to
>&nbsp;

I could be wrong but if you use this parameter for saxon you should be
able to get what you want (YMMV) 

<xsl:param name="saxon.character.representation"
                     select="'entity'"/>

-- 

Togan Muftuoglu

Reply via email to