Re: Interaction between force-page-count and initial-page-number
Chris, Comments below. Chris Bowditch wrote: Peter B. West wrote: snip/ The Rec says of force-page-number:auto, 'If there is no next page-sequence or if the value of its initial-page-number is auto do not force any page.' Should that read, '...the value of its initial-page-number is auto, auto-even or auto-odd...'? If not, some questions of behaviour arise. Hi Peter - I dont think the spec needs to say auto-even or auto-odd here. Unless I'm missing something it seems clear to me that if initial-page-number=auto-odd and the force-page-number=auto on the previous page-sequence then a page must be forced when the first page sequence ends on an odd page. My point is that the spec is *not* clear on this. 1st p-s: What's your 1st number (my last is 11)? The 2nd calculates that it's first number must be 13, based on initial-page-number:auto-odd. 2nd p-s: 13 The 1st p-s now forces a blank page, numbered 12. If it were to query again, based on the new last page number, the dialogue would go I dont see why it needs to re-query just because the last page number changed. After all the last page number changed as a result of communication between ps1 and ps2, so why go round again? My purpose in setting this scenario out is to demonstrate that, in these circumstances, a requery is not necessary. In general, though, if you have a mutual dependency, and the conditions on one side of the dependency change, you're up for another round. In the circumstances outlined, the analysis indicates that no recursion is necessary. However, there is nothing in the spec to indicate that a page sequence with force-page-number:auto should include its current last generated number in a query. It simply indicates that such a page-sequence should find out from the following page sequence whether its first number is odd, even or auto, in order to determine its own last page number. Unfortunately, the following page sequence may not be able to answer that question without first finding out what the last page number of the preceding page-sequence is. The scenario I outlined goes beyond what the spec states in order to resolve the deadlock. If this process is intended by the editors, they need to spell it out. 1st p-s: 1st number (12)? 2nd p-s: 13 and the extra dialogue would be unnecessary. Is this the intention? I agree this extra dialog is unnecessary but I couldnt tell from the quotes you made why you think the spec implies that it is necessary. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Interaction between force-page-count and initial-page-number
The editors, I am seeking clarification of the relationship between the force-page-number and initial-page-number properties in certain circumstances: specifically, when the value of force-page-number is auto and the value of initial-page-number on a following page-sequence is either auto-even or auto-odd. Apart from the descriptions of the properties, I found no other discussion about the interaction of these properties. The Rec says of force-page-number:auto, 'If there is no next page-sequence or if the value of its initial-page-number is auto do not force any page.' Should that read, '...the value of its initial-page-number is auto, auto-even or auto-odd...'? If not, some questions of behaviour arise. Say, for example, the last generated page of a force-page-number:auto page-sequence has an odd number, and the following page-sequence has an initial-page-number value of auto-odd. The page-sequence queries the following page-sequence for first first page number. The second page-sequence, in turn, queries the first page sequence for its last page number. Who goes first? Because the 1st page sequence is the only source of information on actual generated page numbers, the following scenario seems reasonable. The 1st sequence queries the 2nd, passing its current generated last page number. The 2nd then uses this number to generate a response. Let's say the generated last number is 11. 1st p-s: What's your 1st number (my last is 11)? The 2nd calculates that it's first number must be 13, based on initial-page-number:auto-odd. 2nd p-s: 13 The 1st p-s now forces a blank page, numbered 12. If it were to query again, based on the new last page number, the dialogue would go 1st p-s: 1st number (12)? 2nd p-s: 13 and the extra dialogue would be unnecessary. Is this the intention? This approach avoids holes in the page numbering, but I note that the combination of force-page-count:odd and a following initial-page-number:auto-odd will force a such a hole. Whatever the case, it would be worthwhile adding a clarification to the Rec. Peter -- Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Antwort: Re: Additional page forced by force-page-count
Thanks a lot for your responses!!! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Additional page forced by force-page-count
Dear FOPies, I'm using the force-page-count=even property to ensure an even number of pages. The page-sequence has some static content (footer and header). If my page-sequence has an odd number of pages, FOP appends an additional page correctly. The problem is that the appended page is not really empty; the static content is rendered. But I need an empty page. I'm not sure if this is a bug... Can somebody help me? Thx in advance, Sascha. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Additional page forced by force-page-count
On 10.01.2003 10:51:34 Sascha Schmidt wrote: Dear FOPies, :-) I'm using the force-page-count=even property to ensure an even number of pages. The page-sequence has some static content (footer and header). If my page-sequence has an odd number of pages, FOP appends an additional page correctly. The problem is that the appended page is not really empty; the static content is rendered. But I need an empty page. I'm not sure if this is a bug... Can somebody help me? Never done this myself, but have a look at the blank-or-not-blank attribute on fo:conditional-page-master-reference. You should be able to create a simple-page-master without static content regions and reference this one with blank, the normal ones with not-blank. Got it? Please post to fop-user next time for these questions. And without HTML if possible. Thanks a lot! Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
page-number-citation in combination with force-page-count
Question: In my current print jobs, I have two page sequences where the second sequence has its own numbering scheme (reset to 1). The PDF I generate need be printed in duplex mode. My first page sequence typically has two pages, but there's sometimes a document where the first sequence is three pages long. Since I need to have an even number of pages in the first sequence (otherwise duplex printing is broken, in insert a force-page-count=end-on-even in the first sequence. Works fine. But: I use page-number-citations in the footer to get page x of y style page counts. To get the y, I append an empty block with an id property to the flow that I reference with the page-number-citation. Because that empty block happens to be formatted on page 3 (4 is empty in this case), I get a footer page 4 of 3 on page 4. Of course, this is logical, I think. Now the question is: how can that kind of problem be solved with :FO (preferably with FOP, too.. 8-) ) I need to reference a formatting object that is on the empty page. This I cannot do, since I don't have a formatting object on the page - besides the static-content footer which doesn't help, because it's repeated -. Well, ok, I might be able to do something with the blank-or-not-blank property, but then the blank page isn't counted. I don't see how I could use a page-position=last property for this, either. Did I stumble upon a missing feature in XSL:FO, or am I just too tired? Any ideas? Thanks in advance, Arnd Beissner -- Cappelino Informationstechnologie GmbH Arnd Beißner Bahnhofstr. 3, 71063 Sindelfingen, Germany Email: [EMAIL PROTECTED] Phone: +49-7031-463458 Mobile: +49-173-3016917 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: page-number-citation in combination with force-page-count
Arnd Beißner wrote: I don't see how I could use a page-position=last property for this, either. This could work if it were implemented in FOP. Did I stumble upon a missing feature in XSL:FO, Yes. There is no feature to really *count* pages, you can only cite page numbers. Postprocessing with iText or implementing an extension element might help. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: page-number-citation in combination with force-page-count
J.Pietschmann wrote: Arnd Beißner wrote: I don't see how I could use a page-position=last property for this, either. This could work if it were implemented in FOP. Did I stumble upon a missing feature in XSL:FO, Yes. There is no feature to really *count* pages, you can only cite page numbers. Postprocessing with iText or implementing an extension element might help. Thanks, that'd be an extension element for me. If I do it, I'll report my findings. Thanks again, Arnd Beissner -- Cappelino Informationstechnologie GmbH Arnd Beißner Bahnhofstr. 3, 71063 Sindelfingen, Germany Email: [EMAIL PROTECTED] Phone: +49-7031-463458 Mobile: +49-173-3016917 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
force-page-count attribute in fo:page-sequence
Has anyone used the force-page-count attribute in fo:page-sequence ? I am using FOP 0.19 and when I render to PDF it reports that it is ignoring the force-page-count attribute. TIA, -- Dinesh Patel Britannic Assurance. This email and any accompanying documents are intended only for the named recipient, are confidential and may be privileged.If you are not the intended recipient please notify us immediately by email to [EMAIL PROTECTED] and you must not copy, disclose or otherwise use this message. Unauthorised use is strictly prohibited and may be unlawful. The content of this e-mail represents the view of the individual and not the company. The company reserves the right to monitor the content of all e-mails in accordance with lawful business practice. Whilst attachments are virus checked before transmission, Britannic Assurance plc does not accept any liability in respect of any virus which is not detected. Britannic Assurance plc, No. 3002 is registered in England and maintains its registered office at 1 Wythall Green Way, Wythall, Birmingham B47 6WG. Telephone 01564 82 88 88 Fax: 01564 82 88 22 Website: www.britannicassurance.com Britannic Assurance plc, Britannic Unit Linked Assurance Limited and Britannic ISA Managers Limited are regulated by the Personal Investment Authority. Britannic Unit Trust Managers Limited is regulated by IMRO. Each of these companies is a member of the Britannic marketing group which only advises on and sells its own life assurance, pensions, unit trust and ISA products. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: force-page-count attribute in fo:page-sequence
At 03:06 PM 11/2/01 -, Dinesh Patel wrote: Has anyone used the force-page-count attribute in fo:page-sequence ? I am using FOP 0.19 and when I render to PDF it reports that it is ignoring the force-page-count attribute. The CHANGES file will say for sure when that property was supported. Off the top of my head it showed up in 0.20. Regards, Arved Sandstrom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
force-page-count
The force-page-count property on fo:page-sequence is now supported, in full (that means you can use 'auto', 'even', 'odd', 'end-on-even', 'end-on-odd' and 'no-force'). Caveats: 1. This is relatively untested stuff. I ran through a bunch of combinations, but let's face it, proper black-box testing of the various force-page-count + initial-page-number + page-sequence page count combinations results in a *large* number of test cases, and I've only dented the surface. Expect bugs; 2. If 'force-page-count' produces an extra page, it will be a blank page. This is unsophisticated, but if anyone can think of a better idea, let's hear it. :-) You, of course, have access to the outer regions on this blank page using the blank-or-not-blank='blank' conditional-page-master-reference; 3. This third point is related to point 2. The default on force-page-count is 'auto', and unlike a lot of other properties, this one doesn't mean don't do anything. In fact, 'auto' will result in a forced blank page (in this implementation) fairly frequently. You need to account for this by having a suitable simple-page-master available, basically one that is identified with a blank-or-not-blank='blank' conditional-page-master-reference, or a default that is effectively the same. If not, I cannot guarantee beautiful behaviour at the moment. Basically you don't want a page-master that tries to pull in fo:flow content being used for a blank page. If you have been using page-breaks you are probably already OK with this. Short fix for point 3: if you have lots of material (direct FO, or XSLT stylesheets) change your fo:page-sequences to have a force-page-count='no-force'. This will save you from having to deal with blank pages if you don't want to. Again, keep in mind that 'no-force' is NOT the default. Hope this property, in combination with 'initial-page-count', plugs most of the remaining holes in pagination. The final big one, I believe, is page-position=last. Regards, Arved Sandstrom --- This mail was sent through the Nova Scotia Provincial Server, with technical resources provided by Chebucto Community Net. http://nsaccess.ns.ca/mail/ http://www.chebucto.ns.ca/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
