Re: So much trouble getting FOP to use arabic

2007-03-09 Thread Jeremias Maerki
I think you somehow got the command wrong. GCJ (which you seem to be
using) tries to use part of the classpath as the main class. I can't
tell from your post how exactly you wrote the command. From my own
experiments I can tell that GCJ is rather special compared to other Java
tools. I've never had much success with it. I think you either have to
figure out how exactly you have to build the command for the TTFReader
with GCJ or you should install a Sun or Harmony JVM and proceed as
documented on the website.

Remember what Manuel told you: FOP may not satisfy your requirements
with arabic script as a lot of functionality in this area is still
missing. Good luck all the same.

On 08.03.2007 22:20:43 Rico Secada wrote:
 Hi
 
 I am trying to make a custom font for FOP to use, I am using the information 
 on the website. 
 
 I get the following error:
 
 build/fop.jar:lib/avalon-framework.jar:lib/xml-apis.jar:
 lib/xercesImpl.jar:lib/xalan.jar org.apache.fop.fonts.apps.TTFReader
 .fonts/Iqraa.ttf Iqraa.xml
 Exception in thread main java.lang.NoClassDefFoundError:
 lib.xercesImpl.jar:lib.xalan.jar
at gnu.java.lang.MainThread.run(libgcj.so.70)
 Caused by: java.lang.ClassNotFoundException:
 lib.xercesImpl.jar:lib.xalan.jar not found in
 gnu.gcj.runtime.SystemClassLoader{urls=[file:./],
 parent=gnu.gcj.runtime.ExtensionClassLoader{urls=[], parent=null}}
at java.net.URLClassLoader.findClass(libgcj.so.70)
at gnu.gcj.runtime.SystemClassLoader.findClass(libgcj.so.70)
at java.lang.ClassLoader.loadClass(libgcj.so.70)
at java.lang.ClassLoader.loadClass(libgcj.so.70)
at gnu.java.lang.MainThread.run(libgcj.so.70)
 
 What am I doing wrong?
 
 Best and kind regards,
 Rico


Jeremias Maerki


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: jEuclid-problem

2007-03-09 Thread Vincent Hennebert
Andreas L Delmelle a écrit :
 On Mar 8, 2007, at 22:02, Thomas Zastrow wrote:
 
 Hi Tom,
 
 Andreas L Delmelle schrieb:
 snip /
 Andreas, thank you for your help :-)
 
 You're welcome, of course.
 
 I'm not sure if I can help something, I have some Java-experience but
 don't want to mess up other's work.
 
 If you really want to help, all that needs to be changed/updated is the
 class org.apache.fop.mathml.MathMLElement (located in
 examples/mathml/src, to restore compatibility with the latest JEuclid.
 
 It only seems that JEuclid, in one of the last releases, has begun
 targeting Java 1.5 as a minimum. I can't say for sure whether no other
 problems will arise. FOP and Batik both still have a minimal target JVM
 of 1.3 (release FOP 0.93 / Batik 1.6). For FOP this should be 1.4 by the
 next release. This means we can't use Java 1.5 features like generics or
 typesafe enums internally in FOP, and I'm not sure whether the MathBase
 constructor will accept a standard Map, which would resolve to:
 MapObject, Object

That should be ok. You would have to use Java 1.5 to run FOP with
Jeuclid. You can use a non-generic map in the FOP code, you will only
get warnings from the compiler about non-typesafe checking. But the code
would still run.


 If this latter issue is only minor, and the updated MathBase constructor
 also accepts non-generic Maps, then updating the extension should prove
 to be a cake-walk. If the issue cannot be overcome, then I'm afraid this
 means that either:
 a) for the time being, FOP will remain incompatible with the latest
 JEuclid versions
 b) the need may arise for a separate MathML extension that is written in
 Java 5

Good luck!
Vincent

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Page break

2007-03-09 Thread pedro

Hi all
   another question.
  I have a module with 4 column.The first column is a product descripion and
