css2xslfo-support Mailing List for CSSToXSLFO (Page 8)
Brought to you by:
wdonne
Menu
▾
▴
css2xslfo-support — CSSToXSLFO support
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
(9) |
Apr
(6) |
May
(24) |
Jun
(14) |
Jul
|
Aug
(4) |
Sep
|
Oct
(1) |
Nov
|
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
|
Feb
(4) |
Mar
(17) |
Apr
(8) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
(2) |
| 2007 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(11) |
Jul
(2) |
Aug
(6) |
Sep
|
Oct
(1) |
Nov
(7) |
Dec
(5) |
| 2008 |
Jan
(2) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(12) |
Jul
(2) |
Aug
(4) |
Sep
(5) |
Oct
(21) |
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
|
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(16) |
Oct
|
Nov
|
Dec
|
|
From: Andreas J. <li...@an...> - 2005-05-24 15:26:18
|
--On Dienstag, 24. Mai 2005 17:03 Uhr +0200 Werner Donn=E9=20
<wer...@re...> wrote:
> Andreas,
>
> The page property on div.mybottom is set to "left" and you have only
> one page, which is at the right. If you remove the page property the
> bottom region will appear on both sides. If you want, for example,
> a different alignment for left and right pages, you can make two
> mybottoms and set the page property accordingly.
Ok. Now I am trying to add dynamic text from the H1 tag to the bottom
(taken from the manual). However the text from H1 tag does not show up.
Anything else I am missing?
Andreas
<html>
<head>
<style type=3D"text/css">
@page
{
margin-top: 35mm;
}
@page :left
{
margin-left: 15mm;
margin-right: 35mm;
}
@page :right
{
margin-left: 35mm;
margin-right: 15mm;
}
@media print {
div.mybottom {
region: bottom;
height: 2cm;
display: none;
}
div.mybottom > span.mark:before { content: string(mark); }
}
h1 { string-set: mark contents; }
</style>
</head>
<body>
<div class=3D"mybottom">
This should go to the bottom
<span class=3D"mark"/>
</div>
<h1>Hello world</h1>
<div class=3D"copyrightnotice">
labber labber.....
labber labber.....
</div>
</body>
</html>
|
|
From: <wer...@re...> - 2005-05-24 15:03:54
|
Andreas,
The page property on div.mybottom is set to "left" and you have only
one page, which is at the right. If you remove the page property the
bottom region will appear on both sides. If you want, for example,
a different alignment for left and right pages, you can make two
mybottoms and set the page property accordingly.
Regards,
Werner.
Andreas Jung wrote:
> Hello Werner,
>
> I am still fighting with some esoteric page formatting issues. I tried
> the following
> to put some text into the bottom region. However none of my renders
> (Xinc, XFC)
> output anything in the bottom region although the FO contains the text.
> Any ideas?
>
> Andreas
>
> ----------
>
> <html>
> <head>
> <style type="text/css">
>
> @page
> {
> margin-top: 35mm;
> }
>
> @page :left
> {
> margin-left: 15mm;
> margin-right: 35mm;
> }
>
> @page :right
> {
> margin-left: 35mm;
> margin-right: 15mm;
> }
>
> @media print {
> div.mybottom {
> region: bottom;
> page: left;
> height: 100pt;
> display: none;
> }
> }
>
> </style>
>
> </head>
>
> <body>
> <div class="mybottom">
> This should go to the bottom
> </div>
>
> <div class="copyrightnotice">
> labber labber.....
> </div>
> </body>
> </html>
>
>
--
Werner Donné -- Re BVBA
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803 e-mail: wer...@re...
|
|
From: Andreas J. <li...@an...> - 2005-05-24 14:43:31
|
Hello Werner,
I am still fighting with some esoteric page formatting issues. I tried the=20
following
to put some text into the bottom region. However none of my renders (Xinc,=20
XFC)
output anything in the bottom region although the FO contains the text. Any =
ideas?
Andreas
----------
<html>
<head>
<style type=3D"text/css">
@page
{
margin-top: 35mm;
}
@page :left
{
margin-left: 15mm;
margin-right: 35mm;
}
@page :right
{
margin-left: 35mm;
margin-right: 15mm;
}
@media print {
div.mybottom {
region: bottom;
page: left;
height: 100pt;
display: none;
}
}
</style>
</head>
<body>
<div class=3D"mybottom">
This should go to the bottom
</div>
<div class=3D"copyrightnotice">
labber labber.....
</div>
</body>
</html>
|
|
From: <wer...@re...> - 2005-05-23 14:31:19
|
Andreas, Indeed, I see it now. The value of your class attribute contains a "_", which is not legal in a CSS selector. The selector is therefore ignored. Regards, Werner. Andreas Jung wrote: > > > --On Montag, 23. Mai 2005 16:09 Uhr +0200 Werner Donné > <wer...@re...> wrote: > >> Andreas, >> >> Can you compare what you have with the attached working example? >> > > This works...I found the problem (don't know if it is one. > I used class="copyright_notice" in my DIV. I am not use if this is > forbidden > or not...anyway it causes some part of csstoxslfo to ignore the > corresponding > CSS statement. > > Sorry for the smoke, > ANdre > as -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: Andreas J. <li...@an...> - 2005-05-23 14:25:55
|
--On Montag, 23. Mai 2005 16:09 Uhr +0200 Werner Donn=E9 = <wer...@re...>=20 wrote: > Andreas, > > Can you compare what you have with the attached working example? > This works...I found the problem (don't know if it is one. I used class=3D"copyright_notice" in my DIV. I am not use if this is = forbidden or not...anyway it causes some part of csstoxslfo to ignore the=20 corresponding CSS statement. Sorry for the smoke, ANdreas |
|
From: <wer...@re...> - 2005-05-23 14:09:46
|
Andreas, Can you compare what you have with the attached working example? Werner. Andreas Jung wrote: > > > --On Montag, 23. Mai 2005 13:46 Uhr +0200 Werner Donné > <wer...@re...> wrote: > >> Hi Andreas, >> >> The border itself should be set too, e.g. "border: solid 0.2pt". >> > > This has no effect (my original code contained that already for > rendering a border > for the online layout. > > Andre > as -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: Andreas J. <li...@an...> - 2005-05-23 11:53:18
|
--On Montag, 23. Mai 2005 13:46 Uhr +0200 Werner Donn=E9 = <wer...@re...>=20 wrote: > Hi Andreas, > > The border itself should be set too, e.g. "border: solid 0.2pt". > This has no effect (my original code contained that already for rendering a = border for the online layout. Andreas |
|
From: <wer...@re...> - 2005-05-23 11:47:13
|
Hi Andreas,
The border itself should be set too, e.g. "border: solid 0.2pt".
Regards,
Werner.
Andreas Jung wrote:
> Hi Werner,
>
> sorry for boring you again.
>
> I have the following:
>
> div.copyright_notice {
> border-color: #000000;
> }
>
>
> ...
> <div class="copyright_notice">....</div>
>
> The generated FO files does not contain any border-color attribute.
> Bug or feature?
>
> Andre
> as
--
Werner Donné -- Re BVBA
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803 e-mail: wer...@re...
|
|
From: Andreas J. <li...@an...> - 2005-05-23 11:03:49
|
Hi Werner,
sorry for boring you again.
I have the following:
div.copyright_notice {
border-color: #000000;
}
...
<div class=3D"copyright_notice">....</div>
The generated FO files does not contain any border-color attribute.
Bug or feature?
Andreas |
|
From: <wer...@re...> - 2005-05-23 08:22:47
|
Hi Andreas, You can put an empty "colgroup" element in your table with the "span" attribute set to the number of columns and potentially other attributes that a "col" would inherit from "colgroup", according to the HTML spec. In order to determine the number of columns you can count the number of cells in the first row. Regards, Werner. Andreas Jung wrote: > Hello Werner, > > is there a trick to auto-generate table-column declarations? I've seen > that there is code in the > stylesheets but I could not figure out when table-column directives are > generated. > > Thanks, > Andre > as -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: Andreas J. <li...@an...> - 2005-05-23 08:04:32
|
Hello Werner, is there a trick to auto-generate table-column declarations? I've seen that = there is code in the stylesheets but I could not figure out when table-column directives are=20 generated. Thanks, Andreas |
|
From: <wer...@re...> - 2005-05-18 08:35:11
|
Hi Andreas, The manual contains such an example: http://www.re.be/css2xslfo/1_0rc2/manual.html. Its style sheet is embedded. Regards, Werner. Andreas Jung wrote: > > > --On Dienstag, 17. Mai 2005 16:45 Uhr +0200 Werner Donné > <wer...@re...> wrote: > >> Hi Andreas, >> >> I'm sorry, but the manual doesn't say that you need at least one @page >> rule for it to work. Without an @page rule the User Agent page set-up >> is generated. The regions are then not taken into account. I'll update >> the manual. > > > Do you have a quick example? > >> >> There are two other problems with your example. You should declare >> the XHTML namespace (xmlns="http://www.w3c.org/1999/xhtml" on html). >> Comments starting with "//" are not valid in CSS. You should use "/* ... >> */". >> The CSS parser appears to loose track because of this. > > > Ok, but the comments did not harm :-) > > Thanks, > Andre > as -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: Andreas J. <an...@an...> - 2005-05-18 08:23:20
|
--On Dienstag, 17. Mai 2005 16:45 Uhr +0200 Werner Donn=E9=20 <wer...@re...> wrote: > Hi Andreas, > > I'm sorry, but the manual doesn't say that you need at least one @page > rule for it to work. Without an @page rule the User Agent page set-up > is generated. The regions are then not taken into account. I'll update > the manual. Do you have a quick example? > > There are two other problems with your example. You should declare > the XHTML namespace (xmlns=3D"http://www.w3c.org/1999/xhtml" on html). > Comments starting with "//" are not valid in CSS. You should use "/* ... > */". > The CSS parser appears to loose track because of this. Ok, but the comments did not harm :-) Thanks, Andreas |
|
From: <wer...@re...> - 2005-05-17 14:46:22
|
Hi Andreas, I'm sorry, but the manual doesn't say that you need at least one @page rule for it to work. Without an @page rule the User Agent page set-up is generated. The regions are then not taken into account. I'll update the manual. There are two other problems with your example. You should declare the XHTML namespace (xmlns="http://www.w3c.org/1999/xhtml" on html). Comments starting with "//" are not valid in CSS. You should use "/* ... */". The CSS parser appears to loose track because of this. Regards, Werner. Andreas Jung wrote: > > > > --On Dienstag, 17. Mai 2005 13:20 Uhr +0200 Werner Donné > <wer...@re...> wrote: > >> Andreas, >> >> That is because div.top should have the "height" property. Because >> of its absence nothing is generated for div.top and hence also >> not for its child span.mark, for which the retrieve-marker code >> would have been generated. >> >> Werner. > > > I added "height: 100pt" to the div.top declarations but it does make a > difference. > > Andre > as -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: Andreas J. <an...@an...> - 2005-05-17 14:25:48
|
--On Dienstag, 17. Mai 2005 13:20 Uhr +0200 Werner Donn=E9=20 <wer...@re...> wrote: > Andreas, > > That is because div.top should have the "height" property. Because > of its absence nothing is generated for div.top and hence also > not for its child span.mark, for which the retrieve-marker code > would have been generated. > > Werner. I added "height: 100pt" to the div.top declarations but it does make a=20 difference. Andreas |
|
From: <wer...@re...> - 2005-05-17 11:21:07
|
Andreas, That is because div.top should have the "height" property. Because of its absence nothing is generated for div.top and hence also not for its child span.mark, for which the retrieve-marker code would have been generated. Werner. Andreas Jung wrote: > > > --On Dienstag, 17. Mai 2005 12:28 Uhr +0200 Werner Donné > <wer...@re...> wrote: > >> Hi Andreas, >> >> I think it is because the top region has no height and is therefore >> not generated at all. The rest seems ok to me. >> >> Best regards, >> >> Werner. >> > > I see that the generated FO contains <fo:marker > marker-class-name="mark">.... > but I don't see any code that looks like <fo:retrieve-marker > retrieve-class-name="mark"...>... > > Andreas > > > -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: Andreas J. <an...@an...> - 2005-05-17 10:41:40
|
--On Dienstag, 17. Mai 2005 12:28 Uhr +0200 Werner Donn=E9=20 <wer...@re...> wrote: > Hi Andreas, > > I think it is because the top region has no height and is therefore > not generated at all. The rest seems ok to me. > > Best regards, > > Werner. > I see that the generated FO contains <fo:marker=20 marker-class-name=3D"mark">.... but I don't see any code that looks like <fo:retrieve-marker=20 retrieve-class-name=3D"mark"...>... Andreas |
|
From: <wer...@re...> - 2005-05-17 10:28:53
|
Hi Andreas,
I think it is because the top region has no height and is therefore
not generated at all. The rest seems ok to me.
Best regards,
Werner.
Andreas Jung wrote:
> Hi,
>
> we are producing documents from HTML fragments where each fragment has a
> unique ID and title.
> In the output all fragments start on a new page. I would like that all
> pages have the
> corresponding ID and title somehow formatted as headline. Can I do that
> with css2xslfo?
> I tried to work with named strings but it does not work. Here is my code:
>
> <html>
> <head>
> <style type="text/css">
> // This is the main stylesheet for all export actions through FO
>
> h1 {
> font-size: 12pt;
> }
>
> div.document {
> break-after: page;
> hyphenation-remain-character-count: 3;
> hyphenation-push-character-count: 3;
> font-family: sans-serif;
> }
>
> .kursiv {
> font-style: italic;
> }
>
> .strich {
> text-decoration: underline;
> }
>
>
> div.top {
> region: top;
> display: none;
> }
>
> div.top > span.mark:before { content: string(mark); }
>
> h1 { string-set: mark contents; }
>
>
> </style>
> </head>
>
> <body tal:define="print_what options/print_what;
> was options/was|request/was|string:gldg;
> vonID options/vonID|request/vonID|nothing;
> bisID options/bisID|request/bisID|nothing;
> ">
>
> <div class="top">
> <span class="mark" />
> </div>
>
> <h1>sucks</h1>
>
> ....
>
>
> I would expect that 'sucks' appeared somewhere in the top region but the
> string is treated like a normal
> <h1> statement...any ideas?
>
> Thanks,
> Andre
> as
--
Werner Donné -- Re BVBA
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803 e-mail: wer...@re...
|
|
From: Andreas J. <an...@an...> - 2005-05-17 09:32:29
|
Hi,
we are producing documents from HTML fragments where each fragment has a=20
unique ID and title.
In the output all fragments start on a new page. I would like that all=20
pages have the
corresponding ID and title somehow formatted as headline. Can I do that=20
with css2xslfo?
I tried to work with named strings but it does not work. Here is my code:
<html>
<head>
<style type=3D"text/css">
// This is the main stylesheet for all export actions through FO
h1 {
font-size: 12pt;
}
div.document {
break-after: page;
hyphenation-remain-character-count: 3;
hyphenation-push-character-count: 3;
font-family: sans-serif;
}
.kursiv {
font-style: italic;
}
.strich {
text-decoration: underline;
}
div.top {
region: top;
display: none;
}
div.top > span.mark:before { content: string(mark); }
h1 { string-set: mark contents; }
</style>
</head>
<body tal:define=3D"print_what options/print_what;
was options/was|request/was|string:gldg;
vonID options/vonID|request/vonID|nothing;
bisID options/bisID|request/bisID|nothing;
">
<div class=3D"top">
<span class=3D"mark" />
</div>
<h1>sucks</h1>
....
I would expect that 'sucks' appeared somewhere in the top region but the=20
string is treated like a normal
<h1> statement...any ideas?
Thanks,
Andreas |
|
From: Grzegorz M. <cs...@wp...> - 2005-04-21 09:50:38
|
Matthias Wessendorf wrote:
> [INFO] area contents overflows area in line
Try to set style on all html elements, like this:
body, h1, h2, h3, p, div, [and others] {
hyphenate: false;
}
Should be good. An error ocures because elements don't fit in space
which FOP prepares for them and it tries to put them in next line (in
which they don't fit as well).
Grzegorz Makosa
|
|
From: <wer...@re...> - 2005-04-21 09:43:54
|
Hi Matthias, Your file is indeed valid and when you run css2xslfo you get valid XSL-FO. The way you start the FOP filter is also correct. I also get this endless loop, but I can't explain it. The XSL-FO file is quite trivial. It seems to be FOP problem. I suggest you run the css2xslfo.jar instead and take the resulting XSL-FO file and put a request to the FOP team with it. The attachted PDF file is what XEP4.3 makes of it. Regards, Werner. Matthias Wessendorf wrote: > Hi all, > > I have a valid XHTML doc like this > > --------------------------------------- > > <?xml version="1.0"?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > <html xmlns="http://www.w3.org/1999/xhtml"> > <head> > <title>Text des Titels</title> > </head> > <body> > > <ol> > <li>first</li> > <li>second</li> > </ol> > > </body> > </html> > > --------------------------------------- > > Now I use that command: > > C:\JavaLibs>java -jar css2fop1.jar test.html -pdf test.pdf > > but I become that messages.... in an endless loop. > > I thought the fop specific jar has a filter for Apache FOP? > > Any ideas, how to enalbe that filter? > > thanks, > matthias > > > -------------------------------messages------------------------------- > > [INFO] building formatting object tree > [INFO] setting up fonts > [ERROR] property - "text-transform" is not implemented yet. > [ERROR] property - "text-transform" is not implemented yet. > [INFO] [1] > [ERROR] Couldn't find hyphenation pattern en_GB > using general language pattern en instead. > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > [INFO] area contents overflows area in line > > > ------------------------------------------------------- > This SF.Net email is sponsored by: New Crystal Reports XI. > Version 11 adds new functionality designed to reduce time involved in > creating, integrating, and deploying reporting solutions. Free runtime info, > new features, or free trial, at: http://www.businessobjects.com/devxi/728 > _______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support > > -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: Matthias W. <mwe...@pi...> - 2005-04-21 09:28:02
|
Hi all,
I have a valid XHTML doc like this
---------------------------------------
<?xml version=3D"1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns=3D"http://www.w3.org/1999/xhtml">
<head>
<title>Text des Titels</title>
</head>
<body>
=20
<ol>
<li>first</li>
<li>second</li>
</ol>
</body>
</html>
---------------------------------------
Now I use that command:
C:\JavaLibs>java -jar css2fop1.jar test.html -pdf test.pdf
but I become that messages.... in an endless loop.
I thought the fop specific jar has a filter for Apache FOP?
Any ideas, how to enalbe that filter?
thanks,
matthias
-------------------------------messages-------------------------------
[INFO] building formatting object tree
[INFO] setting up fonts
[ERROR] property - "text-transform" is not implemented yet.
[ERROR] property - "text-transform" is not implemented yet.
[INFO] [1]
[ERROR] Couldn't find hyphenation pattern en_GB
using general language pattern en instead.
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
[INFO] area contents overflows area in line
|
|
From: Grzegorz M. <cs...@wp...> - 2005-04-11 14:26:14
|
Andreas Jung wrote:
> <html>
> <body>
> <table>
> <tr>
> <td>a</td>
> <td>b</td>
> </tr>
> <td>c</td>
> <td>d</td>
> <tr>
> </tr>
>
> </table>
>
> </body>
> </html>
FOP doesn't support "auto" size tables. You have to use fixed width. For
example:
<table>
<colgroup span="3">
<col width="20mm"/>
<col width="20mm"/>
<col width="60mm"/>
</colgroup>
<tr>
<td>a</td>
<td>b</td>
<td>c</td>
</tr>
</table>
So every table in your html (or pdf) page must have fixed width. It
looks like a problem now, but in future you'll see that it isn't as bad
as it was at the beginning :)
And, of course, you have to use other style on your table:
table {
width: 100%;
table-layout: fixed;
}
And I preffer mm as unit, because Browsers (like IE) visualise pixel
units in different style that Adobe Reader. Milimeters looks similar.
Grzegorz Makosa
|
|
From: <wer...@re...> - 2005-04-11 14:25:27
|
Hi Andreas, You should add <col width="..."/> elements in the table. Note that for FOP the width should be fixed. I also recommend to put a tbody around the tr elements. Regards, Werner. Andreas Jung wrote: > Hi, > > I am trying to convert a stupid table from HTML -> XHTML-> PDF. > I am using css2xfo for the FO generation and FO 0.20.5 for the PDF part. > This fails badly (the generated PDF is empty): > > That's the HTML file (which is internally converted to xhtml through tidy): > > ung@localhost:/develop/repository/Haufe/Entwickler/ajung/converters: cat > out.html > <html> > <body> > <table> > <tr> > <td>a</td> > <td>b</td> > </tr> > <td>c</td> > <td>d</td> > <tr> > </tr> > > </table> > > </body> > </html> > > > Output of FO: > > ajung@localhost:/develop/repository/Haufe/Entwickler/ajung/converters: > python2.3 test.py out.html > Konvertiere out.html nach PDF|RTF|PS via XSL-FO > [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser > [INFO] FOP 0.20.5 > [INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser > [INFO] building formatting object tree > [INFO] setting up fonts > [ERROR] property - "text-transform" is not implemented yet. > [ERROR] property - "text-transform" is not implemented yet. > [ERROR] Error in padding-bottom property value '0': > org.apache.fop.fo.expr.PropertyException: No conversion defined > [ERROR] Error in padding-left property value '0': > org.apache.fop.fo.expr.PropertyException: No conversion defined > [ERROR] Error in padding-right property value '0': > org.apache.fop.fo.expr.PropertyException: No conversion defined > [ERROR] Error in padding-top property value '0': > org.apache.fop.fo.expr.PropertyException: No conversion defined > [INFO] [1] > [WARNING] table-layout=auto is not supported, using fixed! > [WARNING] current implementation of tables requires a table-column for > each column, indicating column-width > [INFO] Parsing of document complete, stopping renderer > > I have no idea how to get this simple table converted. Any help is > appreciated. > > Andrea > s -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: Andreas J. <li...@an...> - 2005-04-11 14:09:27
|
Hi,
I am trying to convert a stupid table from HTML -> XHTML-> PDF.
I am using css2xfo for the FO generation and FO 0.20.5 for the PDF part.
This fails badly (the generated PDF is empty):
That's the HTML file (which is internally converted to xhtml through tidy):
ung@localhost:/develop/repository/Haufe/Entwickler/ajung/converters: cat=20
out.html
<html>
<body>
<table>
<tr>
<td>a</td>
<td>b</td>
</tr>
<td>c</td>
<td>d</td>
<tr>
</tr>
</table>
</body>
</html>
Output of FO:
ajung@localhost:/develop/repository/Haufe/Entwickler/ajung/converters:=20
python2.3 test.py out.html
Konvertiere out.html nach PDF|RTF|PS via XSL-FO
[INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser
[INFO] FOP 0.20.5
[INFO] Using org.apache.xerces.parsers.SAXParser as SAX2 Parser
[INFO] building formatting object tree
[INFO] setting up fonts
[ERROR] property - "text-transform" is not implemented yet.
[ERROR] property - "text-transform" is not implemented yet.
[ERROR] Error in padding-bottom property value '0':=20
org.apache.fop.fo.expr.PropertyException: No conversion defined
[ERROR] Error in padding-left property value '0':=20
org.apache.fop.fo.expr.PropertyException: No conversion defined
[ERROR] Error in padding-right property value '0':=20
org.apache.fop.fo.expr.PropertyException: No conversion defined
[ERROR] Error in padding-top property value '0':=20
org.apache.fop.fo.expr.PropertyException: No conversion defined
[INFO] [1]
[WARNING] table-layout=3Dauto is not supported, using fixed!
[WARNING] current implementation of tables requires a table-column for each =
column, indicating column-width
[INFO] Parsing of document complete, stopping renderer
I have no idea how to get this simple table converted. Any help is=20
appreciated.
Andreas |
