css2xslfo-support Mailing List for CSSToXSLFO (Page 6)
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: Brad C. <bk...@mu...> - 2006-04-04 19:08:36
|
I am trying to get version 1.3 of CSSToFOPNew to load xhtml via a url, but it always ignores the url and instead reads from stdin. It doesn't generate an error when a url is specified. It just ignores it. ie ./csstofop http://somewhere.com/somefile.htm -ps /tmp/test.ps always tries to read from stdin. I have to use links -source 1 http://somewhere.com/somefile.htm | ./csstofop -ps /tmp/test.ps Is this a known bug? For output, I'd like to pipe the postscript output to lpr, but can't seem to do that without using /dev/stdout. Also, the -q option isn't supported by CSSToFOPNew I tried. ./csstofop -ps - that doesn't work.. and FOP libraries output lots of debugging stuff I don't need to see. I can work around these issues with another script, but just a heads up that at least reading from a url doesn't seem to work. -- Brad Clements, bk...@mu... (315)268-1000 http://www.murkworks.com AOL-IM or SKYPE: BKClements |
|
From: Brad C. <bk...@mu...> - 2006-04-04 14:08:39
|
On 4 Apr 2006 at 9:23, Andreas Jung wrote:
> Werner,
>
> I am trying to upgrade from V 1.0 to V 1.3 but having problems
> with page regions again. The code of the attached html file is taken
> from the 1.3 manual however I don't see the page numbers on the
> pdf/rtf (using XINC, XFC).
>
div.bottom-left
{
height: 15mm;
page: left;
region: bottom;
text-align: left;
}
Maybe you need to add
width:100%;
precedence: true;
?
not sure, but comparing your source to my source, that's the only difference I
have. Maybe 15mm isn't tall enough for your current font?
--
Brad Clements, bk...@mu... (315)268-1000
http://www.murkworks.com
AOL-IM or SKYPE: BKClements
|
|
From: Andreas J. <li...@an...> - 2006-04-04 07:23:41
|
Werner, I am trying to upgrade from V 1.0 to V 1.3 but having problems with page regions again. The code of the attached html file is taken from the 1.3 manual however I don't see the page numbers on the pdf/rtf (using XINC, XFC). Andreas |
|
From: <wer...@re...> - 2006-03-14 08:32:44
|
Hi Brad,
See my inline comments.
Best regards,
Werner.
Brad Clements wrote:
> I found something odd with 1.3, I am thinking I'm doing something wrong=
.
>=20
> I have an xhtml document with embedded stylesheet. It works fine in Fir=
efox.
>=20
> In part, I have this style:
>=20
> div.invoice_header {
> font-size:9pt;
> region: top;
> precedence: true;
> width:100%;
> height: 3in;
> }
>=20
>=20
> Then, in the body, I have this:
>=20
> <body>
> <div class=3D"invoice_header" >
> <table style=3D"table-layout:fixed;width:100%;">
> <col width=3D"1*" />
> <col width=3D"1*" />
>=20
> (snipped)
>=20
>=20
> What happens is the div is not treated as a top region, instead it's pu=
t into the=20
> body flow. If I change the color in the stylesheet, the changed color i=
s reflected=20
> correctly in the browser, but not in the postscript output from fop. So=
I think=20
> csstoxslfo isn't connecting the div class to the stylesheet.
>=20
> I used to have <table class=3D"invoice_header"> and that worked ok.
>=20
> But when I changed from table to div, region activation of the div stop=
ped=20
> working.
>=20
> To make this work, I have to do add a style statement to the div:
>=20
>=20
> style=3D"region:top;height:3in"
>=20
>=20
> Am I doing something wrong?
This is because of the underscore in "invoice_header". The underscore is =
not a
legal CSS character, which makes it an illegal rule and those should be i=
gnored
according to the spec.
>=20
> --
>=20
> I am not sure what @page name to use.. I'm doing onsided output, so I =
have this=20
> in my embedded stylesheet:
>=20
>=20
> @page onesided
> {
> margin:1%;
> }=20
>=20
> What I really want to do is to reduce the margins on all pages. I also =
tried
>=20
> margin: 0.25in 0.25in 0.25in 0.25in=20
>=20
> But that had no effect either.
>=20
> How do I set the margins for all pages to be the same smaller size than=
the=20
> default?
>=20
> What page names *should* I be using to apply to "the default starting p=
age". In=20
> the case of onesided, I guess I have first-onesided and onesided.. That=
it?
>=20
In this case you can use an anonymous page. The following should work:
@page
{
margin: 10%;
}
For your first page you can then say:
@page :first
{
margin: 20%;
}
> --
>=20
> I use table-layout:fixed;width:100% everywhere in my document, but I st=
ill get=20
> these complaints:
>=20
> INFO: table-layout=3D"fixed" and width=3D"auto", but auto-layout not su=
pported =3D>=20
> assuming width=3D"100%"
>=20
> But width is already 100% on the table, maybe it's complaining about th=
e width of=20
> the parent div? =20
>=20
I think at least one of the columns has no explicit width. Combined with =
the
100% on the table this comes down to automatic table layout.
> --
>=20
> It seems that width units 'ex' is not allowed, but 'em' works. Is that =
a FOP=20
> limitation?
>=20
> or, is 'ex' an html -only thing?
In CSS ex is a valid unit, but not in XSL-FO. I should document that.
>=20
>=20
>=20
>=20
>=20
--=20
Werner Donn=E9 -- Re BVBA
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803 e-mail: wer...@re...
|
|
From: Brad C. <bk...@mu...> - 2006-03-13 20:14:04
|
I found something odd with 1.3, I am thinking I'm doing something wrong.
I have an xhtml document with embedded stylesheet. It works fine in Firefox.
In part, I have this style:
div.invoice_header {
font-size:9pt;
region: top;
precedence: true;
width:100%;
height: 3in;
}
Then, in the body, I have this:
<body>
<div class="invoice_header" >
<table style="table-layout:fixed;width:100%;">
<col width="1*" />
<col width="1*" />
(snipped)
What happens is the div is not treated as a top region, instead it's put into the
body flow. If I change the color in the stylesheet, the changed color is reflected
correctly in the browser, but not in the postscript output from fop. So I think
csstoxslfo isn't connecting the div class to the stylesheet.
I used to have <table class="invoice_header"> and that worked ok.
But when I changed from table to div, region activation of the div stopped
working.
To make this work, I have to do add a style statement to the div:
style="region:top;height:3in"
Am I doing something wrong?
--
I am not sure what @page name to use.. I'm doing onsided output, so I have this
in my embedded stylesheet:
@page onesided
{
margin:1%;
}
What I really want to do is to reduce the margins on all pages. I also tried
margin: 0.25in 0.25in 0.25in 0.25in
But that had no effect either.
How do I set the margins for all pages to be the same smaller size than the
default?
What page names *should* I be using to apply to "the default starting page". In
the case of onesided, I guess I have first-onesided and onesided.. That it?
--
I use table-layout:fixed;width:100% everywhere in my document, but I still get
these complaints:
INFO: table-layout="fixed" and width="auto", but auto-layout not supported =>
assuming width="100%"
But width is already 100% on the table, maybe it's complaining about the width of
the parent div?
--
It seems that width units 'ex' is not allowed, but 'em' works. Is that a FOP
limitation?
or, is 'ex' an html -only thing?
--
Brad Clements, bk...@mu... (315)268-1000
http://www.murkworks.com
AOL-IM or SKYPE: BKClements
|
|
From: <wer...@re...> - 2006-03-13 14:17:46
|
Hi Brad, I indeed forgot to mention the class name, which is necessary to build the command-line, in the manual. Thanks for reporting it. In the table columns you can use the "1*" syntax for the width attribute. The "pcw" unit is for setting the width property in a CSS style sheet. Best regards, Werner. Brad Clements wrote: > On 13 Mar 2006 at 12:01, Werner Donn=E9 wrote: >=20 >> Hi Brad, >> >> The command-line in my script is as follows: >> >> fop=3D/var/local/fop-0.91beta >> java -Xbootclasspath/p:/var/local/saxon-8.4/saxon8.jar -cp \ >> $fop/build/fop.jar:$fop/lib/avalon-framework-4.2.0.jar:$fop/lib/bati >> k-all-1.6.jar:$fop/lib/commons-io-1.1.jar:$fop/lib/commons-logging-1 >> .0.4.jar:$fop/lib/serializer-2.7.0.jar:$fop/lib/css2fopnew.jar \ >> be.re.css.CSSToFOPNew $* >> >=20 > Thanks, that solved the problem. >=20 > I keep forgetting that using -cp with java disables -jar >=20 > The css_to_xslfo_manual doesn't mention be.re.css.CSSToFOPNew class, it > says: >=20 > For fop 0.20.5: >> java -jar css2fop.jar url_or_filename <options> > For fop 0.91beta you should create a classpath with css2fopnew.jar, > fop.jar and all > the jar files in the fop lib directory. >=20 > So, java newbies like me kinda skip over the fact that -jar won't work > with -cp >=20 >> Regarding to your second problem, have you set a width on the "col" >> elements? >=20 > Yes >=20 > <col width=3D"50%" /> >=20 > All my widths are in %, should I use pcw instead? >=20 > --=20 > Brad Clements, bk...@mu... (315)268-1000 > http://www.murkworks.com =20 > AOL-IM or SKYPE: BKClements >=20 --=20 Werner Donn=E9 -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: Brad C. <bk...@mu...> - 2006-03-13 14:01:26
|
On 13 Mar 2006 at 12:01, Werner Donn=E9 wrote: > Hi Brad, > > The command-line in my script is as follows: > > fop=3D/var/local/fop-0.91beta > java -Xbootclasspath/p:/var/local/saxon-8.4/saxon8.jar -cp \ > $fop/build/fop.jar:$fop/lib/avalon-framework-4.2.0.jar:$fop/lib/bati > k-all-1.6.jar:$fop/lib/commons-io-1.1.jar:$fop/lib/commons-logging-1 > .0.4.jar:$fop/lib/serializer-2.7.0.jar:$fop/lib/css2fopnew.jar \ > be.re.css.CSSToFOPNew $* > Thanks, that solved the problem. I keep forgetting that using -cp with java disables -jar The css_to_xslfo_manual doesn't mention be.re.css.CSSToFOPNew class, it says: For fop 0.20.5: > java -jar css2fop.jar url_or_filename <options> For fop 0.91beta you should create a classpath with css2fopnew.jar, fop.jar and all the jar files in the fop lib directory. So, java newbies like me kinda skip over the fact that -jar won't work wit= h -cp > Regarding to your second problem, have you set a width on the "col" > elements? Yes <col width=3D"50%" /> All my widths are in %, should I use pcw instead? -- Brad Clements, bk...@mu... (315)268-1000 http://www.murkworks.com AOL-IM or SKYPE: BKClements |
|
From: <wer...@re...> - 2006-03-13 12:48:20
|
Andreas,
I'm still puzzled by this. I just downloaded Xinc 2.0.2 and there
I see the correct margins around the block that corresponds to
div.outline.
Best regards,
Werner.
Andreas Jung wrote:
> Thanks,
>=20
> I am using XFC 2.3 and Xinc 2.02. I hacked around the issue by modifyin=
g
> the css.xsl stylesheet and by adding some post-processing on the
> generated FO file...this works for us now. I'll try to upgrade to
> csstoxslfo 1.3
> for the next major release of our products and hope to solve this is a
> more sane way.
>=20
> Andreas
>=20
> --On 13. M=E4rz 2006 11:56:01 +0100 Werner Donn=E9 <wer...@re...>=
wrote:
>=20
>> Hi Andreas,
>>
>> I have attached the output of Xinc 2.0.1 using CSSToXSLFO 1.0, but fir=
st
>> I have set the space-after to "0.0em" in order to show the difference.
>> The top margin is there and the bottom margin is 0. I have also added
>> the RTF file generated with XFC 2.1. It shows the same result. Are we
>> using the same version of Xinc and XFC?
>>
>> The reason for replacing margin-top with space-before and margin-botto=
m
>> with space-after is the treatment of conditionality. For the space-*
>> properties it is "discard", while for the margin-* properties it is se=
t
>> to "retain". The XSL-FO 1.0 spec says it is for compatibility with CSS=
2.
>> In other words, CSSToXSLFO is not compliant with CSS2 in this regard.
>>
>> I did it at the time, because in most cases a top margin is not desire=
d
>> when a a block is the first in a reference area. If the CSS2 behaviour
>> would be followed, the CSSToXSLFO user should be aware of when a
>> reference area is generated and when not and in the appropriate places
>> the style sheet should written to set the margin-top to 0 explicitly.
>> There are two problems with this. First, the user is not aware of the
>> difference between reference areas and normal areas, nor he should be.
>> Second, style sheets become much more complicated and it will cause a
>> lot of trial and error, because you don't always know when to expect
>> a reference area. For example, say you have a top margin for the "h1"
>> element. For the first one you need a special rule ("first-child") to
>> set it to 0.
>>
>> Best regards,
>>
>> Werner.
>>
>> Andreas Jung wrote:
>>>
>>>
>>> --On 6. M=E4rz 2006 10:38:52 +0100 Werner Donn=E9 <wer...@re...=
>
>>> wrote:
>>>
>>>> Hi Andreas,
>>>>
>>>> I tried it with version 1.0 as well as 1.3 and the margin is there.
>>>> Set it to zero to see the difference. It is not part of the content
>>>> rectangle however, which is why the background doesn't reach that fa=
r.
>>>> If that is what you want you should use padding instead of margin.
>>>>
>>>>
>>>
>>> This issue seems to depend very much on the converter. Neither with X=
inc
>>> nor XFC I can see the top/bottom margin. I investigated the generated=
FO
>>> file.
>>> The related fo:block has margin-top|bottom set to 0em but uses
>>> space-after|before to specify the margin. Replacing
>>> space-after|space-before with margin-bottom|top let the margins work.=
Is
>>> there any reason why you use space-after|before vs. border-bottom|top=
?
>>>
>>> What is the recommend way to get around this issue?
>>>
>>> Andreas
>>>
>>>
>>
>> --=20
>> Werner Donn=E9 -- Re BVBA
>> Engelbeekstraat 8
>> B-3300 Tienen
>> tel: (+32) 486 425803 e-mail: wer...@re...
>=20
>=20
>=20
--=20
Werner Donn=E9 -- Re BVBA
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803 e-mail: wer...@re...
|
|
From: <wer...@re...> - 2006-03-13 12:12:46
|
Hi Andreas, The repetition of the marker seems to be a Xinc bug indeed. With XEP it works as expected. With FOP it is also repeated, but there the formatting is copied from the flow too, which is a bug in FOP. According to the XFC manual marker elements are not supported, which is why nothing appears at all. Best regards, Werner. Andreas Jung wrote: > I attach an archive with some files. The RTF is generated with XFC, the= PDF > using Xinc. As far as I can remember XFC does not support the related > way how csstoslfo generates the code. But it would be nice to have this > feature > for PDF....it could be a Xinc bug as well.. >=20 > Andreas >=20 > --On 20. Februar 2006 10:24:17 +0100 Werner Donn=E9 <wer...@re...= > > wrote: >=20 >> Hi Andreas, >> >> This is supposed to be the default behaviour. The manual also >> uses this feature. Can you send me the example? I'll investigate >> it. >> >> Best regards, >> >> Werner. >> >> Andreas Jung wrote: >>> I am (still) using csstoxslfo 1.0. I want to use named strings to >>> put the value of titles within <h1> into the headline. This works so >>> far. >>> However when headline does not show the latest title from the latest = h1 >>> element when there are multiple pages between two h1 tags. Is there a >>> workaround to show the values of named strings on every page until th= e >>> value changes the next time? >>> >>> Andre >>> as >> >> --=20 >> Werner Donn=E9 -- Re BVBA >> Engelbeekstraat 8 >> B-3300 Tienen >> tel: (+32) 486 425803 e-mail: wer...@re... >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. Do you grep through log >> files for problems? Stop! Download the new AJAX search engine that >> makes >> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK= ! >> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&da= t=3D121642 >> _______________________________________________ >> css2xslfo-support mailing list >> css...@li... >> https://lists.sourceforge.net/lists/listinfo/css2xslfo-support >=20 >=20 >=20 --=20 Werner Donn=E9 -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: Andreas J. <li...@an...> - 2006-03-13 11:06:15
|
Thanks,
I am using XFC 2.3 and Xinc 2.02. I hacked around the issue by modifying
the css.xsl stylesheet and by adding some post-processing on the generated=20
FO file...this works for us now. I'll try to upgrade to csstoxslfo 1.3
for the next major release of our products and hope to solve this is a more =
sane way.
Andreas
--On 13. M=C3=A4rz 2006 11:56:01 +0100 Werner Donn=C3=A9 =
<wer...@re...> wrote:
> Hi Andreas,
>
> I have attached the output of Xinc 2.0.1 using CSSToXSLFO 1.0, but first
> I have set the space-after to "0.0em" in order to show the difference.
> The top margin is there and the bottom margin is 0. I have also added
> the RTF file generated with XFC 2.1. It shows the same result. Are we
> using the same version of Xinc and XFC?
>
> The reason for replacing margin-top with space-before and margin-bottom
> with space-after is the treatment of conditionality. For the space-*
> properties it is "discard", while for the margin-* properties it is set
> to "retain". The XSL-FO 1.0 spec says it is for compatibility with CSS2.
> In other words, CSSToXSLFO is not compliant with CSS2 in this regard.
>
> I did it at the time, because in most cases a top margin is not desired
> when a a block is the first in a reference area. If the CSS2 behaviour
> would be followed, the CSSToXSLFO user should be aware of when a
> reference area is generated and when not and in the appropriate places
> the style sheet should written to set the margin-top to 0 explicitly.
> There are two problems with this. First, the user is not aware of the
> difference between reference areas and normal areas, nor he should be.
> Second, style sheets become much more complicated and it will cause a
> lot of trial and error, because you don't always know when to expect
> a reference area. For example, say you have a top margin for the "h1"
> element. For the first one you need a special rule ("first-child") to
> set it to 0.
>
> Best regards,
>
> Werner.
>
> Andreas Jung wrote:
>>
>>
>> --On 6. M=C3=A4rz 2006 10:38:52 +0100 Werner Donn=C3=A9 =
<wer...@re...>
>> wrote:
>>
>>> Hi Andreas,
>>>
>>> I tried it with version 1.0 as well as 1.3 and the margin is there.
>>> Set it to zero to see the difference. It is not part of the content
>>> rectangle however, which is why the background doesn't reach that far.
>>> If that is what you want you should use padding instead of margin.
>>>
>>>
>>
>> This issue seems to depend very much on the converter. Neither with Xinc
>> nor XFC I can see the top/bottom margin. I investigated the generated FO
>> file.
>> The related fo:block has margin-top|bottom set to 0em but uses
>> space-after|before to specify the margin. Replacing
>> space-after|space-before with margin-bottom|top let the margins work. Is
>> there any reason why you use space-after|before vs. border-bottom|top?
>>
>> What is the recommend way to get around this issue?
>>
>> Andreas
>>
>>
>
> --
> Werner Donn=C3=A9 -- Re BVBA
> Engelbeekstraat 8
> B-3300 Tienen
> tel: (+32) 486 425803 e-mail: wer...@re...
|
|
From: <wer...@re...> - 2006-03-13 11:00:29
|
Hi Brad, The command-line in my script is as follows: fop=3D/var/local/fop-0.91beta java -Xbootclasspath/p:/var/local/saxon-8.4/saxon8.jar -cp \ $fop/build/fop.jar:$fop/lib/avalon-framework-4.2.0.jar:$fop/lib/batik-a= ll-1.6.jar:$fop/lib/commons-io-1.1.jar:$fop/lib/commons-logging-1.0.4.jar= :$fop/lib/serializer-2.7.0.jar:$fop/lib/css2fopnew.jar \ be.re.css.CSSToFOPNew $* You can add the system property "be.re.stack" with -Dbe.re.stack to get full stack traces when there is an exception. Regarding to your second problem, have you set a width on the "col" elements? Best regards, Werner. Brad Clements wrote: > Hi, >=20 > I'm trying to run css2fopnew1_3.jar with fop 0.91 beta. >=20 > I've copied all the lib .jar files and fop.jar into the same directory = as=20 > css2fopnew1_3.jar. >=20 > I get this error: >=20 > $JAVA_HOME/bin/java -jar css2fopnew1_3.jar ~/temp/packing_slip.xml.htm = -ps=20 > /tmp/packingslip.ps >=20 > org/apache/avalon/framework/configuration/ConfigurationException >=20 >=20 > I've also tried building up an explicit .jar list for -cp (just used a = mangled fop sh=20 > script), I get the same results >=20 > am I required to have a configuration file? I assume it's fop.xconf.. s= o I tried this=20 > too: >=20 > $JAVA_HOME/bin/java -jar css2fopnew1_3.jar -fc ../fop-0.91beta/conf/fop= .xconf =20 > ~/temp/packing_slip.xml.htm -ps /tmp/packingslip.ps >=20 > org/apache/avalon/framework/configuration/ConfigurationException >=20 >=20 > Same error. >=20 > How can I get a full traceback to debug this? >=20 > ---- >=20 > Unrelated, I'm using css2xslfo1_3.jar in the meantime. >=20 > I have source xhtml with two tables, both tables specify style=3D"table= - > layout:fixed;width:100%" and have <col /> elements. >=20 > But fop complains the same for each table: >=20 > table-layout=3D"fixed" and width=3D"auto", but auto-layout not supporte= d =3D> assuming=20 > width=3D"100%" > table-layout=3D"fixed" and width=3D"auto", but auto-layout not supporte= d =3D> assuming=20 > width=3D"100%" > table-layout=3D"fixed" and width=3D"auto", but auto-layout not supporte= d =3D> assuming=20 > width=3D"100%" >=20 > strange, eh? >=20 >=20 >=20 --=20 Werner Donn=E9 -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: <wer...@re...> - 2006-03-13 10:55:09
|
Hi Andreas,
I have attached the output of Xinc 2.0.1 using CSSToXSLFO 1.0, but first
I have set the space-after to "0.0em" in order to show the difference.
The top margin is there and the bottom margin is 0. I have also added
the RTF file generated with XFC 2.1. It shows the same result. Are we
using the same version of Xinc and XFC?
The reason for replacing margin-top with space-before and margin-bottom
with space-after is the treatment of conditionality. For the space-*
properties it is "discard", while for the margin-* properties it is set
to "retain". The XSL-FO 1.0 spec says it is for compatibility with CSS2.
In other words, CSSToXSLFO is not compliant with CSS2 in this regard.
I did it at the time, because in most cases a top margin is not desired
when a a block is the first in a reference area. If the CSS2 behaviour
would be followed, the CSSToXSLFO user should be aware of when a
reference area is generated and when not and in the appropriate places
the style sheet should written to set the margin-top to 0 explicitly.
There are two problems with this. First, the user is not aware of the
difference between reference areas and normal areas, nor he should be.
Second, style sheets become much more complicated and it will cause a
lot of trial and error, because you don't always know when to expect
a reference area. For example, say you have a top margin for the "h1"
element. For the first one you need a special rule ("first-child") to
set it to 0.
Best regards,
Werner.
Andreas Jung wrote:
>=20
>=20
> --On 6. M=E4rz 2006 10:38:52 +0100 Werner Donn=E9 <wer...@re...> =
wrote:
>=20
>> Hi Andreas,
>>
>> I tried it with version 1.0 as well as 1.3 and the margin is there.
>> Set it to zero to see the difference. It is not part of the content
>> rectangle however, which is why the background doesn't reach that far.
>> If that is what you want you should use padding instead of margin.
>>
>>
>=20
> This issue seems to depend very much on the converter. Neither with Xin=
c
> nor XFC I can see the top/bottom margin. I investigated the generated F=
O
> file.
> The related fo:block has margin-top|bottom set to 0em but uses
> space-after|before to specify the margin. Replacing
> space-after|space-before with margin-bottom|top let the margins work. I=
s
> there any reason why you use space-after|before vs. border-bottom|top?
>=20
> What is the recommend way to get around this issue?
>=20
> Andreas
>=20
>=20
--=20
Werner Donn=E9 -- Re BVBA
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803 e-mail: wer...@re...
|
|
From: Andreas J. <li...@an...> - 2006-03-13 09:50:37
|
I attach an archive with some files. The RTF is generated with XFC, the PDF using Xinc. As far as I can remember XFC does not support the related way how csstoslfo generates the code. But it would be nice to have this feature for PDF....it could be a Xinc bug as well.. Andreas --On 20. Februar 2006 10:24:17 +0100 Werner Donné <wer...@re...> wrote: > Hi Andreas, > > This is supposed to be the default behaviour. The manual also > uses this feature. Can you send me the example? I'll investigate > it. > > Best regards, > > Werner. > > Andreas Jung wrote: >> I am (still) using csstoxslfo 1.0. I want to use named strings to >> put the value of titles within <h1> into the headline. This works so far. >> However when headline does not show the latest title from the latest h1 >> element when there are multiple pages between two h1 tags. Is there a >> workaround to show the values of named strings on every page until the >> value changes the next time? >> >> Andre >> as > > -- > Werner Donné -- Re BVBA > Engelbeekstraat 8 > B-3300 Tienen > tel: (+32) 486 425803 e-mail: wer...@re... > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 > _______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support |
|
From: Brad C. <bk...@mu...> - 2006-03-12 22:30:27
|
Hi, I'm trying to run css2fopnew1_3.jar with fop 0.91 beta. I've copied all the lib .jar files and fop.jar into the same directory as css2fopnew1_3.jar. I get this error: $JAVA_HOME/bin/java -jar css2fopnew1_3.jar ~/temp/packing_slip.xml.htm -ps /tmp/packingslip.ps org/apache/avalon/framework/configuration/ConfigurationException I've also tried building up an explicit .jar list for -cp (just used a mangled fop sh script), I get the same results am I required to have a configuration file? I assume it's fop.xconf.. so I tried this too: $JAVA_HOME/bin/java -jar css2fopnew1_3.jar -fc ../fop-0.91beta/conf/fop.xconf ~/temp/packing_slip.xml.htm -ps /tmp/packingslip.ps org/apache/avalon/framework/configuration/ConfigurationException Same error. How can I get a full traceback to debug this? ---- Unrelated, I'm using css2xslfo1_3.jar in the meantime. I have source xhtml with two tables, both tables specify style="table- layout:fixed;width:100%" and have <col /> elements. But fop complains the same for each table: table-layout="fixed" and width="auto", but auto-layout not supported => assuming width="100%" table-layout="fixed" and width="auto", but auto-layout not supported => assuming width="100%" table-layout="fixed" and width="auto", but auto-layout not supported => assuming width="100%" strange, eh? -- Brad Clements, bk...@mu... (315)268-1000 http://www.murkworks.com AOL-IM or SKYPE: BKClements |
|
From: Andreas J. <li...@an...> - 2006-03-11 09:34:31
|
--On 6. M=C3=A4rz 2006 10:38:52 +0100 Werner Donn=C3=A9 = <wer...@re...> wrote: > Hi Andreas, > > I tried it with version 1.0 as well as 1.3 and the margin is there. > Set it to zero to see the difference. It is not part of the content > rectangle however, which is why the background doesn't reach that far. > If that is what you want you should use padding instead of margin. > > This issue seems to depend very much on the converter. Neither with Xinc=20 nor XFC I can see the top/bottom margin. I investigated the generated FO=20 file. The related fo:block has margin-top|bottom set to 0em but uses=20 space-after|before to specify the margin. Replacing=20 space-after|space-before with margin-bottom|top let the margins work. Is=20 there any reason why you use space-after|before vs. border-bottom|top? What is the recommend way to get around this issue? Andreas |
|
From: Andreas J. <li...@an...> - 2006-03-06 09:39:47
|
Thanks for the hint but neither Xinc nor XFC work with that. Anyway..it was a nice try to satisfy the requirements of my boss :-) Andreas --On 6. M=C3=A4rz 2006 10:17:37 +0100 Werner Donn=C3=A9 = <wer...@re...> wrote: > Hi Andreas, > > This can be done as follows: > > <?xml version=3D"1.0" encoding=3D"UTF-8"?> > <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> > <html xmlns=3D"http://www.w3.org/1999/xhtml"> > <head> > <title></title> > </head> > <body> > <div style=3D"height: 100%"> > <div style=3D"height: 100%"> > <p>A paragraph.</p> > </div> > <p>The end.</p> > </div> > </body> > </html> > > I'm not entirely sure, however, that this is portable. It works fine > with XEP and XSL Formatter, but not with Xinc or FOP, for example. > There was a discussion about a similar case here > http://www.renderx.net/lists/xep-support/4131.html. > > Best regards, > > Werner. > > Andreas Jung wrote: >> We have the usecase where a document contains <div> at the end of the >> text. This <div> should be aligned with the bottom of the last page >> where it appear. So there must be a flexible vertical spacing between >> the last text >> before this <DIV> and the <DIV> itself. Is there a way to accomplish >> that? >> >> Regards, >> Andreas >> >> >> ----------------------- >> | text text text text | >> | text text text text | >> | | >> | | >> | | >> | | >> | ------------------- | >> | DIV goes here | >> ----------------------- >> >> > > -- > Werner Donn=C3=A9 -- Re BVBA > Engelbeekstraat 8 > B-3300 Tienen > tel: (+32) 486 425803 e-mail: wer...@re... > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language that extends applications into web and mobile media. Attend the > live webcast and join the prime developer group breaking into this new > coding territory! > = http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=3D12= 1642 > _______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support |
|
From: <wer...@re...> - 2006-03-06 09:38:46
|
Hi Andreas, I tried it with version 1.0 as well as 1.3 and the margin is there. Set it to zero to see the difference. It is not part of the content rectangle however, which is why the background doesn't reach that far. If that is what you want you should use padding instead of margin. Best regards, Werner. Andreas Jung wrote: > The following code should place "text goes here" inside a grey box > which is seperated from the upper and lower <p> by 2em. However the margin > of 2em is only visible for left and right bottom. The DIV itself is > directly > placed under/over the <p> without additional vertical space. Is this a > bug or a feature? > > Andreas > > > <?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" xml:lang="de" lang="de"> > <head> > <style type="text/css"> > /* This is the main stylesheet for all export actions through XSL-FO. > DON'T TOUCH THIS SCRIPT UNLESS YOU KNOW WHAT YOU ARE REALLY DOING!!!! > */ > > div.outline { > margin: 2em 2em 2em 2em; > background: #eeeeee; > } > > </style> > > <title>Dokument HI1383992</title> > </head> > <body> > > <p>hello world</p> > > <div class="outline"> > text goes here > </div> > <p>hello world</p> > > > </body> > </htm > l> -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: <wer...@re...> - 2006-03-06 09:17:32
|
Hi Andreas, This can be done as follows: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title></title> </head> <body> <div style="height: 100%"> <div style="height: 100%"> <p>A paragraph.</p> </div> <p>The end.</p> </div> </body> </html> I'm not entirely sure, however, that this is portable. It works fine with XEP and XSL Formatter, but not with Xinc or FOP, for example. There was a discussion about a similar case here http://www.renderx.net/lists/xep-support/4131.html. Best regards, Werner. Andreas Jung wrote: > We have the usecase where a document contains <div> at the end of the > text. This <div> should be aligned with the bottom of the last page > where it appear. So there must be a flexible vertical spacing between > the last text > before this <DIV> and the <DIV> itself. Is there a way to accomplish that? > > Regards, > Andreas > > > ----------------------- > | text text text text | > | text text text text | > | | > | | > | | > | | > | ------------------- | > | DIV goes here | > ----------------------- > > -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: Andreas J. <li...@an...> - 2006-03-06 07:54:24
|
We have the usecase where a document contains <div> at the end of the text. = This <div> should be aligned with the bottom of the last page where it=20 appear. So there must be a flexible vertical spacing between the last text before this <DIV> and the <DIV> itself. Is there a way to accomplish that? Regards, Andreas ----------------------- | text text text text | | text text text text | | | | | | | | | | ------------------- | | DIV goes here | ----------------------- |
|
From: Andreas J. <li...@an...> - 2006-03-06 07:34:45
|
The following code should place "text goes here" inside a grey box
which is seperated from the upper and lower <p> by 2em. However the margin
of 2em is only visible for left and right bottom. The DIV itself is =
directly
placed under/over the <p> without additional vertical space. Is this a bug=20
or a feature?
Andreas
<?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" xml:lang=3D"de" lang=3D"de">
<head>
<style type=3D"text/css">
/* This is the main stylesheet for all export actions through XSL-FO.
DON'T TOUCH THIS SCRIPT UNLESS YOU KNOW WHAT YOU ARE REALLY =
DOING!!!!
*/
div.outline {
margin: 2em 2em 2em 2em;
background: #eeeeee;
}
</style>
<title>Dokument HI1383992</title>
</head>
<body>
<p>hello world</p>
<div class=3D"outline">
text goes here
</div>
<p>hello world</p>
</body>
</html> |
|
From: <wer...@re...> - 2006-02-20 09:23:47
|
Hi Andreas, This is supposed to be the default behaviour. The manual also uses this feature. Can you send me the example? I'll investigate it. Best regards, Werner. Andreas Jung wrote: > I am (still) using csstoxslfo 1.0. I want to use named strings to > put the value of titles within <h1> into the headline. This works so far. > However when headline does not show the latest title from the latest h1 > element when there are multiple pages between two h1 tags. Is there a > workaround to show the values of named strings on every page until the > value changes the next time? > > Andre > as -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
|
From: Andreas J. <li...@an...> - 2006-02-19 11:48:39
|
I am (still) using csstoxslfo 1.0. I want to use named strings to put the value of titles within <h1> into the headline. This works so far. However when headline does not show the latest title from the latest h1=20 element when there are multiple pages between two h1 tags. Is there a=20 workaround to show the values of named strings on every page until the=20 value changes the next time? Andreas |
|
From: <wer...@re...> - 2006-02-17 17:15:55
|
Hi Andreas, You can use a right floating box for that and set the clear property of the surrounding paragraphs to "rigth" as well. I've attached an example. Best regards, Werner. Andreas Jung wrote: > I have a case where a box containing text should be positioned on the > right side e.g. like that: > > > > > header header header header header > ---------------------------------------------------- > > |---------class="foo"-----------| > | Box goes here werewjlkrjewlrj| > |-------------------------------| > > > more text more text more text more text more text more > text more text more text more text more text more text > more text more text more text > > How should the definition for class="foo" look like > in this case`? > > 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...> - 2006-02-17 16:58:23
|
I have a case where a box containing text should be positioned on the right =
side e.g. like that:
header header header header header
----------------------------------------------------
|---------class=3D"foo"-----------|
| Box goes here werewjlkrjewlrj|
|-------------------------------|
more text more text more text more text more text more
text more text more text more text more text more text
more text more text more text
How should the definition for class=3D"foo" look like
in this case`?
Thanks,
Andreas |
|
From: <wer...@re...> - 2005-12-07 15:05:32
|
Hi Andreas, You should use the "region" attribute, because it doesn't exist in HTML. Instead you should specify the region property for the elements. In this case you can replace for example region="top" with style="region: top" This is a small CSS fragment on the element. You should also set the body region on the "body" element. You can ommit this, because it is already done in the User Agent style sheet. Best regards, Werner. Andreas Jung wrote: > Hi, > > I tried the following HTML to figure out how page regions work with the > V 1.2 however I can not see the text appearing within the regions after > converting the FO file to PDF using Xinc. Is there something I am missing? > > Thanks, > Andreas > > > ---- > > <?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" xml:lang="de" lang="de"> > <body> > <div region="top"> > top > </div> > > <div region="left"> > left > </div> > > <div region="right"> > left > </div> > > > <div region="bottom"> > bottom > </div> > > <div region="body"> > <h1>§ 19 Automatisierte Einzelentscheidungen</h1> > <p>Entscheidungen, die zu einer tatsächlichen oder rechtlichen > Satz 1 für Entscheidungen verwendet werden, wenn</p> > </div> > > </body> > </html >> -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