the third is the price.Then when if the description is break on the new page
the prrice is on the same line of the first product description line but i
want that the price is dyplayed on the last line of the description


I have

Desc  |..  |   Price

The fop is   0,00  
a good to
ool
--new page
and is 
opensource


Desc  |..  |   Price

The fop is   
a good to
ool
--new page
and is 
opensource  0,0



The data is part of a table of the body template.




-- 
View this message in context: 
http://www.nabble.com/Page-break-tf3375024.html#a9392289
Sent from the FOP - Users mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



border-top-xxx and border-bottom-xxx causing wierd errors

2007-03-09 Thread nick humphrey

hi, i'm using ubuntu 6.10 edgy linux, jdk sun java version 1.5.0_08,
and the latest fop-trunk from svn
in my xslt i have the following line:
==code==
fo:block-container position=absolute left=0mm top=0mm font-size=10pt
border-left-color=red   
border-left-style=solid
border-left-width=1mm



==/code==

when i run fop from the command line it works fine:
./fop -xml ~/in.xml -xsl ~/in.xslt -pdf ~/out.pdf

but if i change that xml line to border-top-xxx or border-bottom-xxx
(where xxx is color style or width) i get this following errors:
=
9/03/2007 13:29:59 org.apache.fop.apps.FOUserAgent setTargetResolution
INFO: target-resolution set to: 72.0dpi (px2mm=0.3528)
9/03/2007 13:30:01 org.apache.fop.fo.FOTreeBuilder$MainFOHandler endElement
WARNING: Mismatch: page-sequence (http://www.w3.org/1999/XSL/Format)
vs. root (http://www.w3.org/1999/XSL/Format)
9/03/2007 13:30:01 org.apache.fop.fo.FOTreeBuilder fatalError
SEVERE: javax.xml.transform.TransformerException:
java.lang.IllegalStateException: lineWidth must be set and positive,
but it is: -2834
9/03/2007 13:30:01 org.apache.fop.cli.Main startFOP
SEVERE: Exception
javax.xml.transform.TransformerException:
java.lang.IllegalStateException: lineWidth must be set and positive,
but it is: -2834
   at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:168)
   at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
   at org.apache.fop.cli.Main.startFOP(Main.java:166)
   at org.apache.fop.cli.Main.main(Main.java:197)

-

; SystemID: file:///home/myself/in.xslt; Line#: 27; Column#: 57
javax.xml.transform.TransformerException:
java.lang.IllegalStateException: lineWidth must be set and positive,
but it is: -2834
   at 
org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2416)
   at 
org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(TransformerImpl.java:2281)
   at 
org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1367)
   at 
org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:709)
   at 
org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1284)
   at 
org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1262)
   at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:165)
   at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
   at org.apache.fop.cli.Main.startFOP(Main.java:166)
   at org.apache.fop.cli.Main.main(Main.java:197)
Caused by: java.lang.IllegalStateException: lineWidth must be set and
positive, but it is: -2834
   at 
org.apache.fop.layoutmgr.BreakingAlgorithm.getLineWidth(BreakingAlgorithm.java:1087)
   at 
org.apache.fop.layoutmgr.PageBreakingAlgorithm.getLineWidth(PageBreakingAlgorithm.java:853)
   at 
org.apache.fop.layoutmgr.PageBreakingAlgorithm.computeDifference(PageBreakingAlgorithm.java:367)
   at 
org.apache.fop.layoutmgr.BreakingAlgorithm.considerLegalBreak(BreakingAlgorithm.java:696)
   at 
org.apache.fop.layoutmgr.PageBreakingAlgorithm.considerLegalBreak(PageBreakingAlgorithm.java:309)
   at 
org.apache.fop.layoutmgr.BreakingAlgorithm.findBreakingPoints(BreakingAlgorithm.java:485)
   at 
org.apache.fop.layoutmgr.BreakingAlgorithm.findBreakingPoints(BreakingAlgorithm.java:403)
   at 
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:338)
   at 
org.apache.fop.layoutmgr.BlockContainerLayoutManager.getNextKnuthElementsAbsolute(BlockContainerLayoutManager.java:506)
   at 
