On Wed, 2 Nov 2005 05:27 pm, Jingjing Lee wrote:
> --- Manuel Mall <[EMAIL PROTECTED]> wrote:
> > On Wed, 2 Nov 2005 01:03 am, Chris Bowditch wrote:
> > > Manuel Mall wrote:
> > > > Currently if one puts a zero-width-space
> >
> > (U+200B) into an XSL-FO
> >
> > > > file (or specifies
> >
> > linefeed-treatment="treat-as-zero-width-space")
> >
> > > > it is rendered as a "missing character" in PDF.
> >
> > Is that correct,
> >
> > > > i.e. does this character have to exist in the
> >
> > font used or should
> >
> > > > the formatter or renderer simply remove this
> >
> > character? It is the
> >
> > > > second approach that both AntennaHouse and
> >
> > RenderX appear to have
> >
> > > > chosen.
> > >
> > > I recommend that no character is output for a ZWS.
> >
> > The whole purpose
> >
> > > of placing a ZWS into the input XSL-FO is to give
> >
> > layout an extra
> >
> > > break opportunity, without changing the appearance
> >
> > of the generated
> >
> > > document.
> >
> > That seems to be the consensus, that is consider ZWS
> > for line breaking
> > but then discard and don't give it to the renderers.
> >
> > Are there any other (unusual Unicode) characters
> > which fall in the same
> > category that is they influence layout decisions but
> > should not be seen
> > by the renderers?
> >
> > > Chris
> >
> > Manuel
>
> According to UAX#14, this characters is invisible too
> 00AD SOFT HYPHEN (SHY)
> 2060 WORD JOINER (WJ)
> FEFF ZERO WIDTH NO-BREAK SPACE (ZWNBSP)
>
Yes and they are all of General Category Cf I think so may be all Cf 
characters?

> Jingjing
>
Manuel

Reply via email to