DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6042>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6042

Linewraps elide data on lines with intermixed typefaces

           Summary: Linewraps elide data on lines with intermixed typefaces
           Product: Fop
           Version: all
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Major
          Priority: Other
         Component: pdf renderer
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


In the following FO code (which I've done my best to minimize, despite that I
don't really know XSL-FO yet, not having read the standard at the moment), the
PDF document produced is missing some of the text which is set in Courier.  The
problem occurs in FOP 0.20.2RC, which for some reason doesn't show up in the
Version field in this form.

The example comes from a larger document which has this problem in several
places in the PDF output.

<?xml version="1.0" encoding="UTF-8"?>
<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format";
  font-family="Times Roman" font-size="10pt" text-align="justify">
<fo:layout-master-set>
<fo:page-sequence-master
  master-name="oneside1">
<fo:repeatable-page-master-alternatives>
<fo:conditional-page-master-reference master-name="simple1"/>
</fo:repeatable-page-master-alternatives>
</fo:page-sequence-master>
<fo:simple-page-master master-name="simple1" page-width="8.5in"
page-height="11in" margin-top="1in" margin-bottom="1in"
margin-left="10pc" margin-right="1in"><fo:region-body
margin-bottom="24pt" margin-top="24pt"/><fo:region-before
extent="12pt"/><fo:region-after
extent="12pt"/></fo:simple-page-master></fo:layout-master-set>

<fo:page-sequence id="" hyphenate="true" master-name="oneside1"
language="en"> <fo:flow flow-name="xsl-region-body"><fo:block
space-before.optimum="1em"
space-before.minimum="0.8em" space-before.maximum="1.2em">Simple types
are easy to parse, as they consist of a single token describing that
type (which is always one of <fo:inline
font-family="Courier">"Integer"</fo:inline>, <fo:inline
font-family="Courier">"Double"</fo:inline>, <fo:inline
font-family="Courier">"String"</fo:inline>, <fo:inline
font-family="Courier">"Date_DateOnly"</fo:inline>, <fo:inline
font-family="Courier">"Date_DateTime"</fo:inline>, <fo:inline
font-family="Courier">"Date_TimeOfDay"</fo:inline>, or <fo:inline
font-family="Courier">"Date_ElapsedTime"</fo:inline>).  If the full
type of a field is simple, then that token is the value returned by
the method; otherwise, that token is added to the list of subtypes
maintained by the enclosing
complex.</fo:block></fo:flow></fo:page-sequence></fo:root>

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

Reply via email to