RE: [docbook-apps] Controlling the publishing process - shell scripts, Ant, other tools
Hi, I have been using ant for publishing for some time. Typical usage scenarios in my company are these: - publish documentation to webhelp and pdf as part of the application build - publish documentation as an eclipse infocenter plugin (this involves updating working copy from svn, stopping infocenter, publishing docs, starting infocenter) * What are some advantages an Ant-based publishing system has over a shell script system? Clearly Ant is cross-platform, what else? I do not have that much experience with shell scripts, but ant is quite extensible - you can use extension libraries or write you own. * Is there a typical Ant architecture for large, single-sourced documentation sets? I've got over 30 large documents being published to multiple formats. Would I set up a build.xml file for each document and format permutation and then have a master build.xml file to run them all at once? You could do with one file only. You could write a macro for each output format (http://ant.apache.org/manual/Tasks/macrodef.html) and then call it directly with parameters for each doc. Something like this: macrodef name=publish-to-pdf atribute name=input-file/ ... /macrodef target name=build-all-doc publish-to-pdf input-file=path-to-doc1/ publish-to-pdf input-file=path-to-doc2/ /target * The example on Dave Pawson's site (thanks, Dave!) shows web site publishing. Does anyone know of example Ant setups for publishing large manual sets to PDF and online help? I cannot share our build scripts, but our largest document has circa 700 pages (PDF). * Can Ant handle complicated file manipulation like packaging Eclipse help plugins into an Infocenter WAR file? Will I end up having to write shell-script code for an Ant task to execute? Yes, you can create war files directly usány the war task (http://ant.apache.org/manual/Tasks/war.html). Pavel Škopík -Original Message- From: Peter Desjardins [mailto:peter.desjardins...@gmail.com] Sent: Thursday, August 26, 2010 4:56 AM To: DocBook Apps Subject: [docbook-apps] Controlling the publishing process - shell scripts, Ant, other tools Hi. I've been publishing DocBook for a few years and I've always used shell scripts to control the process. This has worked well for me but I'm starting a new publishing system from scratch and I'd like to improve the maintainability and scalability of the process if I can. Although I could do anything I needed to do with my publishing system when it was based on shell scripts, it really wasn't something that could be easily maintained by someone else. I tried to comment and otherwise document my scripts but realistically, it would have been frustrating for someone else to pick through the logic. For my new publishing system, I'm considering using Apache Ant. I see that other people seem happy publishing XML with Ant and the software developers I work with use it for their build process. So I've started experimenting with Ant, starting with the examples at http://www.dpawson.co.uk/docbook/ant.html. It's not coming easily in the first few hours I've spent with it. Here are some of the questions I have. Any input will be very helpful. * What are some advantages an Ant-based publishing system has over a shell script system? Clearly Ant is cross-platform, what else? * Is there a typical Ant architecture for large, single-sourced documentation sets? I've got over 30 large documents being published to multiple formats. Would I set up a build.xml file for each document and format permutation and then have a master build.xml file to run them all at once? * The example on Dave Pawson's site (thanks, Dave!) shows web site publishing. Does anyone know of example Ant setups for publishing large manual sets to PDF and online help? * Can Ant handle complicated file manipulation like packaging Eclipse help plugins into an Infocenter WAR file? Will I end up having to write shell-script code for an Ant task to execute? * What other build control systems should I consider in this situation? I don't think my colleagues would be very excited about GNU make files. I'm not too excited about the idea of a CMS to handle publishing. Anything else? Thanks for your help. Peter Desjardins - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org __ Informace od ESET NOD32 Antivirus, verze databaze 5397 (20100825) __ Tuto zpravu proveril ESET NOD32 Antivirus. http://www.eset.cz __ Informace od ESET NOD32 Antivirus, verze databaze 5397 (20100825) __ Tuto zpravu proveril ESET NOD32 Antivirus. http://www.eset.cz - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Controlling the publishing process - shell scripts, Ant, other tools
On Wed, 25 Aug 2010 22:55:36 -0400 Peter Desjardins peter.desjardins...@gmail.com wrote: Here are some of the questions I have. Any input will be very helpful. * What are some advantages an Ant-based publishing system has over a shell script system? Clearly Ant is cross-platform, what else? Fairly well known Peter. More chance of others maintaining your script? * Is there a typical Ant architecture for large, single-sourced documentation sets? I've got over 30 large documents being published to multiple formats. Would I set up a build.xml file for each document and format permutation and then have a master build.xml file to run them all at once? I have multiple media in one ant build file. Suggest you review it and group our output as appropriate. There is an 'include' facility in ant which I use for definitions, you could look at that. I guess time spent on design will pay off later, usual ideas. * The example on Dave Pawson's site (thanks, Dave!) shows web site publishing. Does anyone know of example Ant setups for publishing large manual sets to PDF and online help? I do a 120 page document (embarrassed to say what) using 'book' root element. No problem. * Can Ant handle complicated file manipulation like packaging Eclipse help plugins into an Infocenter WAR file? Will I end up having to write shell-script code for an Ant task to execute? I call xslt using the java and task, I guess you could do the same for building a war file? Otherwise perhaps run them in bash as a precursor to running ant? * What other build control systems should I consider in this situation? I don't think my colleagues would be very excited about GNU make files. I'm not too excited about the idea of a CMS to handle publishing. Anything else? ditto... although Norm seems pretty impressed with his employers kit. Not that I've used Peter. HTH -- regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] I18N
I'm reading a text which is very localized. It's odd words, rather than boilerplate which I believe is the basis for docbook I18N. Anyone any references please for best practice in this area? I like the docbook principles, to keep all 'foreign' text out of the main body and reference it [via some means], for XSLT processing using the xml:lang and a 'set' of lang files. Could the docbook ideas be used for this? TIA regards Dave Pawson http://www.dpawson.co.uk XSLT, XSL-FO and docbook FAQ doc -- regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] Controlling the publishing process - shell scripts, Ant, other tools
Hi Peter,
I also use Ant for our build process and would add a couple of points to those
others have made:
The xslt task [1] allows you to pass in parameters if they have been
specified. This is very convenient since you want to use the default values
from the xslts unless you pass in a value. I.e. you don't want to pass in an
empty string and override the default in the xslts. So in the following
example, if=webhelp.include.search.tab tells the xslt task only to pass in
this param if the property webhelp.include.search.tab has been set.
xslt
in=${input-xml}
out=${output-dir}/dummy.html
style=${stylesheet-path}
scanincludeddirectories=false
classpath=${xslt-processor-classpath}
param name=webhelp.include.search.tab
expression=${webhelp.include.search.tab}
if=webhelp.include.search.tab/
param name=webhelp.base.dir expression=${output-dir}
if=output-dir/
param name=webhelp.indexer.language
expression=${webhelp.indexer.language} if=webhelp.indexer.language/
/xslt
I only use the xslt task with Saxon 6 and 9 and can use the classpath attribute
to pick the one I need, BUT it won't work if Saxon 6 is in the CLASSPATH when
you run Ant. If you get a mysterious error, try invoking ant with a clean
classpath.
Ant has a baby version of XML catalogs but can also use a real catalog
resolver. Sometimes the baby version is convenient if your needs are limited.
A limitation of Ant compared to shell scripts or make is that it lacks common
scripting constructs like if/then and try/catch. If you need things like this,
then you can use the ant-contrib extensions ([2] and [3]). I was reluctant to
use extensions, but ultimately found I needed the functionality.
To collect images for the output directory after assembling transclusions,
filtering, and so on, I run an xslt over the processed document and generate an
ant script, then run that ant script from the main ant script. I have it check
to see if any images are missing so it can fail if they are. To catch common
images (callouts, admon graphics) you need either to run the xslt on the output
or code the xslt so it knows what DcoBook constructs require what graphics.
As Pavel mentions, Ant is good at making war files etc. In fact, globbing is a
particular strength. By default, when making a zip of some kind, it excludes
obvious cruft like svn or cvs directories.
I've looked a little at xproc, which seems designed for this situation, but
haven't gotten far yet. I can tell that it would make certain parts very easy,
but one point I'm confused on is how chunked output is treated. Is each chunk a
separate pipeline that I can process further? How would I handle the image
case? Or perhaps I should invoke xproc from ant and each for certain tasks?
Btw., the webhelp gsoc project [5] has a sample ant build file that could give
some ideas (though very simple-minded wrt how it handles images). The idea is
that the user makes a small build.xml that declares a couple of properties
(input doc file name, desired output dir, and any xslt params to pass in), then
imports the main build.xml included with webhelp which contains the logic.
Hope that helps,
David
[1] http://ant.apache.org/manual/Tasks/style.html
[2] http://ant-contrib.sourceforge.net/
[3] http://ant-contrib.sourceforge.net/tasks/tasks/
[4] http://en.wikipedia.org/wiki/XProc
[5] http://www.thingbag.net/docbook/gsoc2010/doc/content/ch02s01.html
-Original Message-
From: Peter Desjardins [mailto:peter.desjardins...@gmail.com]
Sent: Wednesday, August 25, 2010 9:56 PM
To: DocBook Apps
Subject: [docbook-apps] Controlling the publishing process - shell scripts,
Ant, other tools
Hi. I've been publishing DocBook for a few years and I've always used
shell scripts to control the process. This has worked well for me but
I'm starting a new publishing system from scratch and I'd like to
improve the maintainability and scalability of the process if I can.
Although I could do anything I needed to do with my publishing system
when it was based on shell scripts, it really wasn't something that
could be easily maintained by someone else. I tried to comment and
otherwise document my scripts but realistically, it would have been
frustrating for someone else to pick through the logic.
For my new publishing system, I'm considering using Apache Ant. I see
that other people seem happy publishing XML with Ant and the software
developers I work with use it for their build process. So I've started
experimenting with Ant, starting with the examples at
http://www.dpawson.co.uk/docbook/ant.html. It's not coming easily in
the first few hours I've spent with it.
Here are some of the questions I have. Any input will be very helpful.
* What are some advantages an Ant-based publishing system has over a
shell script system? Clearly Ant is cross-platform, what else?
* Is there a typical Ant
Re: [docbook-apps] Segmented list issue with FOP
Dean: For what it is worth, I have also seen very similar errors - but definately not using a segmented list, Using DocBook XSL 1.75.2, FOP 0.95 same warning, and error message about proportional column width, and though not a segmented list it was in some other sort of list and/or a table. Process did not fail, and I was able to produce PDF. I thought it might be an issue with the FOP rendering, not the XML code. Your code looks fine to me. For what its worth /Gregorio -Original Message- From: deannelson deannel...@aol.com To: docbook-apps@lists.oasis-open.org Sent: Wed, Aug 25, 2010 5:12 pm Subject: [docbook-apps] Segmented list issue with FOP Hello all, I am using a segmented list (1.75.2) and it gives me a warning in FOP 1.0 but still renders fine: WARNING: The following feature isn't implemented by Apache FOP, yet: table-layout=auto (on fo:table) (See position 2:23461) Aug 25, 2010 2:05:58 PM org.apache.fop.events.LoggingEventListener processEvent SEVERE: Invalid property value encountered in column-width=proportional-column-width(1): org.apache.fop.fo.expr.PropertyException: file:/C:/doc/Documentation/403/seglisttest.fo:2:23461: proportional-column-width() function may only be used when fo:table has table-layout=fixed.; property:'column-width' (See position 2:23541) Aug 25, 2010 2:05:58 PM org.apache.fop.events.LoggingEventListener processEvent SEVERE: Invalid property value encountered in column-width=proportional-column-width(1): org.apache.fop.fo.expr.Proper tyException: file:/C:/doc/Documentation/403/seglisttest.fo:2:23461: proportional-column-width() function may only be use d when fo:table has table-layout=fixed.; property:'column-width' (See position 2:23621) - Here is the code I used: ?xml version=1.0 encoding=ISO-8859-1 standalone=no? !DOCTYPE section PUBLIC -//OASIS//DTD DocBook XML V4.5//EN http://www.docbook.org/xml/4.5/docbookx.dtd; [ ] section id=grip-chem titleEffect of Chemicals on Grip Plate Polymer/title segmentedlist type=tabular segtitleChemical/segtitle segtitleRating/segtitle seglistitem segAcetic acid/seg segB/seg /seglistitem seglistitem segAcetone/seg segC/seg /seglistitem seglistitem segAluminum Chloride solutions/seg segT/seg /seglistitem /segmentedlist /section I tried to find this in the stock style sheets but couldn't see where it is being generated. Is this just some old code that needs a touch up or is there a another parameter that I may have missed dealing with the sizing? Regards, Dean Nelson
RE: [docbook-apps] Controlling the publishing process - shell scripts, Ant, other tools
We have a fairly complex Ant based system that uses an individual build file for each document that includes a set of build files that have the actual targets for building; this allows us to customize things like file names and destination paths easily. Each document can be processed into a number of different outputs by selecting appropriate targets (things like build.pdf, build.html, build.html.single -- there are actually over a dozen targets, including a couple that do things like counting words and checking how much content is reused for estimates the localizers need). We routinely process documents that are 100 to 400 or so pages -- policy says to break them up into volumes if they get much larger. One thing we found really helpful is that Ant is XML, so we can use transforms to generate new Ant build files on the fly (to pass in dynamic parameters) and then transfer control to the new build file. Moving from Make files to Ant was a bit challenging at first for a bunch of UNIX hackers, but we found a lot of advantages to it due to it being XML (so the same tools that edit our documents can edit the build files) and having native XSLT transform capability built into it. It is extensible and easy to modularize things, which helps a lot. It also allowed us to make things cross-platform which became important as we rolled things out to a wider community of users. Regards, Larry Rowland -Original Message- From: Peter Desjardins [mailto:peter.desjardins...@gmail.com] Sent: Wednesday, August 25, 2010 8:56 PM To: DocBook Apps Subject: [docbook-apps] Controlling the publishing process - shell scripts, Ant, other tools Hi. I've been publishing DocBook for a few years and I've always used shell scripts to control the process. This has worked well for me but I'm starting a new publishing system from scratch and I'd like to improve the maintainability and scalability of the process if I can. Although I could do anything I needed to do with my publishing system when it was based on shell scripts, it really wasn't something that could be easily maintained by someone else. I tried to comment and otherwise document my scripts but realistically, it would have been frustrating for someone else to pick through the logic. For my new publishing system, I'm considering using Apache Ant. I see that other people seem happy publishing XML with Ant and the software developers I work with use it for their build process. So I've started experimenting with Ant, starting with the examples at http://www.dpawson.co.uk/docbook/ant.html. It's not coming easily in the first few hours I've spent with it. Here are some of the questions I have. Any input will be very helpful. * What are some advantages an Ant-based publishing system has over a shell script system? Clearly Ant is cross-platform, what else? * Is there a typical Ant architecture for large, single-sourced documentation sets? I've got over 30 large documents being published to multiple formats. Would I set up a build.xml file for each document and format permutation and then have a master build.xml file to run them all at once? * The example on Dave Pawson's site (thanks, Dave!) shows web site publishing. Does anyone know of example Ant setups for publishing large manual sets to PDF and online help? * Can Ant handle complicated file manipulation like packaging Eclipse help plugins into an Infocenter WAR file? Will I end up having to write shell-script code for an Ant task to execute? * What other build control systems should I consider in this situation? I don't think my colleagues would be very excited about GNU make files. I'm not too excited about the idea of a CMS to handle publishing. Anything else? Thanks for your help. Peter Desjardins - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Segmented list issue with FOP
Thanks, but that type doesn't do anything in the code. Also using the PIs does not help either. After looking closer in the 1.75.2 stylesheets, the segmentedlist template in fo/lists.xsl has a problem when used in FOP. It specifies the table as an auto table and it needs to be a fixed table since FOP doesn't support that feature yet. So, in this case I modified the template from fo:table to fo:table table-layout=fixed width=100% Is this something that should be addressed in the standard stylesheets (i.e bugtracked)? Regards, Dean Nelson In a message dated 08/26/10 01:01:55 Pacific Daylight Time, reflex...@reflexing.ru writes: On Thu, Aug 26, 2010 at 3:12 AM, deannelson deannel...@aol.com wrote: Hello all, I am using a segmented list (1.75.2) and it gives me a warning in FOP 1.0 but still renders fine: WARNING: The following feature isn't implemented by Apache FOP, yet: table-layout=auto (on fo:table) (See position 2:23461) Aug 25, 2010 2:05:58 PM org.apache.fop.events.LoggingEventListener processEvent SEVERE: Invalid property value encountered in column-width=proportional-column-width(1): org.apache.fop.fo.expr.PropertyException: file:/C:/doc/Documentation/403/seglisttest.fo:2:23461: proportional-column-width() function may only be used when fo:table has table-layout=fixed.; property:'column-width' (See position 2:23541) Aug 25, 2010 2:05:58 PM org.apache.fop.events.LoggingEventListener processEvent SEVERE: Invalid property value encountered in column-width=proportional-column-width(1): org.apache.fop.fo.expr.Proper tyException: file:/C:/doc/Documentation/403/seglisttest.fo:2:23461: proportional-column-width() function may only be use d when fo:table has table-layout=fixed.; property:'column-width' (See position 2:23621) - Here is the code I used: ?xml version=1.0 encoding=ISO-8859-1 standalone=no? !DOCTYPE section PUBLIC -//OASIS//DTD DocBook XML V4.5//EN http://www.docbook.org/xml/4.5/docbookx.dtd; [ ] section id=grip-chem titleEffect of Chemicals on Grip Plate Polymer/title segmentedlist type=tabular segtitleChemical/segtitle segtitleRating/segtitle seglistitem segAcetic acid/seg segB/seg /seglistitem seglistitem segAcetone/seg segC/seg /seglistitem seglistitem segAluminum Chloride solutions/seg segT/seg /seglistitem /segmentedlist /section I tried to find this in the stock style sheets but couldn't see where it is being generated. Is this just some old code that needs a touch up or is there a another parameter that I may have missed dealing with the sizing? Regards, Dean Nelson Hello Dean. Do you have customized DocBook? Cause segmentedlist element doesn't have type attribute. Can you please cut it off and use this processing instructions instead: ?dbhtml list-presentation=table? ?dbfo list-presentation=table? Hope it will help. -- Jabber: reflex...@reflexing.ru, ICQ: 8163230, Skype on demand.
Re: [docbook-apps] Segmented list issue with FOP
Hi, Actually, this was a bug in DocBook XSL. The stylesheets sometimes use fo:table to layout certain elements. For segmentedlist, a layout table is used if the stylesheet parameter 'segmentedlist.as.table' is changed from the default 0 to 1. In this case, because the fo:table-columns use proportional-column-width(), it should set the table property 'table-layout' to 'fixed' instead of the default value of 'auto'. This bug has already been fixed in SVN and will be in the next release. Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: gpev...@aol.com To: deannel...@aol.com ; docbook-apps@lists.oasis-open.org Sent: Thursday, August 26, 2010 7:03 AM Subject: Re: [docbook-apps] Segmented list issue with FOP Dean: For what it is worth, I have also seen very similar errors - but definately not using a segmented list, Using DocBook XSL 1.75.2, FOP 0.95 same warning, and error message about proportional column width, and though not a segmented list it was in some other sort of list and/or a table. Process did not fail, and I was able to produce PDF. I thought it might be an issue with the FOP rendering, not the XML code. Your code looks fine to me. For what its worth /Gregorio -Original Message- From: deannelson deannel...@aol.com To: docbook-apps@lists.oasis-open.org Sent: Wed, Aug 25, 2010 5:12 pm Subject: [docbook-apps] Segmented list issue with FOP Hello all, I am using a segmented list (1.75.2) and it gives me a warning in FOP 1.0 but still renders fine: WARNING: The following feature isn't implemented by Apache FOP, yet: table-layout=auto (on fo:table) (See position 2:23461) Aug 25, 2010 2:05:58 PM org.apache.fop.events.LoggingEventListener processEvent SEVERE: Invalid property value encountered in column-width=proportional-column-width(1): org.apache.fop.fo.expr.PropertyException: file:/C:/doc/Documentation/403/seglisttest.fo:2:23461: proportional-column-width() function may only be used when fo:table has table-layout=fixed.; property:'column-width' (See position 2:23541) Aug 25, 2010 2:05:58 PM org.apache.fop.events.LoggingEventListener processEvent SEVERE: Invalid property value encountered in column-width=proportional-column-width(1): org.apache.fop.fo.expr.Proper tyException: file:/C:/doc/Documentation/403/seglisttest.fo:2:23461: proportional-column-width() function may only be use d when fo:table has table-layout=fixed.; property:'column-width' (See position 2:23621) - Here is the code I used: ?xml version=1.0 encoding=ISO-8859-1 standalone=no? !DOCTYPE section PUBLIC -//OASIS//DTD DocBook XML V4.5//EN http://www.docbook.org/xml/4.5/docbookx.dtd; [ ] section id=grip-chem titleEffect of Chemicals on Grip Plate Polymer/title segmentedlist type=tabular segtitleChemical/segtitle segtitleRating/segtitle seglistitem segAcetic acid/seg segB/seg /seglistitem seglistitem segAcetone/seg segC/seg /seglistitem seglistitem segAluminum Chloride solutions/seg segT/seg /seglistitem /segmentedlist /section I tried to find this in the stock style sheets but couldn't see where it is being generated. Is this just some old code that needs a touch up or is there a another parameter that I may have missed dealing with the sizing? Regards, Dean Nelson
RE: [docbook-apps] Segmented list issue with FOP
| -Original Message- | From: deannelson | | After looking closer in the 1.75.2 stylesheets, the | segmentedlist template in fo/lists.xsl has a problem when | used in FOP. It specifies the table as an auto table and | it needs to be a fixed table since FOP doesn't support | that feature yet. So, in this case I modified the template | | from | | fo:table | | to | | fo:table table-layout=fixed width=100% | | Is this something that should be addressed in the standard | stylesheets (i.e bugtracked)? I committed a fix a few weeks ago: http://docbook.svn.sourceforge.net/viewvc/docbook?view=revisionrevision=876 1 Mauritz - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] I18N
Hi Dave, I guess I need some clarification of your terminology here. When you say odd words, I presume that means the text is mixed language text, with foreign words mixed with English text, rather than foreign content isolated in elements? And when you say boilerplate, are you referring to the generated text specified in the stylesheet files common/*.xml, which is used for generating Chapter labels and such? I usually think of boilerplate as pre-written reusable snippets of content that are specific to a project. With mixed text of odd words, I'm not sure how useful it is to separate out the content into separate files. Certainly marking content with phrase lang=xx might be helpful, depending on what you need to do with it. Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: Dave Pawson da...@dpawson.co.uk To: docbook-apps@lists.oasis-open.org Sent: Thursday, August 26, 2010 4:47 AM Subject: [docbook-apps] I18N I'm reading a text which is very localized. It's odd words, rather than boilerplate which I believe is the basis for docbook I18N. Anyone any references please for best practice in this area? I like the docbook principles, to keep all 'foreign' text out of the main body and reference it [via some means], for XSLT processing using the xml:lang and a 'set' of lang files. Could the docbook ideas be used for this? TIA regards Dave Pawson http://www.dpawson.co.uk XSLT, XSL-FO and docbook FAQ doc -- regards -- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Segmented list issue with FOP
BTW, my direct email responses to Mauritz are bouncing. I wonder if he is aware of that problem? I don't have an alternate channel to inform him. Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: deannelson To: Mauritz Jeanson ; 'reflexing' ; docbook-apps@lists.oasis-open.org Sent: Thursday, August 26, 2010 12:55 PM Subject: Re: [docbook-apps] Segmented list issue with FOP Thanks Mauritz Bob! In a message dated 08/26/10 09:37:07 Pacific Daylight Time, m...@johanneberg.com writes: | -Original Message- | From: deannelson | | After looking closer in the 1.75.2 stylesheets, the | segmentedlist template in fo/lists.xsl has a problem when | used in FOP. It specifies the table as an auto table and | it needs to be a fixed table since FOP doesn't support | that feature yet. So, in this case I modified the template | | from | | fo:table | | to | | fo:table table-layout=fixed width=100% | | Is this something that should be addressed in the standard | stylesheets (i.e bugtracked)? I committed a fix a few weeks ago: http://docbook.svn.sourceforge.net/viewvc/docbook?view=revisionrevision=876 1 Mauritz - To unsubscribe, e-mail : docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Segmented list issue with FOP
Thanks Mauritz Bob! In a message dated 08/26/10 09:37:07 Pacific Daylight Time, m...@johanneberg.com writes: | -Original Message- | From: deannelson | | After looking closer in the 1.75.2 stylesheets, the | segmentedlist template in fo/lists.xsl has a problem when | used in FOP. It specifies the table as an auto table and | it needs to be a fixed table since FOP doesn't support | that feature yet. So, in this case I modified the template | | from | | fo:table | | to | | fo:table table-layout=fixed width=100% | | Is this something that should be addressed in the standard | stylesheets (i.e bugtracked)? I committed a fix a few weeks ago: http://docbook.svn.sourceforge.net/viewvc/docbook?view=revisionrevision=876 1 Mauritz - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
