From: SourceForge.net <no...@so...> - 2005-06-08 11:52:12
|
Bugs item #1216970, was opened at 2005-06-08 13:52 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1216970&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XSL Group: Print/FO/PDF Status: Open Resolution: None Priority: 5 Submitted By: César Martínez Izquierdo (dispiste) Assigned to: Nobody/Anonymous (nobody) Summary: body.start.indent is ignored in CVS version Initial Comment: Hi, I've installed the CVS version of Docbook XSL in order to avoid bug #1215114 (which has been corrected in CVS). However, when I use that version (from http://docbook.sourceforge.net/snapshots/, version of 2005-06-08), the body.start.indent parameter is ignored (the paragraph is indented). Note that body.start.indent is only ignored when using at the same time fop.extensions=1. Here there is a simple example to show the error: <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "/usr/share/xml/docbook/schema/dtd/4.4/docbookx.dtd"> <book><title>This is the a book written to solve a bug</title> <chapter><title>An example</title> <para>This shouldn't be indented, as body.start.indent = 0</para> </chapter> </book> My customization layer is the following file: <?xml version='1.0'?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" version="1.0"> <!-- External stylesheets --> <!-- The original docbook stylesheets --> <xsl:import href="docbook-xsl-snapshot/fo/docbook.xsl"/> <xsl:param name="body.start.indent" select="'0cm'" /> <xsl:param name="fop.extensions" select="'1'" /> <!-- Draft properties --> <xsl:param name="draft.mode" select="'no'" /> </xsl:stylesheet> (Note that if I remove the fop.extensions parameter, it works fine). In order to produce the PDF, I use the following commands: xsltproc -o tmp/test.fo custom-docbook/simple-custom-docbook.xsl test.docbook fop -pdf test.pdf tmp/test.fo I use xsltproc and fop from official Debian packages (sid). Fop version is 0.20.5 $ xsltproc --version Using libxml 20616, libxslt 10112 and libexslt 810 xsltproc was compiled against libxml 20616, libxslt 10112 and libexslt 810 libxslt 10112 was compiled against libxml 20616 libexslt 810 was compiled against libxml 20616 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1216970&group_id=21935 |
From: SourceForge.net <no...@so...> - 2005-06-14 08:04:37
|
Bugs item #1216970, was opened at 2005-06-08 04:52 Message generated for change (Comment added) made by bobstayton You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1216970&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XSL Group: Print/FO/PDF Status: Open Resolution: None Priority: 5 Submitted By: César Martínez Izquierdo (dispiste) >Assigned to: Robert Stayton (bobstayton) Summary: body.start.indent is ignored in CVS version Initial Comment: Hi, I've installed the CVS version of Docbook XSL in order to avoid bug #1215114 (which has been corrected in CVS). However, when I use that version (from http://docbook.sourceforge.net/snapshots/, version of 2005-06-08), the body.start.indent parameter is ignored (the paragraph is indented). Note that body.start.indent is only ignored when using at the same time fop.extensions=1. Here there is a simple example to show the error: <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "/usr/share/xml/docbook/schema/dtd/4.4/docbookx.dtd"> <book><title>This is the a book written to solve a bug</title> <chapter><title>An example</title> <para>This shouldn't be indented, as body.start.indent = 0</para> </chapter> </book> My customization layer is the following file: <?xml version='1.0'?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" version="1.0"> <!-- External stylesheets --> <!-- The original docbook stylesheets --> <xsl:import href="docbook-xsl-snapshot/fo/docbook.xsl"/> <xsl:param name="body.start.indent" select="'0cm'" /> <xsl:param name="fop.extensions" select="'1'" /> <!-- Draft properties --> <xsl:param name="draft.mode" select="'no'" /> </xsl:stylesheet> (Note that if I remove the fop.extensions parameter, it works fine). In order to produce the PDF, I use the following commands: xsltproc -o tmp/test.fo custom-docbook/simple-custom-docbook.xsl test.docbook fop -pdf test.pdf tmp/test.fo I use xsltproc and fop from official Debian packages (sid). Fop version is 0.20.5 $ xsltproc --version Using libxml 20616, libxslt 10112 and libexslt 810 xsltproc was compiled against libxml 20616, libxslt 10112 and libexslt 810 libxslt 10112 was compiled against libxml 20616 libexslt 810 was compiled against libxml 20616 ---------------------------------------------------------------------- >Comment By: Robert Stayton (bobstayton) Date: 2005-06-14 01:04 Message: Logged In: YES user_id=193218 FOP does not apply a start-indent that is put into the fo:flow element, which is why $body.start.indent is ignored when using FOP. I think the indent you are seeing is the $title.margin.left mechanism that $body.start.indent was designed to replace. In fop, the $title.margin.left is still set to -4pc by default, which produces a positive 4pc para indent. If you set title.margin.left to 0cm, then your para should not be indented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1216970&group_id=21935 |
From: SourceForge.net <no...@so...> - 2005-06-14 11:28:49
|
Bugs item #1216970, was opened at 2005-06-08 13:52 Message generated for change (Comment added) made by dispiste You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1216970&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XSL Group: Print/FO/PDF Status: Open Resolution: None Priority: 5 Submitted By: César Martínez Izquierdo (dispiste) Assigned to: Robert Stayton (bobstayton) Summary: body.start.indent is ignored in CVS version Initial Comment: Hi, I've installed the CVS version of Docbook XSL in order to avoid bug #1215114 (which has been corrected in CVS). However, when I use that version (from http://docbook.sourceforge.net/snapshots/, version of 2005-06-08), the body.start.indent parameter is ignored (the paragraph is indented). Note that body.start.indent is only ignored when using at the same time fop.extensions=1. Here there is a simple example to show the error: <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "/usr/share/xml/docbook/schema/dtd/4.4/docbookx.dtd"> <book><title>This is the a book written to solve a bug</title> <chapter><title>An example</title> <para>This shouldn't be indented, as body.start.indent = 0</para> </chapter> </book> My customization layer is the following file: <?xml version='1.0'?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" version="1.0"> <!-- External stylesheets --> <!-- The original docbook stylesheets --> <xsl:import href="docbook-xsl-snapshot/fo/docbook.xsl"/> <xsl:param name="body.start.indent" select="'0cm'" /> <xsl:param name="fop.extensions" select="'1'" /> <!-- Draft properties --> <xsl:param name="draft.mode" select="'no'" /> </xsl:stylesheet> (Note that if I remove the fop.extensions parameter, it works fine). In order to produce the PDF, I use the following commands: xsltproc -o tmp/test.fo custom-docbook/simple-custom-docbook.xsl test.docbook fop -pdf test.pdf tmp/test.fo I use xsltproc and fop from official Debian packages (sid). Fop version is 0.20.5 $ xsltproc --version Using libxml 20616, libxslt 10112 and libexslt 810 xsltproc was compiled against libxml 20616, libxslt 10112 and libexslt 810 libxslt 10112 was compiled against libxml 20616 libexslt 810 was compiled against libxml 20616 ---------------------------------------------------------------------- >Comment By: César Martínez Izquierdo (dispiste) Date: 2005-06-14 13:28 Message: Logged In: YES user_id=245862 I don't understand you very well. The body.start.indent parameter was working fine with fop and docbook-xsl 1.68.1, so it looks like a regression. Do you mean that the CVS version implements the same parameter in the a different way which is not compatible with fop (because of fop's fault)?? Regards. ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2005-06-14 10:04 Message: Logged In: YES user_id=193218 FOP does not apply a start-indent that is put into the fo:flow element, which is why $body.start.indent is ignored when using FOP. I think the indent you are seeing is the $title.margin.left mechanism that $body.start.indent was designed to replace. In fop, the $title.margin.left is still set to -4pc by default, which produces a positive 4pc para indent. If you set title.margin.left to 0cm, then your para should not be indented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1216970&group_id=21935 |
From: SourceForge.net <no...@so...> - 2005-06-14 15:33:58
|
Bugs item #1216970, was opened at 2005-06-08 04:52 Message generated for change (Comment added) made by bobstayton You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1216970&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XSL Group: Print/FO/PDF Status: Open Resolution: None Priority: 5 Submitted By: César Martínez Izquierdo (dispiste) Assigned to: Robert Stayton (bobstayton) Summary: body.start.indent is ignored in CVS version Initial Comment: Hi, I've installed the CVS version of Docbook XSL in order to avoid bug #1215114 (which has been corrected in CVS). However, when I use that version (from http://docbook.sourceforge.net/snapshots/, version of 2005-06-08), the body.start.indent parameter is ignored (the paragraph is indented). Note that body.start.indent is only ignored when using at the same time fop.extensions=1. Here there is a simple example to show the error: <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "/usr/share/xml/docbook/schema/dtd/4.4/docbookx.dtd"> <book><title>This is the a book written to solve a bug</title> <chapter><title>An example</title> <para>This shouldn't be indented, as body.start.indent = 0</para> </chapter> </book> My customization layer is the following file: <?xml version='1.0'?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" version="1.0"> <!-- External stylesheets --> <!-- The original docbook stylesheets --> <xsl:import href="docbook-xsl-snapshot/fo/docbook.xsl"/> <xsl:param name="body.start.indent" select="'0cm'" /> <xsl:param name="fop.extensions" select="'1'" /> <!-- Draft properties --> <xsl:param name="draft.mode" select="'no'" /> </xsl:stylesheet> (Note that if I remove the fop.extensions parameter, it works fine). In order to produce the PDF, I use the following commands: xsltproc -o tmp/test.fo custom-docbook/simple-custom-docbook.xsl test.docbook fop -pdf test.pdf tmp/test.fo I use xsltproc and fop from official Debian packages (sid). Fop version is 0.20.5 $ xsltproc --version Using libxml 20616, libxslt 10112 and libexslt 810 xsltproc was compiled against libxml 20616, libxslt 10112 and libexslt 810 libxslt 10112 was compiled against libxml 20616 libexslt 810 was compiled against libxml 20616 ---------------------------------------------------------------------- >Comment By: Robert Stayton (bobstayton) Date: 2005-06-14 08:33 Message: Logged In: YES user_id=193218 I checked my notes, and it turns out that the problem is not that FOP doesn't support start-indent on the fo:flow element. It is that FOP only supports margin-left on the page area, not on block areas. As a result, FOP treats margin-left as the start-indent. This means you cannot use a margin-left relative to a start-indent as you can in every other processor. So FOP seems to work, which is why it got into 1.68.1. But if you try to use body.start.indent in combination with a relative margin-left (such as in a TOC), then your indents will be scrambled. There is no way to generally support body.start.indent with FOP, so I disabled it after 1.68.1 release. I updated the doc to explain, but for some reason it didn't get into the snapshot (I'll make sure it is in the next release). If you still want to use body.start.indent and deal with any margin problems, then customize the set.flow.properties template from fo/pagesetup.xsl. You'll see that is where it is disabled for FOP. Otherwise you can go back to title.margin.left, which also is not perfect. I really really wish the FOP developers would release a better version, as supporting it is becoming a real pain. ---------------------------------------------------------------------- Comment By: César Martínez Izquierdo (dispiste) Date: 2005-06-14 04:28 Message: Logged In: YES user_id=245862 I don't understand you very well. The body.start.indent parameter was working fine with fop and docbook-xsl 1.68.1, so it looks like a regression. Do you mean that the CVS version implements the same parameter in the a different way which is not compatible with fop (because of fop's fault)?? Regards. ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2005-06-14 01:04 Message: Logged In: YES user_id=193218 FOP does not apply a start-indent that is put into the fo:flow element, which is why $body.start.indent is ignored when using FOP. I think the indent you are seeing is the $title.margin.left mechanism that $body.start.indent was designed to replace. In fop, the $title.margin.left is still set to -4pc by default, which produces a positive 4pc para indent. If you set title.margin.left to 0cm, then your para should not be indented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1216970&group_id=21935 |
From: SourceForge.net <no...@so...> - 2005-06-30 02:58:30
|
Bugs item #1216970, was opened at 2005-06-08 04:52 Message generated for change (Settings changed) made by bobstayton You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1216970&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XSL Group: Print/FO/PDF >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: César Martínez Izquierdo (dispiste) Assigned to: Robert Stayton (bobstayton) Summary: body.start.indent is ignored in CVS version Initial Comment: Hi, I've installed the CVS version of Docbook XSL in order to avoid bug #1215114 (which has been corrected in CVS). However, when I use that version (from http://docbook.sourceforge.net/snapshots/, version of 2005-06-08), the body.start.indent parameter is ignored (the paragraph is indented). Note that body.start.indent is only ignored when using at the same time fop.extensions=1. Here there is a simple example to show the error: <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "/usr/share/xml/docbook/schema/dtd/4.4/docbookx.dtd"> <book><title>This is the a book written to solve a bug</title> <chapter><title>An example</title> <para>This shouldn't be indented, as body.start.indent = 0</para> </chapter> </book> My customization layer is the following file: <?xml version='1.0'?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" version="1.0"> <!-- External stylesheets --> <!-- The original docbook stylesheets --> <xsl:import href="docbook-xsl-snapshot/fo/docbook.xsl"/> <xsl:param name="body.start.indent" select="'0cm'" /> <xsl:param name="fop.extensions" select="'1'" /> <!-- Draft properties --> <xsl:param name="draft.mode" select="'no'" /> </xsl:stylesheet> (Note that if I remove the fop.extensions parameter, it works fine). In order to produce the PDF, I use the following commands: xsltproc -o tmp/test.fo custom-docbook/simple-custom-docbook.xsl test.docbook fop -pdf test.pdf tmp/test.fo I use xsltproc and fop from official Debian packages (sid). Fop version is 0.20.5 $ xsltproc --version Using libxml 20616, libxslt 10112 and libexslt 810 xsltproc was compiled against libxml 20616, libxslt 10112 and libexslt 810 libxslt 10112 was compiled against libxml 20616 libexslt 810 was compiled against libxml 20616 ---------------------------------------------------------------------- >Comment By: Robert Stayton (bobstayton) Date: 2005-06-29 19:58 Message: Logged In: YES user_id=193218 I'm going to close this bug because the behavior that was described as a problem was actually intentional. FOP cannot support a body start-indent, and so it is disabled. Use title.margin.left to control the overall text indent when using FOP. If you have an undesirable indent with FOP, then set title.margin.left to 0pt. ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2005-06-14 08:33 Message: Logged In: YES user_id=193218 I checked my notes, and it turns out that the problem is not that FOP doesn't support start-indent on the fo:flow element. It is that FOP only supports margin-left on the page area, not on block areas. As a result, FOP treats margin-left as the start-indent. This means you cannot use a margin-left relative to a start-indent as you can in every other processor. So FOP seems to work, which is why it got into 1.68.1. But if you try to use body.start.indent in combination with a relative margin-left (such as in a TOC), then your indents will be scrambled. There is no way to generally support body.start.indent with FOP, so I disabled it after 1.68.1 release. I updated the doc to explain, but for some reason it didn't get into the snapshot (I'll make sure it is in the next release). If you still want to use body.start.indent and deal with any margin problems, then customize the set.flow.properties template from fo/pagesetup.xsl. You'll see that is where it is disabled for FOP. Otherwise you can go back to title.margin.left, which also is not perfect. I really really wish the FOP developers would release a better version, as supporting it is becoming a real pain. ---------------------------------------------------------------------- Comment By: César Martínez Izquierdo (dispiste) Date: 2005-06-14 04:28 Message: Logged In: YES user_id=245862 I don't understand you very well. The body.start.indent parameter was working fine with fop and docbook-xsl 1.68.1, so it looks like a regression. Do you mean that the CVS version implements the same parameter in the a different way which is not compatible with fop (because of fop's fault)?? Regards. ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2005-06-14 01:04 Message: Logged In: YES user_id=193218 FOP does not apply a start-indent that is put into the fo:flow element, which is why $body.start.indent is ignored when using FOP. I think the indent you are seeing is the $title.margin.left mechanism that $body.start.indent was designed to replace. In fop, the $title.margin.left is still set to -4pc by default, which produces a positive 4pc para indent. If you set title.margin.left to 0cm, then your para should not be indented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1216970&group_id=21935 |
From: SourceForge.net <no...@so...> - 2005-06-30 17:23:01
|
Bugs item #1216970, was opened at 2005-06-08 13:52 Message generated for change (Comment added) made by dispiste You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1216970&group_id=21935 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: DocBook XSL Group: Print/FO/PDF Status: Closed Resolution: Rejected Priority: 5 Submitted By: César Martínez Izquierdo (dispiste) Assigned to: Robert Stayton (bobstayton) Summary: body.start.indent is ignored in CVS version Initial Comment: Hi, I've installed the CVS version of Docbook XSL in order to avoid bug #1215114 (which has been corrected in CVS). However, when I use that version (from http://docbook.sourceforge.net/snapshots/, version of 2005-06-08), the body.start.indent parameter is ignored (the paragraph is indented). Note that body.start.indent is only ignored when using at the same time fop.extensions=1. Here there is a simple example to show the error: <?xml version='1.0' encoding='UTF-8'?> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "/usr/share/xml/docbook/schema/dtd/4.4/docbookx.dtd"> <book><title>This is the a book written to solve a bug</title> <chapter><title>An example</title> <para>This shouldn't be indented, as body.start.indent = 0</para> </chapter> </book> My customization layer is the following file: <?xml version='1.0'?> <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:fo="http://www.w3.org/1999/XSL/Format" version="1.0"> <!-- External stylesheets --> <!-- The original docbook stylesheets --> <xsl:import href="docbook-xsl-snapshot/fo/docbook.xsl"/> <xsl:param name="body.start.indent" select="'0cm'" /> <xsl:param name="fop.extensions" select="'1'" /> <!-- Draft properties --> <xsl:param name="draft.mode" select="'no'" /> </xsl:stylesheet> (Note that if I remove the fop.extensions parameter, it works fine). In order to produce the PDF, I use the following commands: xsltproc -o tmp/test.fo custom-docbook/simple-custom-docbook.xsl test.docbook fop -pdf test.pdf tmp/test.fo I use xsltproc and fop from official Debian packages (sid). Fop version is 0.20.5 $ xsltproc --version Using libxml 20616, libxslt 10112 and libexslt 810 xsltproc was compiled against libxml 20616, libxslt 10112 and libexslt 810 libxslt 10112 was compiled against libxml 20616 libexslt 810 was compiled against libxml 20616 ---------------------------------------------------------------------- >Comment By: César Martínez Izquierdo (dispiste) Date: 2005-06-30 19:22 Message: Logged In: YES user_id=245862 OK, thank you very much for your attention and all your comments about the bug. I hope a new release of FOP it is released soon, so that it solves so much problems (it really seems that there will be a new version in a couple of months). ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2005-06-30 04:58 Message: Logged In: YES user_id=193218 I'm going to close this bug because the behavior that was described as a problem was actually intentional. FOP cannot support a body start-indent, and so it is disabled. Use title.margin.left to control the overall text indent when using FOP. If you have an undesirable indent with FOP, then set title.margin.left to 0pt. ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2005-06-14 17:33 Message: Logged In: YES user_id=193218 I checked my notes, and it turns out that the problem is not that FOP doesn't support start-indent on the fo:flow element. It is that FOP only supports margin-left on the page area, not on block areas. As a result, FOP treats margin-left as the start-indent. This means you cannot use a margin-left relative to a start-indent as you can in every other processor. So FOP seems to work, which is why it got into 1.68.1. But if you try to use body.start.indent in combination with a relative margin-left (such as in a TOC), then your indents will be scrambled. There is no way to generally support body.start.indent with FOP, so I disabled it after 1.68.1 release. I updated the doc to explain, but for some reason it didn't get into the snapshot (I'll make sure it is in the next release). If you still want to use body.start.indent and deal with any margin problems, then customize the set.flow.properties template from fo/pagesetup.xsl. You'll see that is where it is disabled for FOP. Otherwise you can go back to title.margin.left, which also is not perfect. I really really wish the FOP developers would release a better version, as supporting it is becoming a real pain. ---------------------------------------------------------------------- Comment By: César Martínez Izquierdo (dispiste) Date: 2005-06-14 13:28 Message: Logged In: YES user_id=245862 I don't understand you very well. The body.start.indent parameter was working fine with fop and docbook-xsl 1.68.1, so it looks like a regression. Do you mean that the CVS version implements the same parameter in the a different way which is not compatible with fop (because of fop's fault)?? Regards. ---------------------------------------------------------------------- Comment By: Robert Stayton (bobstayton) Date: 2005-06-14 10:04 Message: Logged In: YES user_id=193218 FOP does not apply a start-indent that is put into the fo:flow element, which is why $body.start.indent is ignored when using FOP. I think the indent you are seeing is the $title.margin.left mechanism that $body.start.indent was designed to replace. In fop, the $title.margin.left is still set to -4pc by default, which produces a positive 4pc para indent. If you set title.margin.left to 0cm, then your para should not be indented. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=373747&aid=1216970&group_id=21935 |