Re: [docbook-apps] Re: Font for the info part different than for the rest and the colophon

On Jan 29, 2019, at 9:23 AM, Bob Stayton wrote: > > The generated copyright symbol uses a template named 'dingbat' in fo/fo.xsl. > It sets the font-family to the $dingbat.fontset which is defined in > fo/pagesetup.xsl. I remember a time when such hacks were common and reasonable, but is it

Re: [docbook] Tinkering with the DNS for docbook.org

On Feb 26, 2018, at 4:27 PM, Norman Walsh wrote: > > I don’t want to change the process for publishing to cdn.docbook.org > dramatically. That limits the options. Near as I can tell, the only > way to do this and stay on github.io is with some kind of proxy via > cloudfare.

Re: [docbook-apps] Enable FOP's PCL duplexing feature with DocBook XSL stylesheet customization?

On Sep 8, 2017, at 1:33 PM, Jirka Kosek <ji...@kosek.cz> wrote: > > On 7.9.2017 17:46, Warren Young wrote: >> Unfortunately, grepping the DBX FO XSL files in the version of the >> stylesheets packaged for my OS turns up no instances of “duplex”. > > That's because

[docbook-apps] Enable FOP's PCL duplexing feature with DocBook XSL stylesheet customization?

I’ve just learned about a feature of FOP which allows you to enable duplex printing when generating PCL output from FO input: https://xmlgraphics.apache.org/fop/2.2/output.html#pcl-duplex-mode Unfortunately, grepping the DBX FO XSL files in the version of the stylesheets packaged for my OS

Re: [docbook-apps] headers in html and webhelp output of

On Jul 28, 2016, at 1:48 AM, Fekete, Róbert wrote: > > We don't use numbered sect tags, only s So use , , etc, and you’ll get , , etc. in your output. > Our web team notified us that having multiple h1 tags in the html is not > really SEO-friendly, that's why I'd

[docbook] Re: [docbook-apps] Tools to make DocBook easier

On Sep 14, 2015, at 4:04 PM, Warren Block wrote: > > What tools are there to make working with DocBook easier? I wrote a > lint-like proofreading tool There’s already xmllint, which if given a DocBook DTD, will validate the well-formedness of your document, not just in

Re: [docbook] [docbook-apps] Tools to make DocBook easier

On Sep 14, 2015, at 5:35 PM, Warren Block <wbl...@wonkity.com> wrote: > > On Mon, 14 Sep 2015, Warren Young wrote: > >> On Sep 14, 2015, at 4:04 PM, Warren Block <wbl...@wonkity.com> wrote: >>> >>> What tools are there to make working with DocBook e

Re: [docbook] LaTeX math inside docbook, on-the-fly MathML conversion?

On Jan 29, 2015, at 2:20 PM, Stefan Seefeld ste...@seefeld.name wrote: On 29/01/15 03:25 PM, Warren Young wrote: ...most XSL-FO processors don’t support MathML, either. Last time I checked, only Antenna House did. I have been using FOP with the jeuclid plugin for a number of years

[docbook-apps] Re: [docbook] To Namespace or Not To Namespace

On 10/3/2014 10:21, Steve Cuzner wrote: I’m investigating porting our 4.x docbook to 5.x. For our custom elements, I’m considering adding them to our own namespace so that it is more obvious which elements are docbook and which are custom to our extension. While technically not necessary given

Re: [docbook-apps] Workaround for xinclude path bug, fixed in xsltproc 1.1.27?

On 9/15/2014 14:16, Mario Klebsch wrote: Have you thought about using an XML catalog file? The solution I settled on is to disable the user manual build rule when xsltproc 1.1.27 and build root != source root. So, you can use a recent xsltproc in all conditions, but you can still get the

Re: [docbook-apps] Workaround for xinclude path bug, fixed in xsltproc 1.1.27?

Accidentally took this off-list: On 9/11/2014 14:49, Bob Stayton wrote: There is nothing the XSL process can do to correct this problem, as the resolved file does not have the information necessary to locate qux.txt. Though I posted this to the DocBook list, I wasn't expecting a fix to the

[docbook-apps] Workaround for xinclude path bug, fixed in xsltproc 1.1.27?

Take these three files: foo.dbx: ?xml version=1.0 encoding='UTF-8'? !DOCTYPE article PUBLIC -//OASIS//DTD DocBook V4.2//EN http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd; article titleTest/title xi:include href=bar.dbx

Re: [docbook-apps] O'Reilly blog...

On 2/1/2013 11:31, davep wrote: http://techblog.safaribooksonline.com/2013/02/01/the-unxmling-of-digital-books/ It's an interesting article, and the issues it brings up are real. DocBook XML is fine when it fits the shape of the hole your problem has made in the world. The current

Re: [docbook-apps] WYSIWYG Editor for docbook

