Re: [patch] libfo-compat.xsl and significant space

Tim Waugh <[email protected]> writes:

> On Thu, Mar 10, 2005 at 12:34:23AM +0000, Tony Graham wrote:
>
>> Thanks, but instead I added <xsl:preserve-space> and listed all the
>> FOs with #PCDATA in their content model.  Please confirm whether or
>> not that does the job.
>
> It doesn't.  I get things like this:
>
> press<fo:inline font-weight="bold">F8</fo:inline>for the menu
>
> from a DocBook para fragment that had:
>
>     press <keycap>F8</keycap>
>     for the menu

This template rule may be the problem:

  <xsl:template match="text()">
    <xsl:value-of select="normalize-space()"/>
  </xsl:template>

The real problem, for xmlroff, is the whitespace at the beginning of
the lines.

I'll look again at your whitespace patch.

>> or the FoLibfoContext warning mode setting could actually be
>> implemented.
>
> What would be the effect of that?

Whatever we want, not least because (a) it's software, and (b) it's
software that hasn't been written yet.

I was contemplating a warning mode setting to not warn about
unsupported properties.  Just because I find it useful to be warned
about unsupported properties doesn't mean everybody else does.

Regards,


Tony.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click