Re: [docbook-apps] multi-column index does not work for DB5/1.73.2
Title: Re: [docbook-apps] multi-column index does not work for DB Bob Yes, the multicolumn index works fine for a book. I understand the article problem and can live with it. Your XEP output I can't reproduce, I never get index page ranges collapsed, with book or article. See results below. I have up-graded to XEP 4.10, the latest free personal edition, and get the same result. I can't see how it could make any difference, but I'm using MacOS 10.3.9, Oxygen 8.2, Saxon 6.5.5, docbook/5.0/docbook-xsl-ns-1.73.2/fo/docbook.xsl and java dainzu:~ ron$ java -version java version 1.4.2_12 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-270) Java HotSpot(TM) Client VM (build 1.4.2-70, mixed mode) Ron Results: Index A athirteen, 1, 3 atwentyone, 1, 2, 3 B bfourteen, 1, 3 btwentytwo, 1, 2, 3 C cfifteen, 1, 3 ctwentythree, 1, 2, 3 XSL file: ?xml version=1.0 encoding=utf-8? xsl:stylesheet version = 1.0 xmlns:d = http://docbook.org/ns/docbook xmlns:xsl = http://www.w3.org/1999/XSL/Transform xmlns:fo = http://www.w3.org/1999/XSL/Format xmlns:l = http://docbook.sourceforge.net/xmlns/l10n/1.0 xsl:import href =/Applications/Utilities/oxygen/8.2/oxygen/frameworks/docbook/5.0/docbook-xsl-ns-1.73.2/fo/docbook.xsl/ xsl:param name=double.sided select=1 / xsl:param name=xep.extensions select =1/ xsl:param name=column.count.index select =3/ xsl:attribute-set name=index.entry.properties xsl:attribute name=font-size8pt/xsl:attribute xsl:attribute name=line-height12pt/xsl:attribute /xsl:attribute-set xsl:attribute-set name=index.page.number.properties xsl:attribute name=colorblue/xsl:attribute /xsl:attribute-set /xsl:stylesheet XML file: ?xml version=1.0 encoding=UTF-8 ? !DOCTYPE book book xml:id=LL xmlns=http://docbook.org/ns/docbook version=5.0 xml:lang=EN infotitleTitle of book/title/info chaptertitleTitle of chapter/title section xml:id=LL_first xml:lang=EN infotitleTitle of first section/title/info literallayout indextermprimaryone/primary/indexterm1 indextermprimarytwo/primary/indexterm2 indextermprimarythree/primary/indexterm3 indextermprimaryfour/primary/indexterm4 indextermprimaryfive/primary/indexterm5 indextermprimarysix/primary/indexterm6 indextermprimaryseven/primary/indexterm7 indextermprimaryeight/primary/indexterm8 indextermprimarynine/primary/indexterm9 indextermprimaryten/primary/indexterm10 indextermprimaryeleven/primary/indexterm11 indextermprimarytwelve/primary/indexterm12 indextermprimarythirteen/primary/indexterm13 indextermprimaryfourteen/primary/indexterm14 indextermprimaryfifteen/primary/indexterm15 indextermprimarysixteen/primary/indexterm16 indextermprimaryseventeen/primary/indexterm17 indextermprimaryeighteen/primary/indexterm18 indextermprimarynineteen/primary/indexterm19 indextermprimarytwenty/primary/indexterm20 indextermprimaryatwentyone/primary/indexterm21 indextermprimarybtwentytwo/primary/indexterm22 indextermprimaryctwentythree/primary/indexterm23 indextermprimarydtwentyfour/primary/indexterm24 indextermprimarygtwentyfive/primary/indexterm25 indextermprimaryhtwentysix/primary/indexterm26 indextermprimaryitwentyseven/primary/indexterm27 indextermprimaryjtwentyeight/primary/indexterm28 indextermprimaryktwentynine/primary/indexterm29 indextermprimaryltwentythirty/primary/indexterm30 /literallayout literallayout indextermprimarymone/primary/indexterm1 indextermprimaryntwo/primary/indexterm2 indextermprimaryothree/primary/indexterm3 indextermprimarypfour/primary/indexterm4 indextermprimaryqfive/primary/indexterm5 indextermprimaryrsix/primary/indexterm6 indextermprimaryuseven/primary/indexterm7 indextermprimaryveight/primary/indexterm8 indextermprimarywnine/primary/indexterm9 indextermprimaryxten/primary/indexterm10 indextermprimaryyeleven/primary/indexterm11 indextermprimaryztwelve/primary/indexterm12 indextermprimaryathirteen/primary/indexterm13 indextermprimarybfourteen/primary/indexterm14 indextermprimarycfifteen/primary/indexterm15 indextermprimarydsixteen/primary/indexterm16 indextermprimarygseventeen/primary/indexterm17 indextermprimaryheighteen/primary/indexterm18 indextermprimaryinineteen/primary/indexterm19 indextermprimaryjtwenty/primary/indexterm20 indextermprimaryatwentyone/primary/indexterm21 indextermprimarybtwentytwo/primary/indexterm22 indextermprimaryctwentythree/primary/indexterm23 indextermprimarydtwentyfour/primary/indexterm24 indextermprimarygtwentyfive/primary/indexterm25 indextermprimaryhtwentysix/primary/indexterm26 indextermprimaryitwentyseven/primary/indexterm27 indextermprimaryjtwentyeight/primary/indexterm28 indextermprimaryktwentynine/primary/indexterm29 indextermprimaryltwentythirty/primary/indexterm30 /literallayout paraetc/para literallayout indextermprimaryone/primary/indexterm1 indextermprimarytwo/primary/indexterm2 indextermprimarythree/primary/indexterm3 indextermprimaryfour/primary/indexterm4 indextermprimaryfive/primary/indexterm5
[docbook-apps] MathML and graphic images in single source
Hello, I would like to have my MathML equations show up in the PDF and the graphic images of the equations show up in the HTML renderings. Would I use the mediaobject or equation or something else? Right now I am using just the equation tag and then xinclude the MathML source. This works well for the PDF but it doesn't seem to validate under Oxygen 8.3 - any clues on that? I want to expand the equations to add support for an HTML viewer that does not support the MathML, hence the graphics.Any help/thoughts would be appreciated. Thanks! Dean Nelson Sr. Software Engineer Enterprise Electronics Corp http://www.EECradar.com http://www.eecradar.com/ Too much of the world is run on the theory that you don't need road manners if you drive a five-ton truck - Cleon Lyles This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
Re: [docbook-apps] MathML and graphic images in single source
Hi Dean, On Montag, 22. Oktober 2007, Nelson, Dean wrote: I would like to have my MathML equations show up in the PDF and the graphic images of the equations show up in the HTML renderings. Would I use the mediaobject or equation or something else? I am not sure, but if I remember correctly, the stylesheets copies the MathML markup directly into the HTML code. However, for the HTML stylesheets, there is no automatism that converts MathML into, say, PNG. The browser has to support MathML markup. Back to your question: Both elements should work, actually it depends on the title. Generally, an equation has a title that is numbered. It appear also in the list of equations (usually at the beginning of a book). Normally, equations are just a wrapper for mediaobject(s). The element mediaobject holds just the skeleton of the references to your equations, be it for PDF or HTML. Actually it can hold an arbitrary number of imageobjects that points to a image source (see below). It can contain a caption but that is not numbered and doesn't appear in the list of equations. Just to clarify equation and mediaobject. Right now I am using just the equation tag and then xinclude the MathML source. This works well for the PDF but it doesn't seem to validate under Oxygen 8.3 - any clues on that? Do you use DocBook 4.x or DocBook 5? Either way, if you xinclude your MathML source, these elements are unknown in DocBook. You have to customize the DTD or the RELAX NG to allow MathML markup inside equation. See http://www.docbook.org/docs/howto/#faq-customization-mathml for DocBook5. I have no link ATM for customization for DocBook4. I want to expand the equations to add support for an HTML viewer that does not support the MathML, hence the graphics. Any help/thoughts would be appreciated. There is also another possibility. You could just omit the MathML markup and reference to the rendered graphic(s): mediabobject imageobject role=fo !-- For high quality, use a supported vector format like PDF, EPS, ... -- imagedata fileref=equation.pdf/ /imageobject imageobject role=html !-- Any pixel format like JPEG, PNG, GIF, ... should work for a browser -- imagedata fileref=equation.png/ /imageobject /mediaobject You have to render your formula with a respective tool first, that could be OpenOffice.org or LaTeX. The advantage is you can use the official DocBook schema without any customization. The drawback is it's not a direkt way, you need an additional step. Hope that helps, Tom -- Thomas Schraitle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [docbook-apps] MathML and graphic images in single source
Thanks for the reply Tom, I'm using DocBook 4.5 and have been using graphics for the equations. This is quick and easy (usually), but doesn't scale real well. The higher the resolution of the graphics, the bigger the file. Since I have a great deal of these, I lower the resolution as far as I can get away with. As a result, they are not really sharp and crisp like they are when rendered with MathML in the Jeuclid FOP plugin. I want the equations to show up in the equations TOC and be numbered and be able to be referenced, but I also want to treat them differently (use graphics) if the output is HTML. Yet I'm unsure of how to go about that. I wonder if the ALT tag could be used to render Mathml? Regards, Dean Nelson Enterprise Electronics Corp -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 4:25 PM To: docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] MathML and graphic images in single source Hi Dean, On Montag, 22. Oktober 2007, Nelson, Dean wrote: I would like to have my MathML equations show up in the PDF and the graphic images of the equations show up in the HTML renderings. Would I use the mediaobject or equation or something else? I am not sure, but if I remember correctly, the stylesheets copies the MathML markup directly into the HTML code. However, for the HTML stylesheets, there is no automatism that converts MathML into, say, PNG. The browser has to support MathML markup. Back to your question: Both elements should work, actually it depends on the title. Generally, an equation has a title that is numbered. It appear also in the list of equations (usually at the beginning of a book). Normally, equations are just a wrapper for mediaobject(s). The element mediaobject holds just the skeleton of the references to your equations, be it for PDF or HTML. Actually it can hold an arbitrary number of imageobjects that points to a image source (see below). It can contain a caption but that is not numbered and doesn't appear in the list of equations. Just to clarify equation and mediaobject. Right now I am using just the equation tag and then xinclude the MathML source. This works well for the PDF but it doesn't seem to validate under Oxygen 8.3 - any clues on that? Do you use DocBook 4.x or DocBook 5? Either way, if you xinclude your MathML source, these elements are unknown in DocBook. You have to customize the DTD or the RELAX NG to allow MathML markup inside equation. See http://www.docbook.org/docs/howto/#faq-customization-mathml for DocBook5. I have no link ATM for customization for DocBook4. I want to expand the equations to add support for an HTML viewer that does not support the MathML, hence the graphics. Any help/thoughts would be appreciated. There is also another possibility. You could just omit the MathML markup and reference to the rendered graphic(s): mediabobject imageobject role=fo !-- For high quality, use a supported vector format like PDF, EPS, ... -- imagedata fileref=equation.pdf/ /imageobject imageobject role=html !-- Any pixel format like JPEG, PNG, GIF, ... should work for a browser -- imagedata fileref=equation.png/ /imageobject /mediaobject You have to render your formula with a respective tool first, that could be OpenOffice.org or LaTeX. The advantage is you can use the official DocBook schema without any customization. The drawback is it's not a direkt way, you need an additional step. Hope that helps, Tom -- Thomas Schraitle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
