[xsl] fo and last page number ....

Subject: [xsl] fo and last page number ....
From: "Jordan, Tom" <Tom.Jordan@xxxxxxxxxxxxxx>
Date: Mon, 14 Feb 2005 10:08:13 -0600
In pursuit of a robust last page marker.

Now I know that the recommended way is to place
an empty block at the end of an XSL-FO document
and then reference it with a
<fo:page-number-citation ref-id='lastpage'/>

Yet, when you are producing a document that will
then be edited later in the application workflow,
this leaves something desired.

For example, using nfor(http://www.sf.net/projects/nfor),
to producing an RTF document that will be edited via
some RTF editor like Word/Open Office.  When the
user adds additional text to the end of the doc,
they will be actually adding text after the
bookmark used to identify the lastpage; thus
the total number of pages will be inaccurate from
this point on in the workflow.

Since Word/OpenOffice and others generally have
a documents information fields available, why not
provide a way to access this information in XSL-FO
or provide a simple node for the last page.

eg:
<fo:page-number-last/> to complement <fo:page-number/>

or

<fo:doc-prop prop-name='numpages'/>

Where would I propose something like this to the
standard's committee?

Thanks,
-- Tom.

--
"Nothing will ever be attempted, if all
 possible objections must first be
 overcome." - Samuel Johnson 

-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.7 - Release Date: 2/10/2005
 

This e-mail or the documents accompanying this e-mail contain
information that may be confidential and/or privileged. It may
also be prohibited from disclosure under applicable law. The
information is intended to be for the use of the individual or
entity named on this transmission. If you are not the intended
recipient, be aware that any disclosure, copying, distribution
or use of the contents of this information is without
authorization and is prohibited. If you have received this
e-mail in error, please notify us immediately so that we can
take action to correct the problem.

Current Thread