css2xslfo-support Mailing List for CSSToXSLFO (Page 7)
Brought to you by:
wdonne
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-12-07 14:37:59
|
Hi, I tried the following HTML to figure out how page regions work with the V=20 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=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"> <body> <div region=3D"top"> top </div> <div region=3D"left"> left </div> <div region=3D"right"> left </div> <div region=3D"bottom"> bottom </div> <div region=3D"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> |
From: Peng Z. <pen...@hi...> - 2005-10-31 16:02:35
|
From: <wer...@re...> - 2005-08-07 18:51:16
|
Hi Sergey, I'm sorry to disappoint you, but it is not possible to suppress that behaviour. It is the result of the way page inheritance is implemented for the static regions. Less specific ones are copied to more specific ones if the latter are not defined in the document. For example, "left" and "right" inherit from the anonymous page. If there is no definition for the left and right page regions, those from the anonymous page are copied instead. This greatly simplies the XSLT part which is the last element in the internal XMLFilter chain and which is also a bottle neck. Best regards, Werner. Ushakov, Sergey N wrote: > Hi Werner, >=20 > I'm now evaluating and troubleshooting a new fo-2-pdf formatter from > Altsoft, and for this reason would prefer to minimize the number of > different page layouts. >=20 > Unfortunately I can't get rid of two-sided layout with different even/o= dd > page-masters. >=20 > Is there any way to suppress splitting into even/odd when @page is in > effect? >=20 > My best regards, > Sergey Ushakov >=20 >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dcl= ick > _______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support >=20 >=20 --=20 Werner Donn=C3=A9 -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
From: <wer...@re...> - 2005-08-07 18:40:09
|
Hi Andreas, As far as I can see the following is generated for <br/>: <fo:inline margin-left=3D"0pt" margin-right=3D"0pt"> <fo:block/> </fo:inline> I think the space-after comes from a margin-bottom in the style sheet. Do you have a rule like "* { margin-bottom: 0.5em; }" somewhere? Best regards, Werner. Andreas Jung wrote: > Wolfgang, >=20 > we have some preformatted text that need to be translated to PDF (using= =20 > Xinc). <pre>...text..</pre> is translated to <fo:block white-space=3D"p= re">. > However Xinc does not recognize the white-space attribute. As workaroun= d=20 > I generate >=20 > <div > line1<br/> > line2<br/> > ..</div> >=20 > This works fine except csstoxslfo generates <fo:block=20 > space-after=3D"0.5em"...> which produces large gaps between all lines. > So I added >=20 > br { > space-after: 0; > } >=20 > to my stylesheet but I the value for space-after remains unchanged in=20 > the generated FO file. >=20 > Any ideas why? >=20 > Andreas >=20 >=20 > ------------------------------------------------------- > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies > from IBM. Find simple to follow Roadmaps, straightforward articles, > informative Webcasts and more! Get everything you need to get up to > speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dcl= ick > _______________________________________________ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support >=20 >=20 --=20 Werner Donn=E9 -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
From: Ushakov, S. N <us...@in...> - 2005-08-03 04:29:27
|
Hi Werner, I'm now evaluating and troubleshooting a new fo-2-pdf formatter from Altsoft, and for this reason would prefer to minimize the number of different page layouts. Unfortunately I can't get rid of two-sided layout with different even/odd page-masters. Is there any way to suppress splitting into even/odd when @page is in effect? My best regards, Sergey Ushakov |
From: Andreas J. <and...@ha...> - 2005-08-02 08:13:04
|
Wolfgang, we have some preformatted text that need to be translated to PDF (using Xinc). <pre>...text..</pre> is translated to <fo:block white-space="pre">. However Xinc does not recognize the white-space attribute. As workaround I generate <div line1<br/> line2<br/> ..</div> This works fine except csstoxslfo generates <fo:block space-after="0.5em"...> which produces large gaps between all lines. So I added br { space-after: 0; } to my stylesheet but I the value for space-after remains unchanged in the generated FO file. Any ideas why? Andreas |
From: <wer...@re...> - 2005-06-23 07:54:07
|
Hi Min, You should put a "div" in the beginning of the document with the "region" property set to "bottom" and the "height" property to a value of your choice. Within the "div" you can put a "span", for example, for which you specify a span:before rule. In it, you use the "content" property with "counter(page)" as its value. Setting up static regions like that will only work if you also override the page definition with an @page rule. An example can be found at http://www.re.be/css2xslfo/1_0rc2/manual.html. Best regards, Werner. Min Li wrote: > Hi, Mr. Matthias Wessendorf, > > I'm using css2xslfo library to convert xhtml to fo then to pdf using > fop. I'm having trouble finding out the mapping between xhtml and fo to > get a footer at the bottom of a page. right now, the css.xsl defines a > default footer "page number" to the "xsl-region-after" part. If I want > to define my own footer, what tags should I use in xhtml file so that in > fo, my self-defined footer will fall into xsl-region-after automatically. > > Thanks in advance for your prompt reply. > > > Min > > ------------------------------------------------------------------------ > Yahoo! Sports > Rekindle the Rivalries. Sign up for Fantasy Football > <http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=33539/*http://football.fantasysports.yahoo.com?ovchn=YAH&ovcpn=Integration&ovcrn=Mail+footer&ovrfd=YAH&ovtac=AD > > -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
From: Min Li <mi...@ya...> - 2005-06-22 21:29:05
|
Hi, Mr. Matthias Wessendorf, I'm using css2xslfo library to convert xhtml to fo then to pdf using fop. I'm having trouble finding out the mapping between xhtml and fo to get a footer at the bottom of a page. right now, the css.xsl defines a default footer "page number" to the "xsl-region-after" part. If I want to define my own footer, what tags should I use in xhtml file so that in fo, my self-defined footer will fall into xsl-region-after automatically. Thanks in advance for your prompt reply. Min --------------------------------- Yahoo! Sports Rekindle the Rivalries. Sign up for Fantasy Football |
From: <wer...@re...> - 2005-06-06 08:17:34
|
Andreas, This seems to depend on the parser. When I use the one in JDK1.5.0 the entity reference is translated into a control character. With Xerces 2.6.2 and Crimson it is not. I think it is a bug in the XML parses that has something to with the fact that we are dealing with a control character here. Regards, Werner. Andreas Jung wrote: > > > --On 6. Juni 2005 09:33:46 +0200 Werner Donné <wer...@re...> wrote: > >> Hi Andreas, >> >> The XML parser is supposed to resolve those entity references, so >> CSSToXSLFO >> shouldn't even see them. It uses an Xerces parser. Even if they would end >> up >> in the FO file, the parser of the XSL-FO processor would have to resolve >> them. >> Can you send me an example? >> > > > > <!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> > </title> > </head> > <body> > hello › world > </body> > </html> > > > > becomes > > <?xml version="1.0" encoding="UTF-8"?> > <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format" language="en" > hyphenate="true" font-size="11pt" font-family="serif" > country="de"><fo:layout-master-set><fo:simple-page-master > margin-right="25mm" margin-left="25mm" margin-bottom="10mm" > margin-top="10mm" page-width="210mm" page-height="297mm" > writing-mode="lr-tb" master-name="blank"><fo:region-body > margin-right="0mm" margin-left="0mm" margin-bottom="0mm" > margin-top="0mm"/></fo:simple-page-master><fo:simple-page-master > margin-right="25mm + 10mm" margin-left="25mm - 10mm" > margin-bottom="10mm" margin-top="10mm" page-width="210mm" > page-height="297mm" writing-mode="lr-tb" > master-name="even"><fo:region-body margin-top="15mm" margin-right="0mm" > margin-left="0mm" margin-bottom="15mm" > column-count="1"/><fo:region-before region-name="region-before-even" > extent="10mm" display-align="after"/><fo:region-after extent="10mm" > display-align="before"/></fo:simple-page-master><fo:simple-page-master > margin-right="25mm - 10mm" margin-left="25mm + 10mm" > margin-bottom="10mm" margin-top="10mm" page-width="210mm" > page-height="297mm" writing-mode="lr-tb" > master-name="odd"><fo:region-body margin-top="15mm" margin-right="0mm" > margin-left="0mm" margin-bottom="15mm" > column-count="1"/><fo:region-before region-name="region-before-odd" > extent="10mm" display-align="after"/><fo:region-after extent="10mm" > display-align="before"/></fo:simple-page-master><fo:simple-page-master > margin-right="25mm - 10mm" margin-left="25mm + 10mm" > margin-bottom="10mm" margin-top="10mm" page-width="210mm" > page-height="297mm" writing-mode="lr-tb" > master-name="odd-first"><fo:region-body margin-top="15mm" > margin-right="0mm" margin-left="0mm" margin-bottom="15mm" > column-count="1"/><fo:region-after extent="10mm" > display-align="before"/></fo:simple-page-master><fo:simple-page-master > margin-right="25mm" margin-left="25mm" margin-bottom="10mm" > margin-top="10mm" page-width="210mm" page-height="297mm" > writing-mode="lr-tb" master-name="onesided"><fo:region-body > margin-top="15mm" margin-right="0mm" margin-left="0mm" > margin-bottom="15mm" column-count="1"/><fo:region-before > region-name="region-before-even" extent="10mm" > display-align="after"/><fo:region-after extent="10mm" > display-align="before"/></fo:simple-page-master><fo:simple-page-master > margin-right="25mm" margin-left="25mm" margin-bottom="10mm" > margin-top="10mm" page-width="210mm" page-height="297mm" > writing-mode="lr-tb" master-name="onesided-first"><fo:region-body > margin-top="15mm" margin-right="0mm" margin-left="0mm" > margin-bottom="15mm" column-count="1"/><fo:region-after extent="10mm" > display-align="before"/></fo:simple-page-master><fo:simple-page-master > margin-bottom="10mm" margin-top="10mm" page-width="210mm" > page-height="297mm" writing-mode="lr-tb" master-name="title" > margin-left="25mm" margin-right="25mm"><fo:region-body > margin-right="0mm" margin-left="0mm" margin-bottom="0mm" > margin-top="0mm"/></fo:simple-page-master><fo:page-sequence-master > master-name="document"><fo:repeatable-page-master-alternatives><fo:conditional-page-master-reference > master-reference="onesided-first" > page-position="first"/><fo:conditional-page-master-reference > master-reference="onesided" > page-position="any"/><fo:conditional-page-master-reference > master-reference="blank" page-position="any" > blank-or-not-blank="blank"/></fo:repeatable-page-master-alternatives></fo:page-sequence-master></fo:layout-master-set><fo:page-sequence > master-reference="document" initial-page-number="1" > format="1"><fo:static-content flow-name="region-before-even"><fo:block > xmlns:xh="http://www.w3.org/1999/xhtml" > xmlns:css="http://www.w3.org/1998/CSS" text-transform="uppercase" > text-align="start" font-style="oblique"><fo:retrieve-marker > retrieve-boundary="document" > retrieve-position="first-starting-within-page" > retrieve-class-name="component"/></fo:block></fo:static-content><fo:static-content > flow-name="region-before-odd"><fo:block > xmlns:xh="http://www.w3.org/1999/xhtml" > xmlns:css="http://www.w3.org/1998/CSS" text-transform="uppercase" > text-align="end" font-style="oblique"><fo:retrieve-marker > retrieve-boundary="document" > retrieve-position="first-starting-within-page" > retrieve-class-name="component"/></fo:block></fo:static-content><fo:static-content > flow-name="xsl-footnote-separator"><fo:block > xmlns:xh="http://www.w3.org/1999/xhtml" > xmlns:css="http://www.w3.org/1998/CSS"><fo:leader rule-thickness="0.2pt" > rule-style="solid" leader-pattern="rule" > leader-length="41%"/></fo:block></fo:static-content><fo:static-content > flow-name="xsl-region-after"><fo:block > xmlns:xh="http://www.w3.org/1999/xhtml" > xmlns:css="http://www.w3.org/1998/CSS" > text-align="center"><fo:page-number/></fo:block></fo:static-content><fo:flow > flow-name="xsl-region-body"><fo:block> > > <fo:block xmlns:xh="http://www.w3.org/1999/xhtml" > xmlns:css="http://www.w3.org/1998/CSS" margin-right="0pt" > margin-left="0pt" font-family="serif" line-height="1.33" > padding-bottom="0" padding-left="0" padding-right="0" padding-top="0" > unicode-bidi="embed"> > hello › world > </fo:block> > </fo:block></fo:flow></fo:page-sequence></fo:root > > -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
From: Andreas J. <li...@an...> - 2005-06-06 07:57:20
|
--On 6. Juni 2005 09:33:46 +0200 Werner Donn=C3=A9 <wer...@re...> = wrote: > Hi Andreas, > > The XML parser is supposed to resolve those entity references, so > CSSToXSLFO > shouldn't even see them. It uses an Xerces parser. Even if they would end > up > in the FO file, the parser of the XSL-FO processor would have to resolve > them. > Can you send me an example? > <!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> </title> </head> <body> hello › world </body> </html> becomes <?xml version=3D"1.0" encoding=3D"UTF-8"?> <fo:root xmlns:fo=3D"http://www.w3.org/1999/XSL/Format" language=3D"en"=20 hyphenate=3D"true" font-size=3D"11pt" font-family=3D"serif"=20 country=3D"de"><fo:layout-master-set><fo:simple-page-master=20 margin-right=3D"25mm" margin-left=3D"25mm" margin-bottom=3D"10mm"=20 margin-top=3D"10mm" page-width=3D"210mm" page-height=3D"297mm"=20 writing-mode=3D"lr-tb" master-name=3D"blank"><fo:region-body = margin-right=3D"0mm"=20 margin-left=3D"0mm" margin-bottom=3D"0mm"=20 margin-top=3D"0mm"/></fo:simple-page-master><fo:simple-page-master=20 margin-right=3D"25mm + 10mm" margin-left=3D"25mm - 10mm" = margin-bottom=3D"10mm"=20 margin-top=3D"10mm" page-width=3D"210mm" page-height=3D"297mm"=20 writing-mode=3D"lr-tb" master-name=3D"even"><fo:region-body = margin-top=3D"15mm"=20 margin-right=3D"0mm" margin-left=3D"0mm" margin-bottom=3D"15mm"=20 column-count=3D"1"/><fo:region-before region-name=3D"region-before-even"=20 extent=3D"10mm" display-align=3D"after"/><fo:region-after extent=3D"10mm"=20 display-align=3D"before"/></fo:simple-page-master><fo:simple-page-master=20 margin-right=3D"25mm - 10mm" margin-left=3D"25mm + 10mm" = margin-bottom=3D"10mm"=20 margin-top=3D"10mm" page-width=3D"210mm" page-height=3D"297mm"=20 writing-mode=3D"lr-tb" master-name=3D"odd"><fo:region-body = margin-top=3D"15mm"=20 margin-right=3D"0mm" margin-left=3D"0mm" margin-bottom=3D"15mm"=20 column-count=3D"1"/><fo:region-before region-name=3D"region-before-odd"=20 extent=3D"10mm" display-align=3D"after"/><fo:region-after extent=3D"10mm"=20 display-align=3D"before"/></fo:simple-page-master><fo:simple-page-master=20 margin-right=3D"25mm - 10mm" margin-left=3D"25mm + 10mm" = margin-bottom=3D"10mm"=20 margin-top=3D"10mm" page-width=3D"210mm" page-height=3D"297mm"=20 writing-mode=3D"lr-tb" master-name=3D"odd-first"><fo:region-body=20 margin-top=3D"15mm" margin-right=3D"0mm" margin-left=3D"0mm" = margin-bottom=3D"15mm"=20 column-count=3D"1"/><fo:region-after extent=3D"10mm"=20 display-align=3D"before"/></fo:simple-page-master><fo:simple-page-master=20 margin-right=3D"25mm" margin-left=3D"25mm" margin-bottom=3D"10mm"=20 margin-top=3D"10mm" page-width=3D"210mm" page-height=3D"297mm"=20 writing-mode=3D"lr-tb" master-name=3D"onesided"><fo:region-body=20 margin-top=3D"15mm" margin-right=3D"0mm" margin-left=3D"0mm" = margin-bottom=3D"15mm"=20 column-count=3D"1"/><fo:region-before region-name=3D"region-before-even"=20 extent=3D"10mm" display-align=3D"after"/><fo:region-after extent=3D"10mm"=20 display-align=3D"before"/></fo:simple-page-master><fo:simple-page-master=20 margin-right=3D"25mm" margin-left=3D"25mm" margin-bottom=3D"10mm"=20 margin-top=3D"10mm" page-width=3D"210mm" page-height=3D"297mm"=20 writing-mode=3D"lr-tb" master-name=3D"onesided-first"><fo:region-body=20 margin-top=3D"15mm" margin-right=3D"0mm" margin-left=3D"0mm" = margin-bottom=3D"15mm"=20 column-count=3D"1"/><fo:region-after extent=3D"10mm"=20 display-align=3D"before"/></fo:simple-page-master><fo:simple-page-master=20 margin-bottom=3D"10mm" margin-top=3D"10mm" page-width=3D"210mm"=20 page-height=3D"297mm" writing-mode=3D"lr-tb" master-name=3D"title"=20 margin-left=3D"25mm" margin-right=3D"25mm"><fo:region-body = margin-right=3D"0mm"=20 margin-left=3D"0mm" margin-bottom=3D"0mm"=20 margin-top=3D"0mm"/></fo:simple-page-master><fo:page-sequence-master=20 master-name=3D"document"><fo:repeatable-page-master-alternatives><fo:conditi= onal-page-master-reference=20 master-reference=3D"onesided-first"=20 page-position=3D"first"/><fo:conditional-page-master-reference=20 master-reference=3D"onesided"=20 page-position=3D"any"/><fo:conditional-page-master-reference=20 master-reference=3D"blank" page-position=3D"any"=20 blank-or-not-blank=3D"blank"/></fo:repeatable-page-master-alternatives></fo:= page-sequence-master></fo:layout-master-set><fo:page-sequence=20 master-reference=3D"document" initial-page-number=3D"1"=20 format=3D"1"><fo:static-content flow-name=3D"region-before-even"><fo:block=20 xmlns:xh=3D"http://www.w3.org/1999/xhtml"=20 xmlns:css=3D"http://www.w3.org/1998/CSS" text-transform=3D"uppercase"=20 text-align=3D"start" font-style=3D"oblique"><fo:retrieve-marker=20 retrieve-boundary=3D"document" = retrieve-position=3D"first-starting-within-page"=20 retrieve-class-name=3D"component"/></fo:block></fo:static-content><fo:static= -content=20 flow-name=3D"region-before-odd"><fo:block=20 xmlns:xh=3D"http://www.w3.org/1999/xhtml"=20 xmlns:css=3D"http://www.w3.org/1998/CSS" text-transform=3D"uppercase"=20 text-align=3D"end" font-style=3D"oblique"><fo:retrieve-marker=20 retrieve-boundary=3D"document" = retrieve-position=3D"first-starting-within-page"=20 retrieve-class-name=3D"component"/></fo:block></fo:static-content><fo:static= -content=20 flow-name=3D"xsl-footnote-separator"><fo:block=20 xmlns:xh=3D"http://www.w3.org/1999/xhtml"=20 xmlns:css=3D"http://www.w3.org/1998/CSS"><fo:leader = rule-thickness=3D"0.2pt"=20 rule-style=3D"solid" leader-pattern=3D"rule"=20 leader-length=3D"41%"/></fo:block></fo:static-content><fo:static-content=20 flow-name=3D"xsl-region-after"><fo:block=20 xmlns:xh=3D"http://www.w3.org/1999/xhtml"=20 xmlns:css=3D"http://www.w3.org/1998/CSS"=20 text-align=3D"center"><fo:page-number/></fo:block></fo:static-content><fo:fl= ow=20 flow-name=3D"xsl-region-body"><fo:block> <fo:block xmlns:xh=3D"http://www.w3.org/1999/xhtml"=20 xmlns:css=3D"http://www.w3.org/1998/CSS" margin-right=3D"0pt" = margin-left=3D"0pt"=20 font-family=3D"serif" line-height=3D"1.33" padding-bottom=3D"0" = padding-left=3D"0"=20 padding-right=3D"0" padding-top=3D"0" unicode-bidi=3D"embed"> hello › world </fo:block> </fo:block></fo:flow></fo:page-sequence></fo:root |
From: <wer...@re...> - 2005-06-06 07:34:41
|
Hi Andreas, The XML parser is supposed to resolve those entity references, so CSSToXSLFO shouldn't even see them. It uses an Xerces parser. Even if they would end up in the FO file, the parser of the XSL-FO processor would have to resolve them. Can you send me an example? Best regards, Werner. Andreas Jung wrote: > Hello Werner, > > I have some HTML documents containing › entities. They appear > untranslated in the FO file although other HTML files with other numeric > enties are translated into the corresponding UTF-8 code...is this a bug? > > 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-06-05 08:29:45
|
Hello Werner, I have some HTML documents containing › entities. They appear=20 untranslated in the FO file although other HTML files with other numeric=20 enties are translated into the corresponding UTF-8 code...is this a bug? Andreas |
From: <wer...@re...> - 2005-06-03 09:46:50
|
Hi Matthias, When I save the document I see that indeed it is not wellformed. The link element, for example, is not closed. "View Page Source" in Mozilla shows it is closed, but physically it isn't. There is another problem in that the XHTML namespace is not declared, which is required for XHTML documents. If you run it through tidy you will obtain a valid document. Best regards, Werner. Matthias Wessendorf wrote: > hi me again ;) > > I have noticed that exception on *parsing* that link: > http://www.w3schools.com/xhtml/xhtml_reference.asp > > the html validator of firefox (using Tidy) tell me, page is valid > > no error or warning. > > here it goes. (Game.main() is my test class ;)) > > > > > be.re.css.CSSToXSLFOException: The element type "link" must be terminated by the matching end-tag "</link>". > at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:142) > at be.re.css.CSSToXSLFO.main(CSSToXSLFO.java:277) > at pb.Game.main(Game.java:40) > Caused by: > org.xml.sax.SAXParseException: The element type "link" must be terminated by the matching end-tag "</link>". > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at be.re.xml.sax.ProtectEntityResolverFilter.parse(ProtectEntityResolverFilter.java:42) > at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371) > at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371) > at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371) > at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371) > at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371) > at org.apache.xalan.transformer.TrAXFilter.parse(TrAXFilter.java:134) > at be.re.css.CSSToXSLFOFilter.parse(CSSToXSLFOFilter.java:237) > at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:137) > at be.re.css.CSSToXSLFO.main(CSSToXSLFO.java:277) > at pb.Game.main(Game.java:40) > > > ------------------------------------------------------- > This SF.Net email is sponsored by Yahoo. > Introducing Yahoo! Search Developer Network - Create apps using Yahoo! > Search APIs Find out how you can build Yahoo! directly into your own > Applications - visit http://developer.yahoo.net/?fr_______________________________________________ > 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-06-03 09:25:42
|
hi me again ;) I have noticed that exception on *parsing* that link: http://www.w3schools.com/xhtml/xhtml_reference.asp the html validator of firefox (using Tidy) tell me, page is valid no error or warning. here it goes. (Game.main() is my test class ;)) be.re.css.CSSToXSLFOException: The element type "link" must be = terminated by the matching end-tag "</link>". at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:142) at be.re.css.CSSToXSLFO.main(CSSToXSLFO.java:277) at pb.Game.main(Game.java:40) Caused by: org.xml.sax.SAXParseException: The element type "link" must be = terminated by the matching end-tag "</link>". at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at = be.re.xml.sax.ProtectEntityResolverFilter.parse(ProtectEntityResolverFilt= er.java:42) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371) at org.xml.sax.helpers.XMLFilterImpl.parse(XMLFilterImpl.java:371) at org.apache.xalan.transformer.TrAXFilter.parse(TrAXFilter.java:134) at be.re.css.CSSToXSLFOFilter.parse(CSSToXSLFOFilter.java:237) at be.re.css.CSSToXSLFO.convert(CSSToXSLFO.java:137) at be.re.css.CSSToXSLFO.main(CSSToXSLFO.java:277) at pb.Game.main(Game.java:40) |
From: <wer...@re...> - 2005-06-02 15:39:27
|
Hi Matthias, You could edit the fop_filter.xsl file, which is placed between the XSL-FO generator and FOP in css2fop. You can also run css2xslfo instead of css2fop and launch an XSLT processor with a post-processing style sheet. In the coming version the fop_filter.xsl will be extended to cover more cases, especially for tables. The line-height and font-size properties can also be added in your CSS style sheet. Calculating column widths is a way to compensate for not having automatic table layout, but it can only be an approximation, because you have no access to font metrics, etc. I would translated the calculation in proportional widths for the columns. That works with FOP. Such calculations would have to be done in Java. Adding something to CSSToXSLFO is an option, but an unsafe one with respect to upgrades. You can also do it on the XSL-FO document in a Java XML filter. You can then create a new wrapper, with a main method, that has an XMLFilter chain of two entries: be.re.css.CSSToXSLFOFilter first and your filter second. Best regards, Werner. Matthias Wessendorf wrote: > Werner, > > I saw that html2fo (C based) is able to generate a FO that works fine > with FOP. their tables need to <colgroup> etc. > > They are calculating the width and also each <fo:block/> has > those attributes. > > <fo:block line-height="12pt" font-size="10pt" space-before.optimum="1.5pt" space-after.optimum="1.5pt" keep-together="always"> > > keep-allways allows the text to be rendered inside a column of that table. > > Can you tell me the java file, where I could add something like that ? > ` > Or do you know a *patch* for stuff like that? > > Thanks, > Matthias > > >>-----Original Message----- >>From: Werner Donné [mailto:wer...@re...] >>Sent: Thursday, June 02, 2005 11:04 AM >>To: Matthias Wessendorf >>Cc: css...@li... >>Subject: Re: [css2xslfo-support] [FOP] workarounds for xhtml table ? >> >> >>Hi Matthias, >> >>You should add a "col" element to your table with the "width" >>attribute set to something. In this case the value I propose >>is "1*", which indicates the column will occupy the complete >>table. >> >>Regards, >> >>Werner. >> >>Matthias Wessendorf wrote: >> >>>Hi, >>> >>>I come back to css2xslfo. I have currently the problem, >> >>that I need to generate a PDF that >> >>>contains a xhtml table. >>> >>>my xhtml is >>> >>><?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>Foo</title> >>><style type="text/css"> >>> >>>body, h1, h2, h3, p, div, ol, li, table, thead, tbody, th, tr, td { >>> hyphenate: false; >>>} >>> >>> >>></style> >>></head> >>><body> >>> >>><table> >>> <thead> >>> <tr> >>> <th>User</th> >>> </tr> >>> </thead> >>> <tbody> >>> <tr> >>> <td> >>> MW >>> </td> >>> </tr> >>> </tbody> >>></table> >>> >>></body> >>></html> >>> >>> >>> >>> >>> >>> >>> >>>I guess it is valid. But the FOP tells me: >>> >>>[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] >>>[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 >>> >>> >>>and the PDF is blank, no table there :-( >>> >>>Does anybody know a workaround to output that table using FOP ? >>> >>>Thanks, >>>Matthias >>> >>> >>> >>>------------------------------------------------------- >>>This SF.Net email is sponsored by Yahoo. >>>Introducing Yahoo! Search Developer Network - Create apps >> >>using Yahoo! >> >>>Search APIs Find out how you can build Yahoo! directly into your own >>>Applications - visit > > http://developer.yahoo.net/?fr_______________________________________________ > >>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-06-02 15:16:45
|
Werner,=20 I saw that html2fo (C based) is able to generate a FO that works fine with FOP. their tables need to <colgroup> etc. They are calculating the width and also each <fo:block/> has those attributes. <fo:block line-height=3D"12pt" font-size=3D"10pt" = space-before.optimum=3D"1.5pt" space-after.optimum=3D"1.5pt" = keep-together=3D"always"> keep-allways allows the text to be rendered inside a column of that = table. Can you tell me the java file, where I could add something like that ? ` Or do you know a *patch* for stuff like that? Thanks, Matthias > -----Original Message----- > From: Werner Donn=E9 [mailto:wer...@re...] > Sent: Thursday, June 02, 2005 11:04 AM > To: Matthias Wessendorf > Cc: css...@li... > Subject: Re: [css2xslfo-support] [FOP] workarounds for xhtml table ? >=20 >=20 > Hi Matthias, >=20 > You should add a "col" element to your table with the "width" > attribute set to something. In this case the value I propose > is "1*", which indicates the column will occupy the complete > table. >=20 > Regards, >=20 > Werner. >=20 > Matthias Wessendorf wrote: > > Hi, > >=20 > > I come back to css2xslfo. I have currently the problem,=20 > that I need to generate a PDF that=20 > > contains a xhtml table. > >=20 > > my xhtml is > >=20 > > <?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>Foo</title> > > <style type=3D"text/css"> > >=20 > > body, h1, h2, h3, p, div, ol, li, table, thead, tbody, th, tr, td { > > hyphenate: false; > > } > >=20 > >=20 > > </style> > > </head> > > <body> > > =20 > > <table> > > <thead> > > <tr> > > <th>User</th> > > </tr> > > </thead> > > <tbody> > > <tr> > > <td> > > MW > > </td> > > </tr> > > </tbody> > > </table> > >=20 > > </body> > > </html> > >=20 > >=20 > >=20 > >=20 > >=20 > >=20 > >=20 > > I guess it is valid. But the FOP tells me: > >=20 > > [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] > > [WARNING] table-layout=3Dauto is not supported, using fixed! > > [WARNING] current implementation of tables requires a=20 > table-column for each column, indicating column-width > > [INFO] Parsing of document complete, stopping renderer > >=20 > >=20 > > and the PDF is blank, no table there :-( > >=20 > > Does anybody know a workaround to output that table using FOP ? > >=20 > > Thanks, > > Matthias > >=20 > >=20 > >=20 > > ------------------------------------------------------- > > This SF.Net email is sponsored by Yahoo. > > Introducing Yahoo! Search Developer Network - Create apps=20 > using Yahoo! > > Search APIs Find out how you can build Yahoo! directly into your own > > Applications - visit=20 http://developer.yahoo.net/?fr___________________________________________= ____ > css2xslfo-support mailing list > css...@li... > https://lists.sourceforge.net/lists/listinfo/css2xslfo-support >=20 >=20 --=20 Werner Donn=E9 -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |
From: Matthias W. <mwe...@pi...> - 2005-06-02 09:38:28
|
Werner, Andreas, thanks that works for now... but it causes also some errors ;) ok, thanks first. > -----Original Message----- > From: css...@li... > [mailto:css...@li...]On Behalf Of > Andreas Jung > Sent: Thursday, June 02, 2005 11:08 AM > To: Matthias Wessendorf; css...@li... > Subject: Re: [css2xslfo-support] [FOP] workarounds for xhtml table ? >=20 >=20 >=20 >=20 > --On 2. Juni 2005 10:51:47 +0200 Matthias Wessendorf=20 > <mwe...@pi...> wrote: >=20 > > Hi, > > > > I come back to css2xslfo. I have currently the problem,=20 > that I need to > > generate a PDF that contains a xhtml table. > > > > >=20 > I think the workaround is to have a colgroup within the table=20 > with *fixed* > width since FOP can not handle automatic layout for tables.=20 > That's why I=20 > switched to Xinc over FOP...it sucks too much (for my purposes). >=20 > -aj >=20 |
From: Andreas J. <an...@an...> - 2005-06-02 09:07:54
|
--On 2. Juni 2005 10:51:47 +0200 Matthias Wessendorf=20 <mwe...@pi...> wrote: > Hi, > > I come back to css2xslfo. I have currently the problem, that I need to > generate a PDF that contains a xhtml table. > > I think the workaround is to have a colgroup within the table with *fixed* width since FOP can not handle automatic layout for tables. That's why I=20 switched to Xinc over FOP...it sucks too much (for my purposes). -aj |
From: <wer...@re...> - 2005-06-02 09:03:59
|
Hi Matthias, You should add a "col" element to your table with the "width" attribute set to something. In this case the value I propose is "1*", which indicates the column will occupy the complete table. Regards, Werner. Matthias Wessendorf wrote: > Hi, > > I come back to css2xslfo. I have currently the problem, that I need to generate a PDF that > contains a xhtml table. > > my xhtml is > > <?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>Foo</title> > <style type="text/css"> > > body, h1, h2, h3, p, div, ol, li, table, thead, tbody, th, tr, td { > hyphenate: false; > } > > > </style> > </head> > <body> > > <table> > <thead> > <tr> > <th>User</th> > </tr> > </thead> > <tbody> > <tr> > <td> > MW > </td> > </tr> > </tbody> > </table> > > </body> > </html> > > > > > > > > I guess it is valid. But the FOP tells me: > > [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] > [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 > > > and the PDF is blank, no table there :-( > > Does anybody know a workaround to output that table using FOP ? > > Thanks, > Matthias > > > > ------------------------------------------------------- > This SF.Net email is sponsored by Yahoo. > Introducing Yahoo! Search Developer Network - Create apps using Yahoo! > Search APIs Find out how you can build Yahoo! directly into your own > Applications - visit http://developer.yahoo.net/?fr_______________________________________________ > 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-06-02 08:51:56
|
Hi, I come back to css2xslfo. I have currently the problem, that I need to = generate a PDF that=20 contains a xhtml table. my xhtml is <?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>Foo</title> <style type=3D"text/css"> body, h1, h2, h3, p, div, ol, li, table, thead, tbody, th, tr, td { hyphenate: false; } </style> </head> <body> =20 <table> <thead> <tr> <th>User</th> </tr> </thead> <tbody> <tr> <td> MW </td> </tr> </tbody> </table> </body> </html> I guess it is valid. But the FOP tells me: [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] [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 and the PDF is blank, no table there :-( Does anybody know a workaround to output that table using FOP ? Thanks, Matthias |
From: Andreas J. <li...@an...> - 2005-05-25 08:11:09
|
You're right. I have overseen that my HTML page is first processed through tidy before it goes into the csstoxslfo converter. Without tidy I can see the referenced to the markers as well but I could not figure out why it=20 behaves different. Andreas --On Mittwoch, 25. Mai 2005 9:46 Uhr +0200 Werner Donn=E9=20 <wer...@re...> wrote: > Andreas, > > I did that with css2fop1_0rc2.jar. I keep it in my FOP 0.25.5 > distribution, > because it is the last version that was released, so I can run samples > from > the users. I run it as follows: > > java -jar /var/local/fop-0.20.5/lib/css2fop1_0rc2.jar t.html -pdf t.pdf. > > I have attached the XSL-FO file produced when running: > > java -jar /var/local/bin/css2xslfo1_0rc2.jar t.html -fo t.fo > > The output of my "java -version" is: > > java version "1.4.2_01" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) > Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) > > Regards, > > Werner. > > Andreas Jung wrote: >> >> >> >> --On Dienstag, 24. Mai 2005 17:36 Uhr +0200 Werner Donn=E9 >> <wer...@re...> wrote: >> >>> Andreas, >>> >>> For me it does appear, but right after the other text. All I did >>> was declaring the XHTML namespace. See attachment. >>> >> >> When I look at the generated FO then I see the "Hello World" text = sitting >> between <fo:marker marker-class-name=3D"mark"> but I don't see any >> reference to this marker everywhere else in the file...could it be that >> this is a bug in v1.0b2 and you might be using a newer version? >> >> Andreas >> >> > > -- > Werner Donn=E9 -- Re BVBA > Engelbeekstraat 8 > B-3300 Tienen > tel: (+32) 486 425803 e-mail: wer...@re... |
From: <wer...@re...> - 2005-05-25 07:46:21
|
Andreas, I did that with css2fop1_0rc2.jar. I keep it in my FOP 0.25.5 distribution, because it is the last version that was released, so I can run samples from the users. I run it as follows: java -jar /var/local/fop-0.20.5/lib/css2fop1_0rc2.jar t.html -pdf t.pdf. I have attached the XSL-FO file produced when running: java -jar /var/local/bin/css2xslfo1_0rc2.jar t.html -fo t.fo The output of my "java -version" is: java version "1.4.2_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) Regards, Werner. Andreas Jung wrote: > > > > --On Dienstag, 24. Mai 2005 17:36 Uhr +0200 Werner Donné > <wer...@re...> wrote: > >> Andreas, >> >> For me it does appear, but right after the other text. All I did >> was declaring the XHTML namespace. See attachment. >> > > When I look at the generated FO then I see the "Hello World" text sitting > between <fo:marker marker-class-name="mark"> but I don't see any reference > to this marker everywhere else in the file...could it be that this is a bug > in v1.0b2 and you might be using a newer version? > > Andreas > > -- 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 15:59:34
|
--On Dienstag, 24. Mai 2005 17:36 Uhr +0200 Werner Donn=E9=20 <wer...@re...> wrote: > Andreas, > > For me it does appear, but right after the other text. All I did > was declaring the XHTML namespace. See attachment. > When I look at the generated FO then I see the "Hello World" text sitting between <fo:marker marker-class-name=3D"mark"> but I don't see any = reference to this marker everywhere else in the file...could it be that this is a bug in v1.0b2 and you might be using a newer version? Andreas |
From: Andreas J. <li...@an...> - 2005-05-24 15:55:48
|
--On Dienstag, 24. Mai 2005 17:36 Uhr +0200 Werner Donn=E9=20 <wer...@re...> wrote: > Andreas, > > For me it does appear, but right after the other text. All I did > was declaring the XHTML namespace. See attachment. > Which renderer are you using. Neither Xinc, FOP nor XFC show "Hello World"=20 in the bottom :-( Andreas |
From: <wer...@re...> - 2005-05-24 15:37:01
|
Andreas, For me it does appear, but right after the other text. All I did was declaring the XHTML namespace. See attachment. Regards, Werner. Andreas Jung wrote: > > > --On Dienstag, 24. Mai 2005 17:03 Uhr +0200 Werner Donné > <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="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="mybottom"> > This should go to the bottom > <span class="mark"/> > </div> > > <h1>Hello world</h1> > > <div class="copyrightnotice"> > labber labber..... > labber labber..... > </div> > > </body> > </html> > > -- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: wer...@re... |