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=4226>.
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=4226

The orphans property doesn't seem to work

           Summary: The orphans property doesn't seem to work
           Product: Fop
           Version: all
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: pdf renderer
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


The following example produces a paragraph at the bottom of the second page
which has only one line.
However, the initial value of the property is 2. Setting it explicitly doesn't
help either.
--
<?xml version="1.0" encoding="utf-8"?><fo:root
xmlns:fo="http://www.w3.org/1999/XSL/Format"; country="GB" font-family="Times"
language="en">
<fo:layout-master-set>
<fo:simple-page-master master-name="blank" writing-mode="lr-tb"
page-height="297mm" page-width="210mm" margin-top="20mm" margin-bottom="20mm"
margin-left="25mm" margin-right="25mm">
<fo:region-body margin-top="0mm" margin-bottom="0mm" margin-left="0mm"
margin-right="0mm"/>
</fo:simple-page-master>
<fo:simple-page-master master-name="even" writing-mode="lr-tb"
page-height="297mm" page-width="210mm" margin-top="20mm" margin-bottom="20mm"
margin-left="15mm" margin-right="35mm">
<fo:region-body column-count="1" margin-top="15mm" margin-bottom="10mm"
margin-left="0mm" margin-right="0mm"/>
<fo:region-before region-name="region-before-even" extent="15mm"/>
<fo:region-after extent="10mm"/>
</fo:simple-page-master>
<fo:simple-page-master master-name="odd" writing-mode="lr-tb"
page-height="297mm" page-width="210mm" margin-top="20mm" margin-bottom="20mm"
margin-left="35mm" margin-right="15mm">
<fo:region-body column-count="1" margin-top="15mm" margin-bottom="10mm"
margin-left="0mm" margin-right="0mm"/>
<fo:region-before region-name="region-before-odd" extent="15mm"/>
<fo:region-after extent="10mm"/>
</fo:simple-page-master>
<fo:simple-page-master master-name="onesided" writing-mode="lr-tb"
page-height="297mm" page-width="210mm" margin-top="20mm" margin-bottom="20mm"
margin-left="25mm" margin-right="25mm">
<fo:region-body column-count="1" margin-top="15mm" margin-bottom="10mm"
margin-left="0mm" margin-right="0mm"/>
<fo:region-before region-name="region-before-onesided" extent="15mm"/>
<fo:region-after extent="10mm"/>
</fo:simple-page-master>
<fo:simple-page-master master-name="title" writing-mode="lr-tb"
page-height="297mm" page-width="210mm" margin-top="20mm" margin-bottom="20mm"
margin-left="35mm" margin-right="15mm">
<fo:region-body margin-top="0mm" margin-bottom="0mm" margin-left="0mm"
margin-right="0mm"/>
</fo:simple-page-master>
<fo:page-sequence-master master-name="document">
<fo:repeatable-page-master-alternatives>
<fo:conditional-page-master-reference odd-or-even="even" master-name="even"/>
<fo:conditional-page-master-reference odd-or-even="odd" master-name="odd"/>
<fo:conditional-page-master-reference blank-or-not-blank="blank"
page-position="any" master-name="blank"/>
</fo:repeatable-page-master-alternatives>
</fo:page-sequence-master>
</fo:layout-master-set>
<fo:page-sequence master-name="title">
<fo:flow flow-name="xsl-region-body">
<fo:block font-size="2em" font-weight="bold" width="100%" space-before="70mm"
space-before.precedence="force" text-align="center">Specimen Management System
Functional Specification</fo:block>
</fo:flow>
</fo:page-sequence>
<fo:page-sequence format="1" initial-page-number="1" master-name="document">
<fo:static-content flow-name="region-before-even">
<fo:block width="100%" text-align="start" space-after="3pt">
<fo:inline font-style="oblique" text-transform="capitalize">
</fo:inline>
</fo:block>
<fo:block width="100%" height="0.4pt" background-color="black"/>
</fo:static-content>
<fo:static-content flow-name="region-before-odd">
<fo:block width="100%" text-align="end" space-after="3pt">
<fo:inline font-style="oblique" text-transform="capitalize">
</fo:inline>
</fo:block>
<fo:block width="100%" height="0.4pt" background-color="black"/>
</fo:static-content>
<fo:static-content flow-name="region-before-onesided">
<fo:block width="100%" text-align="start" space-after="3pt">
<fo:inline font-style="oblique" text-transform="capitalize">
</fo:inline>
</fo:block>
<fo:block width="100%" height="0.4pt" background-color="black"/>
</fo:static-content>
<fo:static-content flow-name="xsl-region-after">
<fo:block width="100%" text-align="center">
<fo:page-number/>
</fo:block>
</fo:static-content>
<fo:flow flow-name="xsl-region-body"> <fo:wrapper font-weight="bold">
<fo:block font-size="1.6em" space-before="20mm" space-before.precedence="force"
break-before="odd-page">Chapter 1</fo:block>
<fo:block font-size="2.0em" space-after="20mm" space-after.precedence="force"
space-before="10mm" space-before.precedence="force">
Introduction
            </fo:block>
