Re: Spaces when rendering PCL format
Razvan Veina wrote: fo:table-cell border-top-style=double border-top-width=1pt border-top-color=black fo:blockLine no/fo:block /fo:table-cell Can you make sure the width defined for the column is not smaller than the width of Line no Failing that its probably just a deficiency of the PCL Renderer. It should be noted that the PCL Renderer is very primitive and under developed when compared with the PDF Renderer. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spaces when rendering PCL format
The width of the column is much bigger than the width of the text. I guess you're right about the deficiency of the PCL renderer because I made a very interesting change that improved the look of my page: I changed the width of my column with a small value, and like magic, the texts were displayed fine. But now in some places of the same column the spaces seem to be much bigger that a normal space... probably a strange way to calculate the position of the texts... It's like when displaying a text composed from many words, each word is displayed separately. Isn't it possible to treat these kinds of texts like a single word maybe ?... Anyway... I'm aware of the differences between the PCL and PDF renderer, but I *MUST* get PCL output... that's life, I guess :) Thank you. - Original Message - From: Chris Bowditch [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, April 07, 2004 4:11 PM Subject: Re: Spaces when rendering PCL format Razvan Veina wrote: fo:table-cell border-top-style=double border-top-width=1pt border-top-color=black fo:blockLine no/fo:block /fo:table-cell Can you make sure the width defined for the column is not smaller than the width of Line no Failing that its probably just a deficiency of the PCL Renderer. It should be noted that the PCL Renderer is very primitive and under developed when compared with the PDF Renderer. Chris - 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]
Re: Spaces when rendering PCL format
Razvan Veina wrote: The width of the column is much bigger than the width of the text. I guess you're right about the deficiency of the PCL renderer because I made a very interesting change that improved the look of my page: I changed the width of my column with a small value, and like magic, the texts were displayed fine. But now in some places of the same column the spaces seem to be much bigger that a normal space... probably a strange way to calculate the position of the texts... It's like when displaying a text composed from many words, each word is displayed separately. Isn't it possible to treat these kinds of texts like a single word maybe ?... Anyway... I'm aware of the differences between the PCL and PDF renderer, but I *MUST* get PCL output... that's life, I guess :) Patches to the PCL Renderer will be most welcome. But be aware that they wont be applied to the maintenance branch as this is now frozen. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spaces
Miguel Paulo, Actually, I get errors when I use nbsp; in XSL-FO markup. I would have to set it up as an entity. However, when using the following line at the top of my XML document: ?xml version=1.0 encoding=UTF-8? ...I can use #160; as a space character (I believe it's non-breaking, too!), without problems. If you use an encoding attribute value other than UTF-8 you might need to use something else. Hope this helps! Web Maestro Clay Miguel Angel Busto wrote: You can use nbsp; special char instead of space char -Original Message- *From:* Joannes Capitanio [mailto:[EMAIL PROTECTED] *Sent:* lunes, 27 de enero de 2003 13:22 *To:* [EMAIL PROTECTED] *Subject:* Re: Spaces try to use white-space-collapse=false property inside fo:block joannes - Original Message - *From:* Paulo Gustavo Benfatti mailto:[EMAIL PROTECTED] *To:* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] *Sent:* Monday, January 27, 2003 1:00 PM *Subject:* Spaces Hi, How can i add more than a space between two words in fop:block tag ? Thanks, Paulo Benfatti Accenture - São Paulo - Brazil -- Clay Leeds - [EMAIL PROTECTED] Web Developer - Medata, Inc. - http://www.medata.com PGP Public Key: https://mail.medata.com/pgp/cleeds.asc - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spaces
try to use white-space-collapse="false" property inside fo:block joannes - Original Message - From: Paulo Gustavo Benfatti To: [EMAIL PROTECTED] Sent: Monday, January 27, 2003 1:00 PM Subject: Spaces Hi, How can i add more than a space between two words in fop:block tag ? Thanks, Paulo Benfatti Accenture - São Paulo - Brazil
Re: Spaces and precedence
Hi. Here is the (pruned) FO I get as an result of my xsl transformation. What I wanted to do was suppress additional space between two headlines that directly follow each other. fo:flow flow-name=xsl-region-body !-- preceeding blocks -- !-- block one -- fo:block break-before=page id=h1_6 space-before=50pt space-after=20pt space-after.precedence=1 7.Leistungsspektrum /fo:block !-- block two -- fo:block space-before.minimum=0pt space-before.precedence=2 id=h2_1 space-after=20pt space-before=50pt 7.1 Einzelplatzscanner /fo:block !-- succeeding blocks -- /fo:flow Block one := A Block two := B My understanding of the spec: A and B are stackable areas, have no borders or padding and are not reference-areas (block-progression-direction inherited from parent, no indents specified). A and B have a block stacking constraint S according to rule 3a. in chapter 4.2.5 Space Resolution: S1 := space-after=20pt precedence=1 S2 := space-before=50pt precedence=2 S'' := S1 and S2 In this case: S' == S'' because S'' does not contain line-area traits. The resolved space-specifier S would suppress S1 because it has a lower precedence than S2 (point 3 in 4.3.1). Do I get that right? FOP would not suppress anything and just add all spaces. TIA! Ralf
RE: Spaces and precedence
Joerg, it's the diagrams that accompany Section 4.2.5 that make things halfway understandable. They have an diagrammed example of each clause. There are also some key statements in the first paragraph of 4.2.5 - namely, that the definitions are recursive, and, that the entire point of the definitions is to identify areas that have only spaces between them. So actually I was also half-incorrect, because I spoke too hastily; with respect to the situation with _siblings_ and their space-after/space-before, the borders padding do _not_ have to have zero width. Even where borders and padding have non-zero width they may have a conditionality of discard, in which case under certain conditions they look like they have zero width for space-resolution purposes. Arved -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED] Sent: April 24, 2002 9:10 PM To: [EMAIL PROTECTED] Subject: Re: Spaces and precedence Arved Sandstrom wrote: Assuming Western reference-orienattion and writing mode, clause 3a of Section 4.2.5 indicates that if the border-after-width and padding-after of the first block are zero, and the border-before-width and padding-before of the second block are zero, that we have a block-stacking constraint. In which case the precedence on the space-fater of the one and the space-before of the other can be used precisely to achieve this collapsing effect. Thanks for the correction. I'll reread the spec again. J.Pietschmann
RE: Spaces and precedence
-Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED] Sent: April 24, 2002 5:17 PM To: [EMAIL PROTECTED] Subject: Re: Spaces and precedence Ralf Steppacher wrote: I have a short question about spaces and precedences: What I want is to suppress additional space if one headline directly follows another. To achieve this I wrote the template with FOs below but it does not work (I played a bit with attributes and values and could not find any other working solution using precendences). Could anybody please tell me whether my FO is wrong or this is a limitation of FOP? After having read the spec several times, i got the impression that space-*.precedence is for prioritizing space reservations coming from stuff from the same area. Roughly: fo:block space-before=10pt precedence=1 fo:block space-before=5pt precedence=2 stuff ... will put stuff 5pt after preceding content. This means, precedence can't be used to collapse space-after and space-before of consecutive blocks. Assuming Western reference-orienattion and writing mode, clause 3a of Section 4.2.5 indicates that if the border-after-width and padding-after of the first block are zero, and the border-before-width and padding-before of the second block are zero, that we have a block-stacking constraint. In which case the precedence on the space-fater of the one and the space-before of the other can be used precisely to achieve this collapsing effect. Regards, Arved Sandstrom
RE: Spaces and precedence
-Original Message- From: Arved Sandstrom [mailto:[EMAIL PROTECTED] Sent: April 24, 2002 6:38 PM To: [EMAIL PROTECTED] Subject: RE: Spaces and precedence -Original Message- From: J.Pietschmann [mailto:[EMAIL PROTECTED] Sent: April 24, 2002 5:17 PM To: [EMAIL PROTECTED] Subject: Re: Spaces and precedence Ralf Steppacher wrote: I have a short question about spaces and precedences: What I want is to suppress additional space if one headline directly follows another. To achieve this I wrote the template with FOs below but it does not work (I played a bit with attributes and values and could not find any other working solution using precendences). Could anybody please tell me whether my FO is wrong or this is a limitation of FOP? After having read the spec several times, i got the impression that space-*.precedence is for prioritizing space reservations coming from stuff from the same area. Roughly: fo:block space-before=10pt precedence=1 fo:block space-before=5pt precedence=2 stuff ... will put stuff 5pt after preceding content. This means, precedence can't be used to collapse space-after and space-before of consecutive blocks. Assuming Western reference-orienattion and writing mode, clause 3a of Section 4.2.5 indicates that if the border-after-width and padding-after of the first block are zero, and the border-before-width and padding-before of the second block are zero, that we have a block-stacking constraint. In which case the precedence on the space-fater of the one and the space-before of the other can be used precisely to achieve this collapsing effect. Regards, Arved Sandstrom Read orientation and space-after :-) orienattion is one of my top mistyping words (like retrun), but fater is new. :-) Normally I don't have 2 in one post. Drives me nuts. AHS
