Re: AW: [docbook-apps] ragged index with recent fop snapshots
Mike Maxwell maxw...@umiacs.umd.edu was heard to say: The easiest way to get all the LaTeX packages you might need to have installed is to install the latest TeX Live distro: http://www.tug.org/texlive/ It's big, but compared to hard disks these days, no worries. FreeBSD still has teTeX on board, although they may eventually drop support given that Thomas Esser no longer maintains the distro. teTeX has been good enough for me through the years as I mostly have used it for SGML/Passivetex processing once in a while. Moving to TeX Live would certainly make sense if I used TeX more often. As for the font issue: I'm not sure whether you were using LaTeX (8-bit pre-Unicode characters) or XeLaTeX (Unicode compliant version). (Both come in the Tex Live distro.) On the assumption that your XML was Unicode, you should have been using XeLaTeX. A good Unicode font (and it's nice looking, too) is the Charis SIL font: http://scripts.sil.org/CharisSILfont It includes regular, bold, italic, bold italic, small caps, tons of diacritics, IPA etc. It does not however cover Greek characters. I assume that dblatex and/or teTeX do not have any provisions to handle UTF-8 encoded XML files automagically. This may be the point where my problems started. I'm sure there are Unicode fonts that cover both Roman and Greek characters (Arial Unicode does, but is probably not what one would want for typesetting). I'm currently using two non-Unicode fonts that still have all required glyphs. It required a bit of testing though, but many fonts actually have a full set of greek characters and those few symbols that my document uses. The more general solution is to tag the non-Roman strings in XML (either manually or by a script), and create a small XSL transform that tags them for the font when converting to XeLaTeX. We do that for our grammars, which routinely mix in strings in Perso-Arabic scripts, Bengali script, etc. Or you could run a script over the XeLaTeX output by dblatex and font-tag the non-Roman strings directly. You might also want to use the Polyglossia package http://www.tex.ac.uk/ctan/macros/xetex/latex/polyglossia/ to provide language-specific hyphenation, etc. And if someone wants help, there's a XeTeX mailing list: http://www.tug.org/mailman/listinfo/xetex Thanks for these explanations. Now I'm sure that dblatex would do the trick if I put enough effort in setting up things properly. best regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: AW: [docbook-apps] ragged index with recent fop snapshots
davep da...@dpawson.co.uk was heard to say: You need to tell xep where your fonts are, then tell xep to embed the fonts in the PDF so others can read the document. file is xep.xml in the installation directory fonts xmlns=http://www.renderx.com/XEP/config; xml:base=fonts/ default-family=Helvetica!-- relative to xep installation -- Then, for example !-- Fedora fonts -- font-group xml:base=/usr/share/fonts/ label=TrueType embed=true subset=true font-family name=Stam Ashkenaz CLM fontfont-data ttf=culmus/StamAshkenazCLM.ttf/ /font /font-family /font-group Note the 'embed' attribute Thanks Dave for these explanations. I was naive enough to simply follow the instructions shipped with XEP. They told me to put a config file into the current working directory and add the fonts as you describe above. I'm not sure if they mentioned the embed attribute though. In any case, the config file didn't make any difference. I'll try modifying the config file in the install directory as you suggest. Do you have any suggestions for fixing the graphics file problem? XEP can't handle roughly half of my graphics files. I'd have to check the logs again in order to find out which types are affected. regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 - 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] fo template 'header.content'
I want to tweak the header contents. http://www.sagehill.net/docbookxsl/PrintHeaders.html#PrintHeadersText suggests header.content is the right place. Running that, no priority attribute I get Error at xsl:call-template on line 2025 of file:/sgml/docbook/docbook-xsl-ns-1.76.1/fo/pagesetup.xsl: There are several templates named 'header.content' with the same import precedence 3 times. Documentation or use of include rather than import? 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] docbook to word
Hey guys! I should convert docbook 5 to word. Now I only used to convert with fop 1.0 to html and pdf. I founde the stylesheet dbk2wordml.xsl. How do I handle it? which converter do I need? which customizations? Kind regards -- Gruß Lwam Berhane punkt.de GmbH TYPO3-Internet-Dienstleistungen-Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe i...@punkt.dehttp://punkt.de/ AG Mannheim 108285 Gf: Jürgen Egeling - 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] fo template 'header.content'
davep da...@dpawson.co.uk was heard to say: I want to tweak the header contents. http://www.sagehill.net/docbookxsl/PrintHeaders.html#PrintHeadersText suggests header.content is the right place. Hi Dave, I've used Bob's instructions just lately to modify the headers, and things worked right out of the box. I copied the template from fo/pagesetup.xsl to my customization layer and applied a few tweaks to obtain the desired results. What does your customization layer look like? regards, Markus -- Markus Hoenicka http://www.mhoenicka.de AQ score 38 - 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] fo template 'header.content'
On 08/01/2011 12:07 PM, Markus Hoenicka wrote: davep da...@dpawson.co.uk was heard to say: I want to tweak the header contents. http://www.sagehill.net/docbookxsl/PrintHeaders.html#PrintHeadersText suggests header.content is the right place. Hi Dave, I've used Bob's instructions just lately to modify the headers, and things worked right out of the box. I copied the template from fo/pagesetup.xsl to my customization layer and applied a few tweaks to obtain the desired results. What does your customization layer look like? Wrong! I had the template in the customization layer twice. My bad. Sorry to waste bandwidth. Tks Markus 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: AW: [docbook-apps] ragged index with recent fop snapshots
On 8/1/2011 3:45 AM, Markus Hoenicka wrote: I assume that dblatex and/or teTeX do not have any provisions to handle UTF-8 encoded XML files automagically. This may be the point where my problems started. Dunno about teTeX, but dblatex is fine with UTF-8--we use it that way exclusively, and then use XeLaTeX (a Unicode-aware version of LaTeX) to process the resulting file. I'm currently using two non-Unicode fonts that still have all required glyphs. It required a bit of testing though, but many fonts actually have a full set of greek characters and those few symbols that my document uses. If you're using non-Unicode fonts, then you'll need LaTeX rather than XeLaTeX. I'm not sure how (or whether) dblatex handles the conversion in that case--it wouldn't be something a standard encoding converter could handle, because you'd have to convert the non-ASCII (or at least non-ISO) characters into some kind of LaTeX commands, I imagine. I've never tried that. -- Mike Maxwell maxw...@umiacs.umd.edu My definition of an interesting universe is one that has the capacity to study itself. --Stephen Eastmond - 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] acknowledgements
http://www.docbook.org/tdg51/en/html/acknowledgements.html Parents These elements containacknowledgements http://www.docbook.org/tdg51/en/html/acknowledgements.html:article http://www.docbook.org/tdg51/en/html/article.html,book http://www.docbook.org/tdg51/en/html/book.html,module http://www.docbook.org/tdg51/en/html/container.module.html (db.container.module),part http://www.docbook.org/tdg51/en/html/part.html,resource http://www.docbook.org/tdg51/en/html/container.resource.html (db.container.resource). In file block.xsl I see xsl:template match=d:ackno|d:acknowledgements[parent::d:article] fo:block xsl:use-attribute-sets=normal.para.spacing xsl:call-template name=anchor/ xsl:apply-templates/ /fo:block /xsl:template Yet the element, in a book, isn't reported as an unknown element? In components.xsl I see xsl:template match=d:acknowledgements/xsl:template xsl:template match=d:acknowledgements/d:info/xsl:template xsl:template match=d:acknowledgements/d:title/xsl:template xsl:template match=d:acknowledgements/d:titleabbrev/xsl:template xsl:template match=d:acknowledgements/d:subtitle/xsl:template So it would appear that this element in a book is not processed? Is that correct? regards 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] olinking to varlistentry with indexterm inside term
Hi, Let's consider the following XML fragment: varlistentry xml:id=border-color termborder-color/term listitem paraSpecifies the color of all four borders of an element./para /listitem /varlistentry When I use olink targetptr=border-color/, then the link to the varlistentry is created properly. Now, if there is an indexterm element like this: varlistentry xml:id=border-color term indexterm xml:id=id8856773342938128 primarythemes/primary secondaryborder style properties/secondary tertiaryborder-color/tertiary /indextermborder-color/term listitem paraSpecifies the color of all four borders of an element./para /listitem /varlistentry then the same olink targetptr=border-color/ does not generate a link, even though it properly outputs the label, i.e. border-color text. Any ideas what's wrong with my docbook page? Robert - 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] acknowledgements
Hi Dave, In FO output, acknowledgements is not a block, it is a page-sequence. The template for book in division.xsl (in 1.76.1) has this: xsl:apply-templates select=acknowledgements mode=acknowledgements/ and component.xsl as: xsl:template match=acknowledgements mode=acknowledgements to generate the page sequence. It works for me. Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: davep da...@dpawson.co.uk To: Docbook-apps docbook-apps@lists.oasis-open.org Sent: Monday, August 01, 2011 6:51 AM Subject: [docbook-apps] acknowledgements http://www.docbook.org/tdg51/en/html/acknowledgements.html Parents These elements containacknowledgements http://www.docbook.org/tdg51/en/html/acknowledgements.html:article http://www.docbook.org/tdg51/en/html/article.html,book http://www.docbook.org/tdg51/en/html/book.html,module http://www.docbook.org/tdg51/en/html/container.module.html (db.container.module),part http://www.docbook.org/tdg51/en/html/part.html,resource http://www.docbook.org/tdg51/en/html/container.resource.html (db.container.resource). In file block.xsl I see xsl:template match=d:ackno|d:acknowledgements[parent::d:article] fo:block xsl:use-attribute-sets=normal.para.spacing xsl:call-template name=anchor/ xsl:apply-templates/ /fo:block /xsl:template Yet the element, in a book, isn't reported as an unknown element? In components.xsl I see xsl:template match=d:acknowledgements/xsl:template xsl:template match=d:acknowledgements/d:info/xsl:template xsl:template match=d:acknowledgements/d:title/xsl:template xsl:template match=d:acknowledgements/d:titleabbrev/xsl:template xsl:template match=d:acknowledgements/d:subtitle/xsl:template So it would appear that this element in a book is not processed? Is that correct? regards 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] acknowledgements
On 08/01/2011 05:51 PM, Bob Stayton wrote: Hi Dave, In FO output, acknowledgements is not a block, it is a page-sequence. The template for book in division.xsl (in 1.76.1) has this: xsl:apply-templates select=acknowledgements mode=acknowledgements/ and component.xsl as: xsl:template match=acknowledgements mode=acknowledgements to generate the page sequence. It works for me. Yes. Thanks Bob. 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] docbook to word
Lwam, I have only used this stylesheet a couple of times, on very simple files, so I'm far from an expert. Here is what I know, and I'm sure others will chime in with additional information or corrections if I've got it wrong. dbk2wordml.xsl is in a directory called roundtrip in the stylesheet distribution. There are other files in that directory that the stylesheet refers to, so make sure you have the entire directory. Here is the command line I'd use with xsltproc to convert a docbook file called input.xml to an output wordml file called output.xml. The shell variable $roundtrip should contain the path to the roundtrip directory in the distribution: xsltproc -o output.xml --stringparam wordml.template $roundtrip/template.xml $roundtrip/dbk2wordml.xsl input.xml $roundtrip/template.xml is supplied in the roundtrip directory. I don't use Word most of the time, but I am able to open output files from this transform in Open Office, so I suspect you'll be able to do the same with Word. Hope that helps. Best Regards, Dick Hamilton --- XML Press XML for Technical Communicators http://xmlpress.net hamil...@xmlpress.net On Aug 1, 2011, at 3:30 AM, Lwam Berhane wrote: Hey guys! I should convert docbook 5 to word. Now I only used to convert with fop 1.0 to html and pdf. I founde the stylesheet dbk2wordml.xsl. How do I handle it? which converter do I need? which customizations? Kind regards -- Gruß Lwam Berhane punkt.de GmbH TYPO3-Internet-Dienstleistungen-Beratung Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 76133 Karlsruhe i...@punkt.dehttp://punkt.de/ AG Mannheim 108285 Gf: Jürgen Egeling - 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] docbook to word
Hello Lwam, I should convert docbook 5 to word what I am missing here is a purpose of that conversion. Please elaborate it a bit. I suspect some 'better editing' reasons what is IMHO against the superb 'single source' concept you have just got with docbook. Btw, when I tried it in the past, I got the best results with db - html (+css) - MS Word html import. Regards, Jan - 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] olinking to varlistentry with indexterm inside term
Hi, It works for me in PDF output. Does your XML file validate? You didn't mention what kind of output you are generating. Bob Stayton Sagehill Enterprises b...@sagehill.net - Original Message - From: Robert Pasternak rp.i...@gmail.com To: docbook-apps@lists.oasis-open.org Sent: Monday, August 01, 2011 7:13 AM Subject: [docbook-apps] olinking to varlistentry with indexterm inside term Hi, Let's consider the following XML fragment: varlistentry xml:id=border-color termborder-color/term listitem paraSpecifies the color of all four borders of an element./para /listitem /varlistentry When I use olink targetptr=border-color/, then the link to the varlistentry is created properly. Now, if there is an indexterm element like this: varlistentry xml:id=border-color term indexterm xml:id=id8856773342938128 primarythemes/primary secondaryborder style properties/secondary tertiaryborder-color/tertiary /indextermborder-color/term listitem paraSpecifies the color of all four borders of an element./para /listitem /varlistentry then the same olink targetptr=border-color/ does not generate a link, even though it properly outputs the label, i.e. border-color text. Any ideas what's wrong with my docbook page? Robert - 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] Odd column resizing issue
| -Original Message- | From: Bill Burns | | I have been working on retrofitting | the webhelpindexer to work with an older set of stylesheets | (the HTML XSLT from v1.36). I've been eliminating little | XHTML errors here and there, but this last one has me stumped. | | I moved table.xsl to my customization layer folder and | added the XHTML namespace declaration to eliminate the | delimiter problems I was encountering. However, an odd thing | happened with the calculations for my col widths. [...] | When I'm producing plain old HTML, the result is | | col xmlns= width=20%col xmlns= width=40%col | xmlns= width=40% | | However, when I add the XHTML namespace, I get this result: | | col width=1*/colcol width=2*/colcol width=2*/col I'm sorry, but it is a little hard to understand what you are doing. May I ask why you need to retrofit webhelpindexer to work with a very old version of DocBook-XSL? I don't know how to reproduce the table columns problem. You mention the adjustColumnWidth extension function from docbook.py in your follow-up post, so I presume that you use Python to do the transformation. Is this right? Mauritz - 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] XSL-FO size of embedded fonts?
Hello, I'm weighing the value of embedding a font vs. sticking with the defaults in PDF, and am not sure whether to be surprised at how much embedding a font increases the size of small files. The font families are DejaVu TrueType. I am not using encoding-mode=single-byte in the font metrics. xsl:param name=body.font.familyDejaVuSerif/xsl:param xsl:param name=dingbat.font.familyDejaVuSerif/xsl:param xsl:param name=monospace.font.familyDejaVuSansMono/xsl:param xsl:param name=sans.font.familyDejaVuSans/xsl:param xsl:param name=title.font.familyDejaVuSans/xsl:param True, the entire size of all of DejaVu on disk when unpacked is 9.7 MB, though the zipped download is half of that. With those parameters set, short draft release notes, for example, at http://opendj.forgerock.org/doc/OpenDJ-Release-Notes.pdf come out to about 940 KB on disk. Only English text in there, nothing fancy. When those parameters are commented out, the same release notes take up 56 KB on disk. Is that size increase to be expected? Is there some other parameter I should set to reduce the size of the resulting PDF? I'm using docbkx-tools 2.0.13 to process the content. So the underlying XSL is version 1.76.1. Thanks for your time and your advice. Regards, Mark - 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] Odd column resizing issue
I'm sorry, but it is a little hard to understand what you are doing. May I ask why you need to retrofit webhelpindexer to work with a very old version of DocBook-XSL? I don't know how to reproduce the table columns problem. You mention the adjustColumnWidth extension function from docbook.py in your follow-up post, so I presume that you use Python to do the transformation. Is this right? The client I'm working for developed their own flavor of Web Help based on an older DocBook XSL version and had a different mechanism for search. Trying to bring it up to date would've been nontrivial, so I ported the webhelpindexer into their transform environment instead. I'm getting Java exceptions because the output isn't fully XHTML compliant. I'm trying to eliminate the Java exceptions during indexing by adding the XHTML namespace to the stylesheets and generating XHTML compliant content. When I do this to table.xsl, the adjustColumnWidth extension function fails and passes through the values rather than converting them to percentages. As it stands, I can leave table.xsl alone and produce plain HTML. Everything indexes okay. I just get those ugly Java exceptions. I'd rather have a clean transform. Bill Burns Verbum Communications, Inc. +1.208.336.6081 bbu...@verbumcomm.com http://www.verbumcomm.com - 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] Odd column resizing issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Bill, I assume you are able to add steps to their build process if you're adding the indexing step, so you could run their html output through some version of tidy [1] to turn it into xhtml before running the webhelp indexer on it. That way you wouldn't have to touch their ancient xslts. Regards, David [1] http://en.wikipedia.org/wiki/HTML_Tidy On 08/01/2011 06:12 PM, Bill Burns wrote: I'm sorry, but it is a little hard to understand what you are doing. May I ask why you need to retrofit webhelpindexer to work with a very old version of DocBook-XSL? I don't know how to reproduce the table columns problem. You mention the adjustColumnWidth extension function from docbook.py in your follow-up post, so I presume that you use Python to do the transformation. Is this right? The client I'm working for developed their own flavor of Web Help based on an older DocBook XSL version and had a different mechanism for search. Trying to bring it up to date would've been nontrivial, so I ported the webhelpindexer into their transform environment instead. I'm getting Java exceptions because the output isn't fully XHTML compliant. I'm trying to eliminate the Java exceptions during indexing by adding the XHTML namespace to the stylesheets and generating XHTML compliant content. When I do this to table.xsl, the adjustColumnWidth extension function fails and passes through the values rather than converting them to percentages. As it stands, I can leave table.xsl alone and produce plain HTML. Everything indexes okay. I just get those ugly Java exceptions. I'd rather have a clean transform. Bill Burns Verbum Communications, Inc. +1.208.336.6081 bbu...@verbumcomm.com http://www.verbumcomm.com - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJONzbqAAoJEMHeSXG7afUhhv8IAJidbX1soOddpluF2vFH5dRr tNAomY72+eSQ3EsZyPUU/mfSZgcLTUs5CzO2AKg08kAOdsLzuxePYrvfGxPv28Ta Cp5bowjQIn51gLoU6hjLwTOQs/qLVRCOhhE2f2eJBl4y5Q8fP6qBt1bu7zl+zV5y JyFo3GkWOUt0DvXW70i+9vSJ29d34bEtCPv/69OBU0X0jLPZMGznGK/XRm1FDBOO 443ocISRcEeqkJb36m3GLp9yqwy7SvOfpNNj0g022/NQjo6uNPER9JJUYqunsREX sOryn07noCTgSzHMLvAI0OHwNsfnYY1spRcQ+n6QkA63dWc4eo/Y/pKYA835Cpo= =FSvw -END PGP SIGNATURE- - 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] Odd column resizing issue
Excellent, David. I will look at that option. I managed to get rid of all the other old code, but this little enigma had me baffled. Bill Burns Verbum Communications, Inc. +1.208.336.6081 bbu...@verbumcomm.com http://www.verbumcomm.com -Original Message- From: David Cramer [mailto:da...@thingbag.net] Sent: Monday, August 01, 2011 5:30 PM To: docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] Odd column resizing issue -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Bill, I assume you are able to add steps to their build process if you're adding the indexing step, so you could run their html output through some version of tidy [1] to turn it into xhtml before running the webhelp indexer on it. That way you wouldn't have to touch their ancient xslts. Regards, David [1] http://en.wikipedia.org/wiki/HTML_Tidy On 08/01/2011 06:12 PM, Bill Burns wrote: I'm sorry, but it is a little hard to understand what you are doing. May I ask why you need to retrofit webhelpindexer to work with a very old version of DocBook-XSL? I don't know how to reproduce the table columns problem. You mention the adjustColumnWidth extension function from docbook.py in your follow-up post, so I presume that you use Python to do the transformation. Is this right? The client I'm working for developed their own flavor of Web Help based on an older DocBook XSL version and had a different mechanism for search. Trying to bring it up to date would've been nontrivial, so I ported the webhelpindexer into their transform environment instead. I'm getting Java exceptions because the output isn't fully XHTML compliant. I'm trying to eliminate the Java exceptions during indexing by adding the XHTML namespace to the stylesheets and generating XHTML compliant content. When I do this to table.xsl, the adjustColumnWidth extension function fails and passes through the values rather than converting them to percentages. As it stands, I can leave table.xsl alone and produce plain HTML. Everything indexes okay. I just get those ugly Java exceptions. I'd rather have a clean transform. Bill Burns Verbum Communications, Inc. +1.208.336.6081 bbu...@verbumcomm.com http://www.verbumcomm.com - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJONzbqAAoJEMHeSXG7afUhhv8IAJidbX1soOddpluF2vFH5dRr tNAomY72+eSQ3EsZyPUU/mfSZgcLTUs5CzO2AKg08kAOdsLzuxePYrvfGxPv28Ta Cp5bowjQIn51gLoU6hjLwTOQs/qLVRCOhhE2f2eJBl4y5Q8fP6qBt1bu7zl+zV5y JyFo3GkWOUt0DvXW70i+9vSJ29d34bEtCPv/69OBU0X0jLPZMGznGK/XRm1FDBOO 443ocISRcEeqkJb36m3GLp9yqwy7SvOfpNNj0g022/NQjo6uNPER9JJUYqunsREX sOryn07noCTgSzHMLvAI0OHwNsfnYY1spRcQ+n6QkA63dWc4eo/Y/pKYA835Cpo= =FSvw -END PGP SIGNATURE- - 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