org.apache.fop.layoutmgr.BlockContainerLayoutManager.getNextKnuthElements(BlockContainerLayoutManager.java:194)
   at 
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:106)
   at 
org.apache.fop.layoutmgr.PageSequenceLayoutManager$PageBreaker.getNextKnuthElements(PageSequenceLayoutManager.java:272)
   at 
org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:554)
   at 
org.apache.fop.layoutmgr.PageSequenceLayoutManager$PageBreaker.getNextBlockList(PageSequenceLayoutManager.java:264)
   at 
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:301)
   at 
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:263)
   at 
org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:157)
   at 
org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:385)
   at 
org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:148)
   at 
org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:378)
   at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:194)
   at 
org.apache.xml.serializer.ToXMLSAXHandler.endElement(ToXMLSAXHandler.java:261)
   

Re: Page break

2007-03-09 Thread Andreas L Delmelle

On Mar 9, 2007, at 11:53, pedro wrote:

Hi,

  I have a module with 4 column.The first column is a product  
descripion and
the third is the price.Then when if the description is break on the  
new page
the prrice is on the same line of the first product description  
line but i

want that the price is dyplayed on the last line of the description


In that case, you should use display-align=after on the cell  
containing the price.


Caution: if you're using FOP 0.93, I believe someone recently  
mentioned that FOP currently has problems with display-align=after  
when the cell's contents are broken over multiple pages...


HTH!

Andreas


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Page break

2007-03-09 Thread Vincent Hennebert
Hi,

Andreas L Delmelle a écrit :
 On Mar 9, 2007, at 11:53, pedro wrote:
 
 Hi,
 
   I have a module with 4 column.The first column is a product
 descripion and
 the third is the price.Then when if the description is break on the
 new page
 the prrice is on the same line of the first product description line
 but i
 want that the price is dyplayed on the last line of the description
 
 In that case, you should use display-align=after on the cell
 containing the price.
 
 Caution: if you're using FOP 0.93, I believe someone recently mentioned
 that FOP currently has problems with display-align=after when the
 cell's contents are broken over multiple pages...

It works more or less, but still there is no means to achieve Pedros's
needs I think. If you specify display-align=after on the cell
containing the price you will get the following result:

Desc  |..  |   Price

The fop is
a good to
ool  0,00
--new page
and is
opensource

There is enough space to put the price on the first page, so there is no
reason to put it on the second one. Of course, it will lie at the bottom
of the page, but the first one.

This behavior is compliant with the spec I think. Right now I can't
think of a way to achieve what you need. Maybe others have suggestions?

HTH,
Vincent

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Page break

2007-03-09 Thread Jeff Vannest
 I have a module with 4 column.The first column is a product descripion and
 the third is the price.Then when if the description is break on the new
page
 the prrice is on the same line of the first product description line but i
 want that the price is dyplayed on the last line of the description

I assume you're using table cells for the columns? Set the Price table cell
to align to the bottom. In HTML this would be:

td valign=bottom

In XSL-FO it is:

fo:table-cell display-align=after

Actually, you may wish to cause paragraphs not to break on page. In other
words, an entire description will always appear on the same page as its
price. In XSL-FO this is the keep-together=always attribute inside of the
table or cell element you wish to keep on the same page.

I hope that is helpful.

Regards,
Jeff




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Page break

2007-03-09 Thread Chris Bowditch

Vincent Hennebert wrote:

snip/


Desc  |..  |   Price

The fop is
a good to
ool  0,00
--new page
and is
opensource

There is enough space to put the price on the first page, so there is no
reason to put it on the second one. Of course, it will lie at the bottom
of the page, but the first one.

This behavior is compliant with the spec I think. Right now I can't
think of a way to achieve what you need. Maybe others have suggestions?


Well I think the best way to achieve a good looking result in this case 
is to prevent page breaks mid row using keep-together=always on the 
fo:table-row element. That way the price will always be aligned to the 
bottom of the description in the first column.