On 8/12/2012 5:10 PM, Paul Taylor wrote: On 12/08/2012 23:41, Richard Hamilton wrote: There are a bunch of very good visual editors out there that will handle DocBook. The one I know best is Oxygen (http://www.oxygenxml.com/), which works very well with DocBook. Goodness, this product is

Re: [docbook-apps] WYSIWYG Editor for docbook

On 8/12/2012 4:41 PM, Richard Hamilton wrote: There are a bunch of very good visual editors out there that will handle DocBook. The one I know best is Oxygen (http://www.oxygenxml.com/), which works very well with DocBook. The last time I tried opening one of my DocBook manuals with it

Re: [docbook] HOW TO: format formula in docbook 5

On 6/7/2010 9:43 AM, Rowland, Larry wrote: or simply use a PNG of the expression That's good if your output is HTML or something else where bitmap images are appropriate. If your output is PDF or PostScript, better to use a vector graphics form of the equation: PS, PDF, SVG... whatever

Re: [docbook-apps] How to add a Flash swf to a docbook xslt

[EMAIL PROTECTED] wrote: I don't think it is different than an svg as it is basically a vector graphic If we were designing HTML all over again today, maybe that's how we'd do it, but the reality of the situation is that it takes takes about 100 lines of HTML and JavaScript code to reliably

Re: [docbook-apps] How to add a Flash swf to a docbook xslt

Paul Norton wrote: a simplified approach which includes the embed tag as the alternative content within the object tag. That seems likely to work. Due to the apparent age of the document, I'd test it in all the browsers I want to support to be sure, though. It doesn't seem to have the

Re: [docbook] Bold and italic type for mathematics

Stephen Taylor wrote: Mathematicians commonly use bold and italic type to distinguish single-character terms. Eh, I see more plain italics than bold-italics. Does DocBook have suitable elements? No, but they're not necessary. DocBook has tags for declaring mathematics:

Re: [docbook-apps] DocBook 5.x - the difference between mediaobject and inlinemediaobject

John Brown wrote: Isn't everything inline? No. Let us say our media object is FOO. We may insert FOO inline. Or, we may reference FOO as a block-level object separately. As with everything in DocBook, this presentation issue isn't specified by DocBook itself. But, the two

Re: [docbook-apps] Re: DocBook 5.x - the difference between mediaobject and inlinemediaobject

John Brown wrote: I understand the concept fully. Instead of just having bold or something similar, we are forced to type emphasis role=strong. Either you do not in fact understand the concept, or you're being willfully facetious. The standard DocBook stylesheets will bold any text

[docbook-apps] Re: [docbook] xrefs in modular books

Johnson, Eric wrote: What is the recommended way to do cross-references in modular DocBook books? xref or olink? DocBook defines exactly what xref means. You can rely on different tool chains to do the same thing with it. As I read this:

Re: [docbook-apps] Website build/deploy

Dave Pawson wrote: I'm assuming your .dbx is a docbook XML file? Yes. Change all the dbx strings to whatever extension you use, if you don't like dbx. I'm reluctant to even propose cygwin installation. Here's how you sell it to them: Install Cygwin on one of the machines in their

Re: [docbook-apps] Website build/deploy

Warren Young wrote: Again, rsync is a favourite here on Linux systems. Not available to me on Windows. It's part of the Cygwin distribution. Not installed by default, but you By the way, I just realized another reason to use Cygwin: they've also got prepackaged DocBook stuff, including

Re: [docbook-apps] Suppressing book title page in fo output?

Antti Karanta wrote: BTW, what are the two other pages besides the title page? The one with the title in a smaller font than the actual title page is called the verso. The word comes from the same root that gives us reverse, as it refers to the back side of the title page. It's meant

Re: [docbook-apps] Website build/deploy

Dave Pawson wrote: Some desktop icon which runs a script to build the entire site, stop on errors, then use a command line ftp command to deploy to the host. Here's how a Unix programmer (me) does it: I use 'make' to build the pages on my web sites from some source. (I use various template

Re: [docbook-apps] DocBook editor

Lou Iorio wrote: It also seems to me a bad idea to try to use a WYSIWYG editor for any markup language. It's a bad idea to use general purpose tools for something restrictive like DocBook, but it doesn't mean you can't make tools that do work well. Take a look at LyX: http://www.lyx.org/

Re: [docbook-apps] DocBook editor

Lou Iorio wrote: Go to Preferences-Editors-File Associations and add *.dbk. with the same associated editors as *.xml. I think there's one more Preferences setting to deal with, but I don't remember what it is. Thanks. You also have to go into the Content Types area and tell it that *.dbx

Re: [docbook-apps] DocBook editor

Lou Iorio wrote: I use a Mac, not Windows, so I start Eclipse and then open the file I want to edit. Actually, there's no difference between the two platforms in this regard. OS X also has file associations, and when using them, Eclipse launches but doesn't open the file when you

Re: [docbook-apps] Page title formatting error with 1.69.1 stylesheets

Warren Young wrote: Further testing implicates either xsltproc or the stylesheets. For the archives, it's the stylesheets. Thanks to help off-list from Bob Stayton, I found that the Red Hat packages (which CentOS uses verbatim, by policy) have been horribly hacked up relative to the stock

Re: [docbook-apps] Page title formatting error with 1.69.1 stylesheets

Further testing implicates either xsltproc or the stylesheets. I use xsltproc to get from DBX to FO, and then FOP to get from FO to PDF, because I use XIncludes in this document. If I make FOP do all the work, the page title are formatted correctly, although of course the XIncludes break.

[docbook-apps] Page title formatting error with 1.69.1 stylesheets

I'm using the DocBook style sheets to format a user manual for MySQL++. (http://tangentsoft.net/mysql++) For the previous release of MySQL++, I prepared the manual on a different machine which came with v1.65.1 of the style sheets, and it worked correctly. Since moving to a newer machine

Re: [docbook] should I use section or sect1, sect2, sect3 etc?

Rock Lobster wrote: I'm somehow confused on whether I should use nested section tags, or the predefined sect1 to sect5. Are there any benefits in using the latter? Are there any reasons why one way should be avoided in certain situations? DocBook is all about semantic markup. If your

Re: [docbook] should I use section or sect1, sect2, sect3 etc?

Scott Hudson wrote: I usually recommend using nested section. It makes it easier to reuse content in different contexts if you need to. That lack of context is also a disadvantage. It means you can't look at a section of the document and immediately tell where it fits in logically with the