</fo:wrapper> <fo:block font-size="1.4em" font-weight="bold" space-after="1.4em"
space-after.precedence="force" space-before="2.8em"
space-before.conditionality="discard">1.1  Objective Of This Document</fo:block>
<fo:block hyphenate="true" text-align="justify" text-indent="0mm">This
description specifies in detail all the functions and elements
                  of the Specimen Management System. It is the reference for the 
development of
                  the system. Important feedback of the development process may lead to
                  amendments to this document. This should, however, be an exceptional
                  event.</fo:block> <fo:block font-size="1.4em" font-weight="bold"
space-after="1.4em" space-after.precedence="force" space-before="2.8em"
space-before.conditionality="discard">1.2  Intended Audience</fo:block>
<fo:block hyphenate="true" text-align="justify" text-indent="0mm">One part of
the audience consists of the representatives of the
                  user community. They can use the document to verify if the user 
requirements
                  are met by the proposed functions and if the functions provide a 
suitable
                  solution. The people in this position should have sufficient 
knowledge of data
                  and process modelling in order to be able to read the models. The 
syntax is
                  described briefly though in sections  and
                  .</fo:block> <fo:block hyphenate="true" text-align="justify"
text-indent="1em">The other part is the development team, which will provide a
                         technical solution and implement it. Needless to say it needs 
a thorough
                         modelling in order to grasp all the details and understand 
their
                         consequences.</fo:block> <fo:block hyphenate="true" 
text-align="justify"
text-indent="1em">In order to better understand the administrative and technical
                         background of the system, the reader is referred to  and
                         .</fo:block> <fo:block font-size="1.4em" font-weight="bold" 
space-after="1.4em"
space-after.precedence="force" space-before="2.8em"
space-before.conditionality="discard">1.3  Structure Of This Document</fo:block>
<fo:block hyphenate="true" text-align="justify" text-indent="0mm">The document
has eight chapters after this one. The first two are
                  the data model and the process specification. Together they 
represent the core
                  of the system. The following chapter presents the process model. The 
next two
                  chapters specify the interfaces the system must have. The message 
exchange
                  interface exposes the business logic, which implements the system 
core. It is
                  created according to the <fo:inline>?Open Interface?</fo:inline> 
paradigm. The user
                  interfaces assemble all the end-user functions. They are loosely 
coupled with
                  the business logic, i.e. they have no privileged access path to the 
core of the
                  system. Chapter  specifies all the rules for
                  protecting the integrity of the data. Viewpoints such as correctness 
and
                  security are considered in it. Next, the constraints in terms of 
capacity are
                  specified. This is most trivial because the system is quite small in 
almost
                  every aspect. Finally, the specification is justified with respect 
to the user
                  requirements in .</fo:block> <fo:block hyphenate="true" 
text-align="justify"
text-indent="1em">The presentation of the set of specifications is slightly
                  formalised. Each item has a number and is set in italics. The 
descriptive parts
                  are set in the normal way. The purpose of this is to have a tool for 
verifying
                  more easily a technical solution against this specification. It also 
provides a
                  reference facility for related documents.</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