Chris




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: border-top-xxx and border-bottom-xxx causing wierd errors

2007-03-09 Thread Chris Bowditch

nick humphrey wrote:


hi, i'm using ubuntu 6.10 edgy linux, jdk sun java version 1.5.0_08,
and the latest fop-trunk from svn
in my xslt i have the following line:


snip/



when i run fop from the command line it works fine:
./fop -xml ~/in.xml -xsl ~/in.xslt -pdf ~/out.pdf

but if i change that xml line to border-top-xxx or border-bottom-xxx
(where xxx is color style or width) i get this following errors:
=
9/03/2007 13:29:59 org.apache.fop.apps.FOUserAgent setTargetResolution
INFO: target-resolution set to: 72.0dpi (px2mm=0.3528)
9/03/2007 13:30:01 org.apache.fop.fo.FOTreeBuilder$MainFOHandler endElement
WARNING: Mismatch: page-sequence (http://www.w3.org/1999/XSL/Format)
vs. root (http://www.w3.org/1999/XSL/Format)
9/03/2007 13:30:01 org.apache.fop.fo.FOTreeBuilder fatalError
SEVERE: javax.xml.transform.TransformerException:
java.lang.IllegalStateException: lineWidth must be set and positive,
but it is: -2834
9/03/2007 13:30:01 org.apache.fop.cli.Main startFOP
SEVERE: Exception
javax.xml.transform.TransformerException:
java.lang.IllegalStateException: lineWidth must be set and positive,
but it is: -2834
   at 
org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:168)

   at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
   at org.apache.fop.cli.Main.startFOP(Main.java:166)
   at org.apache.fop.cli.Main.main(Main.java:197)



snip/


i have been googling like crazy but finding no answers... anybody know
what might be wrong?


I think it is likely to be a classpath issue. The effects are similar 
when the wrong version of xerces/xalan is used to process the XML/XSL. 
Try to ensure you are using the xerces and xalan versions shipped with 
FOP. Use the endorsed mechanism to override any other xerces/xalan 
versions that your JDK might be picking up.


Chris






-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Typo in AbstractRenderer :: renderBlockViewPort

2007-03-09 Thread Paul Vinkenoog
Hi all,

In fop/render/AbstractRenderer.java, lines 453-462:

  protected void renderBlockViewport(BlockViewport bv, List children) {
  // clip and position viewport if necessary
  if (bv.getPositioning() == Block.ABSOLUTE) {
  // save positions
  int saveIP = currentIPPosition;
  int saveBP = currentBPPosition;

  Rectangle2D clippingRect = null;
  if (bv.getClip()) {
  clippingRect = new Rectangle(saveIP, saveBP, bv.getIPD(), 
bv.getIPD());

I suppose the second call to getIPD() should be getBPD(), unless you
want to force the clipping rect to be square.

At first I wanted to report this through Bugzilla, but the Getting
Help page stipulated that it should be raised at the user list first,
so here it is.


Kind regards,
Paul Vinkenoog

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: border-top-xxx and border-bottom-xxx causing wierd errors

2007-03-09 Thread nick humphrey

thanks for the reply chris =)


Try to ensure you are using the xerces and xalan versions shipped with FOP

not exactly sure how one does this..

you lost me here:
Use the endorsed mechanism to override any other xerces/xalan
versions that your JDK might be picking up.

what is the endorsed mechanism? sorry for my ignorance, and thanks in
advance for your help.


2007/3/9, Chris Bowditch [EMAIL PROTECTED]:

nick humphrey wrote:

 hi, i'm using ubuntu 6.10 edgy linux, jdk sun java version 1.5.0_08,
 and the latest fop-trunk from svn
 in my xslt i have the following line:

snip/


 when i run fop from the command line it works fine:
 ./fop -xml ~/in.xml -xsl ~/in.xslt -pdf ~/out.pdf

 but if i change that xml line to border-top-xxx or border-bottom-xxx
 (where xxx is color style or width) i get this following errors:
 =
 9/03/2007 13:29:59 org.apache.fop.apps.FOUserAgent setTargetResolution
 INFO: target-resolution set to: 72.0dpi (px2mm=0.3528)
 9/03/2007 13:30:01 org.apache.fop.fo.FOTreeBuilder$MainFOHandler endElement
 WARNING: Mismatch: page-sequence (http://www.w3.org/1999/XSL/Format)
 vs. root (http://www.w3.org/1999/XSL/Format)
 9/03/2007 13:30:01 org.apache.fop.fo.FOTreeBuilder fatalError
 SEVERE: javax.xml.transform.TransformerException:
 java.lang.IllegalStateException: lineWidth must be set and positive,
 but it is: -2834
 9/03/2007 13:30:01 org.apache.fop.cli.Main startFOP
 SEVERE: Exception
 javax.xml.transform.TransformerException:
 java.lang.IllegalStateException: lineWidth must be set and positive,
 but it is: -2834
at
 org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:168)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
at org.apache.fop.cli.Main.startFOP(Main.java:166)
at org.apache.fop.cli.Main.main(Main.java:197)


snip/

 i have been googling like crazy but finding no answers... anybody know
 what might be wrong?

I think it is likely to be a classpath issue. The effects are similar
when the wrong version of xerces/xalan is used to process the XML/XSL.
Try to ensure you are using the xerces and xalan versions shipped with
FOP. Use the endorsed mechanism to override any other xerces/xalan
versions that your JDK might be picking up.

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: Typo in AbstractRenderer :: renderBlockViewPort

2007-03-09 Thread Andreas L Delmelle

On Mar 9, 2007, at 15:43, Paul Vinkenoog wrote:

Hi Paul,


In fop/render/AbstractRenderer.java, lines 453-462:
snip /



I suppose the second call to getIPD() should be getBPD(), unless you
want to force the clipping rect to be square.


Looks like a typo indeed. I'll commit the change to the trunk shortly.


At first I wanted to report this through Bugzilla, but the Getting
Help page stipulated that it should be raised at the user list first,
so here it is.


Well, in fact this is slightly off-topic here, and belongs more on  
[EMAIL PROTECTED]
Bugzilla would not make it necessary for you to subscribe to that  
list to reach us there (only have to create a Bugzilla account)


But in any case, thanks for the vigilant eye!
If you encounter any more of these, please do report them.  
Ultimately, the quality of FOP depends greatly upon users like  
yourself, who are not afraid to take a stroll through the code, and  
don't assume that everything they see there is correct.



Cheers,

Andreas


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Typo in AbstractRenderer :: renderBlockViewPort

2007-03-09 Thread Paul Vinkenoog
Hello Andreas,

 At first I wanted to report this through Bugzilla, but the Getting
 Help page stipulated that it should be raised at the user list first,
 so here it is.

 Well, in fact this is slightly off-topic here, and belongs more on
 [EMAIL PROTECTED]

That's what I figured too, but being a relative newcomer I decided to
follow the published guidelines to the letter :-)

 Ultimately, the quality of FOP depends greatly upon users like
 yourself, who are not afraid to take a stroll through the code,

The reason I looked at the code at all was that I wanted to
re-implement the full internal link behaviour (landing on the exact
spot, that is). I've got it working now, need to iron out a few
wrinkles and then I'll bring it up on fop-dev. I hope it's usable for
the project too.


Kind regards,
Paul Vinkenoog

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: border-top-xxx and border-bottom-xxx causing wierd errors

2007-03-09 Thread Andreas L Delmelle

On Mar 9, 2007, at 15:48, nick humphrey wrote:

Hi,


thanks for the reply chris =)

Try to ensure you are using the xerces and xalan versions shipped  
with FOP

not exactly sure how one does this..

you lost me here:
Use the endorsed mechanism to override any other xerces/xalan
versions that your JDK might be picking up.

what is the endorsed mechanism? sorry for my ignorance, and thanks in
advance for your help.


The endorsed standards mechanism is yet another way to force  
overrides, global to your JVM, for the XML API implementations.


Look for the directory $JAVA_HOME$/lib/endorsed. (Create it if it  
does not exist.)
Move all the Xalan/Xerces related JARs from your $FOP_HOME$/lib  
directory there.


The JARs to be moved/copied are
serializer-2.7.0.jar
xalan-2.7.0.jar
xercesImpl-2.7.1.jar
xml-apis.jar

The next time you start your JVM, it uses the versions in the lib/ 
endorsed directory, instead of the ones on that are bundled with the  
Java distribution.



HTH!

Andreas


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Page break

2007-03-09 Thread pedro

Step by step...
The display align works fine but the  keep-together is not that i want.
If i set always on table my module miss the page break and if i set on
cell i don't see change.
Well ,my table is a dynamic table without fixed height..


[code]
xsl:template name=main-document.body
xsl:param name=document-to/
fo:flow flow-name=xsl-region-body
fo:table width=200mm border-collapse=collapse 
table-layout=fixed
border-color=black border-style=solid 
border-width=0.5pt 
fo:table-column column-width=85mm/
fo:table-column column-width=15mm/
fo:table-column column-width=20mm/
fo:table-column column-width=25mm/
fo:table-column column-width=15mm/
fo:table-column column-width=25mm/
fo:table-column column-width=15mm/
fo:table-header
fo:table-row
fo:table-cell 
background-color=rgb(192, 192, 192)
 
border-right-color=black

border-right-style=solid border-  right-width=0.5pt

border-bottom-color=black border-bottom-style=solid

border-bottom-width=0.5pt
fo:block 
font-family=Courier font-size=8pt text-align=left

margin-left=1mm font-weight=boldDescrizione/fo:block
/fo:table-cell
fo:table-cell 
background-color=rgb(192, 192, 192)
 
border-right-color=black

border-right-style=solid border-right-width=0.5pt

border-bottom-color=black border-bottom-style=solid

border-bottom-width=0.5pt
fo:block 
font-family=Courier font-size=8pt text-align=left

margin-left=1mm font-weight=boldU.M./fo:block
/fo:table-cell
fo:table-cell 
background-color=rgb(192, 192, 192)
 
border-right-color=black

border-right-style=solid border-right-width=0.5pt

border-bottom-color=black border-bottom-style=solid

border-bottom-width=0.5pt
fo:block 
font-family=Courier font-size=8pt text-align=left

margin-left=1mm font-weight=bold

Quantitxsl:text
disable-output-escaping=yes#38;#224;/xsl:text/fo:block
/fo:table-cell
fo:table-cell 
background-color=rgb(192, 192, 192)
 
border-right-color=black

border-right-style=solid border-right-width=0.5pt

border-bottom-color=black border-bottom-style=solid

border-bottom-width=0.5pt
fo:block 
font-family=Courier font-size=8pt text-align=left

margin-left=1mm font-weight=boldPrezzo/fo:block
/fo:table-cell
fo:table-cell 
background-color=rgb(192, 192, 192)
 
border-right-color=black

border-right-style=solid border-right-width=0.5pt

border-bottom-color=black border-bottom-style=solid

border-bottom-width=0.5pt
fo:block 
font-family=Courier font-size=8pt text-align=left
   

Re: Page break

2007-03-09 Thread Chris Bowditch

pedro wrote:


Step by step...
The display align works fine but the  keep-together is not that i want.
If i set always on table my module miss the page break and if i set on
cell i don't see change.


I'm not suggesting that you set keep-together on the entire table, i.e. 
fo:table element. I can understand that you may want your table 
spreading across more than one page. Neither am I suggesting you set 
keep-together on fo:table-cell. I don't think keep-together on a single 
table-cell in a row makes much sense. What I am suggesting is that you 
place keep-together on fo:table-row. Of course, this may also not be 
appropriate if you have long rows which you are expecting to take up 
more than a page or so.



Well ,my table is a dynamic table without fixed height..


It shouldn't matter.

Chris

snip/




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]