Re: Problem searching text in FOP generated PDF file
Singhal, Ramneek (Exchange) wrote: I have generated a tabular PDF report using Apache-FOP-0.20.5. if I try to search a String(ctrl-f) in generated PDF report, it never finds it, tough string exists in the document. You've used non-standard (custom) fonts. FOP 0.20.5 doesn't generate the data structures which are necessary for proper searching contents displayed with non-standard fonts. Your options: a) Use predefined fonts only, don't use non-standard fonts. b) Generate the metrics using ansi encoding (use the -enc ansi command line option when starting the TTF reader) Also when I try to copy some text from this pdf reports and try pasting it in some text editor instead of text it shows ?. Same problem. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Poll] Expectations regarding side-floats
Vincent Hennebert wrote: - would you expect a side-float being placed on another page than its anchor? Would you prefer the whole chunk of text to be deferred on the following page? This should not happen unless two (or more) side flows anchored at the same line are stacked. I'm not sure whether the spec has additional guidelines. - would you expect a side-float being split on several pages? This can be controlled using keeps. So yes, side floats should probably be broken across pages by default, if such breaks are possible. - would you expect different layouts, depending on whether a set of side-floats would be placed on the middle of a page or at the bottom (thus, with some of them on the current page and the others on the following page)? Probably yes. I have some difficulty imaging what you actually have in mind. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Poll] Expectations regarding side-floats
Vincent, in considering this, you may wish to also keep in mind: what do you see as the usage difference between side-floats and the xsl:region-start and xsl:region-end regions? I mention this, just to make sure that use cases actually intended for side regions do not move into side-floats, and vice-versa. Glen Vincent Hennebert wrote: Dear Fop users, I'm currently thinking about the implementation of side-floats () into Fop. It turns out that there is a choice to make between several design decisions which imply different behaviors regarding the placement of floats on the page. To help me make a decision, I'd like to know which usage you would make of side-floats: on a general manner, what sort of typographic material would you typeset using side-floats? Particular things of which we don't think in the first place? More specifically, as the XSL-FO recommendation allows some freedom in these areas: - would you expect a side-float being placed on another page than its anchor? Would you prefer the whole chunk of text to be deferred on the following page? - would you expect a side-float being split on several pages? - would you expect different layouts, depending on whether a set of side-floats would be placed on the middle of a page or at the bottom (thus, with some of them on the current page and the others on the following page)? Any comments, remarks, hints of all sort would be welcome. Thanks, Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Poll] Expectations regarding side-floats
Dear Fop users, I'm currently thinking about the implementation of side-floats () into Fop. It turns out that there is a choice to make between several design decisions which imply different behaviors regarding the placement of floats on the page. To help me make a decision, I'd like to know which usage you would make of side-floats: on a general manner, what sort of typographic material would you typeset using side-floats? Particular things of which we don't think in the first place? More specifically, as the XSL-FO recommendation allows some freedom in these areas: - would you expect a side-float being placed on another page than its anchor? Would you prefer the whole chunk of text to be deferred on the following page? - would you expect a side-float being split on several pages? - would you expect different layouts, depending on whether a set of side-floats would be placed on the middle of a page or at the bottom (thus, with some of them on the current page and the others on the following page)? Any comments, remarks, hints of all sort would be welcome. Thanks, Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Does FOP not care about section.autolabel.max.depth?
Yes it was a docbook thin, sorry for that. The problem was that the sub sections were stored in a para element instead in another section element. Thanks -Original Message- From: Chris Bowditch [mailto:[EMAIL PROTECTED] Sent: Freitag, 11. August 2006 11:36 To: fop-users@xmlgraphics.apache.org Subject: Re: Does FOP not care about section.autolabel.max.depth? Remo Liechti wrote: > this generates: > 1. section one > 1.1 section one dot one > section one dot one dot one > > 1.2 section one dot two > section one dot two dot one > > 2. section two > 2.1 section two dot one > > You see, it only goes down one node... to tell the FOP to go down more > steps, a property exists: > section.autolabel.max.depth No, this property does not tell FOP anything. It tells docbook.xsl how to create the XSL-FO. This is a docbook problem ask on the docbook mailing list. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message may contain legally privileged or confidential information and is therefore addressed to the named persons only. The recipient should inform the sender and delete this message, if he/she is not named as addressee. The sender disclaims any and all liability for the integrity and punctuality of this message. The sender has activated an automatic virus scanning, but does not guarantee the virus free transmission of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
region-before with columns
I've a template which it's giving me headaches as i can't seam to find a way to implement it with fop... I've a region-before in a page with 2 columns defined. My only problem is that i need that the region-before to ocupy only the area of the 1st column and allow text to flow into it's "position" to the second column... as it shows in the image below... http://www.nabble.com/user-files/270/page_2_columns.JPG page_2_columns.JPG All help much appresciated... LF -- View this message in context: http://www.nabble.com/region-before-with-columns-tf2089684.html#a5759509 Sent from the FOP - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Does FOP not care about section.autolabel.max.depth?
Remo Liechti wrote: this generates: 1. section one 1.1 section one dot one section one dot one dot one 1.2 section one dot two section one dot two dot one 2. section two 2.1 section two dot one You see, it only goes down one node... to tell the FOP to go down more steps, a property exists: section.autolabel.max.depth No, this property does not tell FOP anything. It tells docbook.xsl how to create the XSL-FO. This is a docbook problem ask on the docbook mailing list. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
