[docbook-apps] Size?

[Dave Pawson]

I write a journal. In pen and ink.
Read it into text, slot it into docbook XML.
Just passed 1400 A4 pages. 639486 words.

I've decided docbook works well for me
;-)

happy new year folks.

regards


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] AI ... db metadata 'extras'?

[Dave Pawson]

Yes thanks - how much more can you add to oXygen :-)

regards

On Fri, 27 Oct 2023 at 06:03, Radu Coravu  wrote:
>
> Hi Dave,
>
> Thanks for posting the link, I hope you enjoyed the live webinar!
>
> Regards,
>
> Radu
>
> Radu Coravu
> Oxygen XML Editor
>
> On 10/26/23 19:29, Dave Pawson wrote:
> > https://www.oxygenxml.com/events/2023/webinar_transforming_technical_content_creation_through_ai_powered_writing.html
> >
> > regards
>
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] AI ... db metadata 'extras'?

[Dave Pawson]

https://www.oxygenxml.com/events/2023/webinar_transforming_technical_content_creation_through_ai_powered_writing.html

regards
-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Fwd: Reminder: Oxygen AI Positron: Transforming Technical Content Creation through AI-Powered Writing starts in 1 Hour

[Dave Pawson]

AI and docbook?
>From Oxygen editor presentation... (in the world of AI)
Given a docbook marked up document: How to add (in metadata) 'what
questions does this document answer?


I'm hoping George will make the presentation available as a recording?
Some rather smart 'add ons' appropriate to docbook.

regards


-- Forwarded message -
From: George Bina 
Date: Wed, 25 Oct 2023 at 14:58
Subject: Reminder: Oxygen AI Positron: Transforming Technical Content
Creation through AI-Powered Writing starts in 1 Hour
To: 


Oxygen AI Positron: Transforming Technical Content Creation through
AI-Powered Writing

Wed, Oct 25, 2023 4:00 PM - 5:00 PM BST

This is a reminder that *"Oxygen AI Positron: Transforming Technical
Content Creation through AI-Powered Writing"* will begin in 1 Hour on:

Wed, Oct 25, 2023 4:00 PM - 5:00 PM BST

Please send your questions, comments and feedback to: supp...@oxygenxml.com

How to Join the Webinar

Wed, Oct 25, 2023 4:00 PM - 5:00 PM BST

Add to calendar: Outlook® Calendar
<https://global.gotowebinar.com/icsCalendar.tmpl?webinar=2838231371715065952=411600401=outlook>
| Google Calendar™
<https://global.gotowebinar.com/icsCalendar.tmpl?webinar=2838231371715065952=411600401=google>
| iCal®
<https://global.gotowebinar.com/icsCalendar.tmpl?webinar=2838231371715065952=411600401=ical>

1. Click the button to join the webinar at the specified time and date:
Join Webinar
<https://global.gotowebinar.com/join/2838231371715065952/411600401>

Note: This link should not be shared with others; it is unique to you.

Before joining, be sure to check system requirements
<https://link.gotowebinar.com/email-welcome?role=attendee=registrantReminderEmail=english>
to avoid any connection issues.

2. Choose one of the following audio options:

To use your computer's audio:

When the webinar begins, you will be connected to audio using your
computer's microphone and speakers (VoIP). A headset is recommended.

or

*To use your telephone:*

If you prefer to use your phone, you must select "Use Telephone" after
joining the webinar and call in using the numbers below.

Australia: +61 2 9091 7604

Access Code: 511-829-629
Audio PIN: Shown after joining the webinar
Calling from another country?
<https://attendee.gotowebinar.com/audio/2838231371715065952>

Webinar ID: 683-583-235

To Cancel this registration

If you can't attend this webinar, you may cancel your registration
<https://attendee.gotowebinar.com/cancel/2838231371715065952/4669605427189421661>
at any time.

This email was sent on behalf of the event organizer by GoTo Webinar. To
review the organizer's privacy policy, exercise any applicable privacy
rights, or stop receiving their communications, please contact the
organizer directly.

Stop GoTo Webinar emails
<https://attendee.gotowebinar.com/subscription.tmpl?organizer=2326079902498751749=glhGBImPR5eUCUVrLAVhnw%3D%3D=george%40oxygenxml.com=dave.pawson%40gmail.com=en_US>
. Report spam
<https://attendee.gotowebinar.com/reportSpam.tmpl?organizer=2326079902498751749=glhGBImPR5eUCUVrLAVhnw%3D%3D=dave.pawson%40gmail.com=683583235=Oxygen+AI+Positron%3A+Transforming+Technical+Conten...=george%40oxygenxml.com=en_US>

333 Summer Street . Boston, MA 02210 . Privacy Policy
<https://secure.logmein.com/home/en/policies/overview> . Anti-spam Policy
<https://www.goto.com/company/legal/anti-spam-policy> . www.goto.com/webinar
©2023 GoTo, Inc.


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

Re: [docbook-apps] fo, chapter headings corrupted

[Dave Pawson]

On Fri, 7 Jul 2023 at 10:28, Norm Tovey-Walsh  wrote:
>
> > font-family="ariesSCB,Symbol,ZapfDingbats">
> […]
> > All that shows in the PDF is
> >
> > 9.!
> >
> > I'm tending to look at a font missing problem, except for the two
> > 'present' characters.
>
> Looks like a missing font problem at first glance. If you don’t have
> “ariesSCB” then you’re only getting characters from Symbol and Zapf
> Dingbats.

Quite right Norm.
   Aries - correct
   aries - incorrect.

Thanks.

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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, chapter headings corrupted

[Dave Pawson]

Using xep.


chapter in fo is



Chapter 9. All at
sea!

All that shows in the PDF is

9.!


I'm tending to look at a font missing problem, except for the two
'present' characters.

Any other ideas please?

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] TOC placement in pdf

[Dave Pawson]

Can you use the  element to place it where you want?


HTH

On Tue, 21 Feb 2023 at 06:28, Richard Hamilton  wrote:
>
> Hello,
>
> The element I’ve used to put things before the toc is , which 
> allows a lot more elements than you might expect, including paragraphs and 
> tables.
>
> It is an abuse of the tag, (I’ve used it only for a dedication in our books), 
> but in a pinch, it might do what you need.
>
> I’m sure others on this list may have some good (probably better:) ideas, but 
> I’m not sure you can do what you want to do with any other element, unless 
> you modify the stylesheets.
>
> I hope that helps.
> Dick Hamilton
> ---
> XML Press
> XML for Technical Communicators
> http://xmlpress.net
> hamil...@xmlpress.net
>
>
>
> > On Feb 20, 2023, at 23:04, rohith R  wrote:
> >
> > Hi,
> >
> >
> > I'm using an article style docbook and convert it into pdf.
> >
> > The TOC is getting generated after the title page. I want it before the 
> > section but after the front matter. How can I accomplish  this?
> >
> > My article structure (docbook5):
> > - title page
> > - other stuff (text and couple of tables)
> > - multiple sections 
> >
> > I want the TOC placed after "other stuff" and before sections.
> >
> > How can I accomplish it?
> > At the moment they get generated after title page when generating pdf.
> >
> > Regards,
> > R
>
>
> -----
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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 xslTNG prerelease 2.0.7

[Dave Pawson]

On Mon, 6 Feb 2023 at 18:48, Tony Graham  wrote:
>
> On 06/02/2023 15:23, Thomas Schraitle wrote:
> ...
> > No localization exists for "" or "". Using default "en".
> > Error at xsl:text on line 169 column 19 of functions.xsl:
> >XTMM9000  Processing terminated by xsl:message at line 169 in
> > functions.xsl
>
> Do you have any 'xml:lang=""' in your document(s)?
>
> It looks like the function [1] can really only generate 'No localization
> exists for "" or "".' if '$gentext-language' is not set (not that I know
> how to set it) and there's an 'xml:lang=""' somewhere in your document.
>
> The 'terminate="yes"' on line 168 does rather contradict the message
> that processing will continue with the default language.

Which begs the question, where to set the default language, and should
it be reported as a bug if not set?
[Guess, $gentext-language will default to 'default language' - does
that make sense?]

HTH
-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] documentation

[Dave Pawson]

Apols to Bob, I thought this may be of use for other projects.

https://rachelandrew.co.uk/archives/2023/01/28/technical-writing-resources/

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Language support in XSL-FO Stylesheets

[Dave Pawson]

Frank, is your solution meeting all your needs (with the corrections
you've made?)

If so, perhaps put in a change request to docbook?

regards

On Thu, 23 Jun 2022 at 15:07, Frank Steimke
 wrote:
>
> Dear List Members,
>
> i had already sent this to the docbook List, but probably this list 
> docbook-apps fits better.
>
> I am using DocBook for a bi-lingual book. Most of the content is written in 
> english, but parts are written in the german language. PDF is produced with 
> XSL Stylesheets 1.79.2 shipped within Oxygen 24 and the Antenna House 
> Formatter v7.
>
> Since most content is english, /book/@xml:lang is 'en'. Fragments in german 
> have @xml:lang='de' at the appropriate level, e. g. for section or note 
> elements. Sometimes i have phrase or emphasis elements only because of the 
> @xml:lang attribute.
>
> Observation is, that hyphenation is wrong in the PDF Document for the german 
> fragments. I think i have found the reason, but i am puzzled. There are two 
> issues which i can't understand:
>
> 1) There is a template named "language.attribute" in I10n.xsl. It calculates 
> the language value looking at the ancestor axis, and emits an attribute named 
> @lang with that value. First Issue: the name of the attribute is wrong, the 
> correct name is @language. See section 7.10.2 "Language"  in Extensible 
> Stylesheet Language (XSL) Version 1.1.
>
> 2) The template named "language.attribute" is rarely used. 2nd Issue: I had 
> to create a customization layer for the templates that matches d:para or 
> d:simpara, which do emit an fo:block element, so that they call the 
> language.attribute template. Same for d:phrase and d:emphasis in inline.xsl
>
> Maybe i have missed something obvious. Are there any reasons for this lack of 
> language support?
>
> Sincerely, Frank Steimke



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Canonical DocBook

[Dave Pawson]

On Sun, 27 Feb 2022 at 11:20, Frank Steimke
 wrote:
>
> What would be a better way to accomplish this?
>
> Ask Norm to document its internal format so that a particular community
> can choose it as the "de facto standard" for developing own stylesheets
> based on it?

Not sure at all Frank.
   Democratic solution perhaps? Majority of TC support A vs B?
Then rely on Norm () to write appropriate stylesheets? Seems unfair IMHO

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Canonical DocBook

[Dave Pawson]

On Sun, 27 Feb 2022 at 11:02, Frank Steimke
 wrote:

> My suggestion is that the DocBook TC standardize and document the
> canonical DocBook format.

(My view). This is the problem Frank?
I'm sure, even within the TC, that defining and agreeing which 'form'
is to be named Canonical
would be contentious?

I agree with the motive, I'm less sure about the means of achieving it?

regards


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Do different xslt processors and parsers really make a difference for pdf output?

[Dave Pawson]

Pure prejudice Kevin. Saxon. 6.x if you need xslt 1.0, otherwise 10 if you can.
   No connection (other than experience) with Saxon.
HTH

On Tue, 6 Jul 2021 at 18:29, Kevin Dunn  wrote:
>
> Thanks, Norm. Yes, I evaluated fop, xep, and ahf, and bought the Antenna 
> House Formatter. My question now is between xsltproc, Saxon 6.5, and Saxon 
> 10. All three are working for me, and I don't have a reason to prefer one to 
> the others. Is there one?
>
> Get Outlook for Android
>
> 
> From: Norm Tovey-Walsh 
> Sent: Tuesday, July 6, 2021, 12:46 PM
> To: Kevin Dunn
> Cc: docbook-apps@lists.oasis-open.org
> Subject: Re: [docbook-apps] Do different xslt processors and parsers really 
> make a difference for pdf output?
>
> Kevin Dunn  writes:
> > Are there reasons to prefer one of these xslt processors to the
> > others? Is it worth looking at the commercial processors?
>
> That’s going to depend on how complicated your output is. The commercial
> processors like AntennaHouse offer both better and more complete support
> for the FO specification. They also offer extensions for things that
> never got standardized.
>
> Be seeing you,
>   norm
>
> --
> Norman Tovey-Walsh 
> https://nwalsh.com/
>
> > Man is not logical and his intellectual history is a record of mental
> > reserves and compromises. He hangs on to what he can in his old beliefs
> > even when he is compelled to surrender their logical basis.--John Dewey
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] insert.link.page.number in xsl stylesheets

[Dave Pawson]

Perhaps look up template overrides? Bobs site again.
Hth

On Tue, 15 Jun 2021 at 16:07, Kevin Dunn  wrote:

> Thanks. Changing the default worked for both xref and link. I could not
> make a custom "mystyle" style work with either of them. That's fine. I
> would prefer to have the same style throughout a document, except when I
> don't want a page reference. "nopage" works for both xrefs and links, so
> now I'm able to do everything I want to do.
>
> FYI, when I tried to use a custom "mystyle", both xref and link gave me
> the default style. xref recognizes page, Page, pageabbrev, pagenumber, and
> nopage. Anything else (including "mystyle") gives the default. link
> recognizes only nopage. Anything else gives the default.
> --
> *From:* Bob Stayton 
> *Sent:* Tuesday, June 15, 2021 2:25 AM
> *To:* Kevin Dunn ; docbook-apps@lists.oasis-open.org <
> docbook-apps@lists.oasis-open.org>
>
> *Subject:* Re: [docbook-apps] insert.link.page.number in xsl stylesheets
>
>
> Hi Kevin,
>
> Indeed, it looks like the "select:" mechanism in @xrefstyle was never
> implemented for link element page references, only for xrefs.  This will
> require customizing the generated text instead.  See
> http://www.sagehill.net/docbookxsl/CustomGentext.html#CustomGenText
>
>
> You can change the default (unspecified) style by adding this to your
> customization layer:
>
>
> 
> http://docbook.sourceforge.net/xmlns/l10n/1.0;
> <http://docbook.sourceforge.net/xmlns/l10n/1.0>>
>   
> 
>   
> 
>   
> 
>
>
> If you don't want to alter the default style, the named style mechanism
> does work, so you could add a this  instead (note the @style attribute):
>
> .
>
> 
> http://docbook.sourceforge.net/xmlns/l10n/1.0;
> <http://docbook.sourceforge.net/xmlns/l10n/1.0>>
>   
> 
>   
> 
>   
> 
>
>
> Then you would get your style if you specify ,
> otherwise you get the default.
>
> Bob staytonb...@sagehill.net
>
> On 6/14/2021 8:27 PM, Kevin Dunn wrote:
>
> Putting "'yes'" (single in double quotes) in the param statement got the
> links to put out page numbers. I guess that's what I get for reading
> Chapter 15 before Chapter 1. But links put out the "unspecified" page
> style, no matter what xrefstyle is set to. I tried:
>
> A Chapter link
>
> A Chapter link
>
> A Chapter link
>
> A Chapter link
>
> A Chapter link
>
> In all five cases, the rendering was:
> A Chapter link [15]
>
> Interestingly, xref and link behave differently when it comes to quotes,
> and I can see that they are treated differently in xref.xsl.
> --
> *From:* Bob Stayton  
> *Sent:* Monday, June 14, 2021 5:00 PM
> *To:* docbook-apps@lists.oasis-open.org
>  
> *Subject:* Re: [docbook-apps] insert.link.page.number in xsl stylesheets
>
>
> I think the problem is in the param statement, where the string yes is
> being interpreted as an element name.
>
>
> 
>
>
> (I added single quotes around the word yes).
>
> Bob staytonb...@sagehill.net
>
> On 6/14/2021 12:05 PM, Kevin Dunn wrote:
>
> I'm customizing xrefs to render page numbers in pdf files for print.
> Setting insert.xref.page.number to yes, and using an xrefstyle attribute, I
> can get the desired output, e.g. "See Appendix B (page 127)."
>
> Page number for links do not work as I would expect from reading
> http://www.sagehill.net/docbookxsl/CustomXrefs.html.
>
> In my custom xsl, I have both:
> 
> 
>
> My xml file contains both:
> 
> A Chapter link
>
> The fo from xsltproc renders page numbers for the xref, but not for the
> link. The behavior is the same using version 1.79.1 stylesheet and the
> snapshot/2020-06-03. Fop, xep, and axf produce PDFs with working links, but
> rendered page numbers only for the xrefs.
>
> I may be misreading the documentation or misunderstanding the xsl (very
> possible). The xsl is different for xref and link in xref.xsl, but to my
> untrained eye, both look reasonable.
>
> Any suggestions?
>
> --
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

Re: [docbook-apps] Two nagging problems with docbook2pdf in texlive 2019

[Dave Pawson]

On Fri, 11 Jun 2021 at 23:05, Kevin Dunn  wrote:
>
> I spent the day playing with the demo versions of XEP and Antenna House 
> Formatter. I got both of them up and running using xsltproc and the default 
> xsl stylesheet, with the SelfDocBook as a source xml file. Pdf from both 
> looks good.
>
> Following DocBook XSL TCG, I was able to add a new font and enable ligatures 
> by editing xep.xml. So XEP seems like I could make it work.
>
> Antenna House Formatter was not too bad to install, but the documentation is 
> huge, and I have yet to figure out how to add a font or enable ligatures. I 
> found the font-config.xml file and added a font to it, but I can't figure out 
> how to tell the formatter to use that font.

That's where you need to read up on xsl-fo. Called up from xsl-fo, AH
then uses font-config to locate the file.

There also seems to be extensions required to enable ligatures, but I
haven't figured out how to use them, either on the command line or in
a configuration file. Is the AH Formatter much more complicated to use
than XEP? Any kind of "newbie guide" for it?

Simple things easy, more complex things you have to work at. No
dummies book that I know of.


>
> As much as I hate to flush all my dsssl-jadetex customizations, it seems like 
> xsl-fo is going to be the way to go.


I think so.
How much work went into learning DSSSL and \tex?

regards


>
>
>  From: Norm Tovey-Walsh
> Sent: Friday, June 11, 2021 11:00 AM
> To: Kevin Dunn
> Cc: docbook-apps@lists.oasis-open.org
> Subject: Re: [docbook-apps] Two nagging problems with docbook2pdf in texlive 
> 2019
>
> Kevin Dunn  writes:
> > Thanks, Dave. You were helpful to me 10 years ago. The XEP PDF output
> > looks pretty nice with the default xsl stylesheet. There are some
> > fancy things I achieved with dsssl and jadetex, and I'm not sure how
>
> There’s a blast from the past!
>
> I’ve been chatting, off and on, with Peter Flynn about working on a way
> to use TeX as a formatting back end in the modern era. But it’s not in
> the top couple of reams of the todo list, at the moment.
>
> I expect the future is XML+CSS and that’s what I have in mind for the
> xslTNG stylesheets. It would be entirely possible, of course, to
> generate XSL-FO, but it feels like custom-HTML output and custom-CSS fed
> through Antennahouse would be the shortest path to victory.
>
> PrinceXML would also work that way.
>
> AFAIK, there are no free formatters that take HTML+CSS and produce
> results comparable with FOP, which surprises me. (Not that the FOP level
> of output would satisfy your requirements; but the lack of reasonable
> open source print formatters is one of the things that leads me to
> ponder generating LaTeX. You know, like we did in the 90’s when we were
> young! :-))
>
> Be seeing you,
>   norm
>
> --
> Norman Tovey-Walsh 
> https://nwalsh.com/
>
> > Linux. Because rebooting is for hardware upgrades.



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Two nagging problems with docbook2pdf in texlive 2019

[Dave Pawson]

On Fri, 11 Jun 2021 at 14:53, Kevin Dunn  wrote:
>
> Thanks, Dave. You were helpful to me 10 years ago. The XEP PDF output looks 
> pretty nice with the default xsl stylesheet. There are some fancy things I 
> achieved with dsssl and jadetex, and I'm not sure how easy they would be with 
> an xsl-fo toolchain:
>
> the Lettrine tex package did a great job producing drop caps.

Nope. Do you really need them?

> I wrote custom dsssl to make xref link to page numbers, for example "These 
> are found in Appendix A (page 127)."

Can do, xslt to produce links in xsl-fo, will product PDF links.

> pdfjadetex produces nice ligatures, including, for example, ffi. Using the 
> default xsl stylesheet, fop doesn't do any ligatures, and xep does fi, but 
> not ffi. Maybe it depends on the font?

Could be, I don't know. Again, essential?


> The titlepage used a custom graphic for the title, rather than rendering it 
> in a font.

Can do. In the xslt to xsl-fo layer.

>
> I'm willing to learn xsl-fo, and I'm willing to spend hundreds, but not 
> thousands of dollars on commercial tools. I've tried xsltproc-fop and 
> xsltproc-xep. Are there other combinations for less than a thousand dollars?

Yes. Antenna house. Expensive, but (IMHO) the best today.

HTH

>
>
> 
> From: Dave Pawson 
> Sent: Friday, June 11, 2021 3:49:18 AM
> To: Kevin Dunn 
> Cc: docbook-apps@lists.oasis-open.org 
> Subject: Re: [docbook-apps] Two nagging problems with docbook2pdf in texlive 
> 2019
>
> My view, a 12 yo tool chain is plain OOD?
>
> How much work did you put in to the stylesheets?
> Is the up to date XSL too far from what you can manage with?
>
> regards
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Two nagging problems with docbook2pdf in texlive 2019

[Dave Pawson]

My view, a 12 yo tool chain is plain OOD?

How much work did you put in to the stylesheets?
Is the up to date XSL too far from what you can manage with?

regards

On Fri, 11 Jun 2021 at 03:46, Kevin Dunn  wrote:
>
> For context, I have published two books marked up in Docbook xml, the first 
> in 2003, and the second in 2010. Both were converted to pdf using docbook2pdf 
> on linux boxes using customized dsssl stylesheets and several tex packages.
>
> In anticipation of writing a third book, I installed texlive on a Ubuntu 
> 20.04 box, and was pleased to find the familiar tools and packages there. I 
> copied my 2010 book over from the very old computer where it was living, and 
> with a few tweaks, I can get it to process (mostly) with my previous 
> stylesheets. However, there are two nagging problems with the docbook2pdf 
> included with texlive:
>
> The book has several Parts. docbook2pdf paginates Part 1 with roman page 
> numbers. Chapter 1 starts on page 1. I would like Part 1 to start on page 1 
> (as it did with the 2009 toolchain).
> The book has Figures, Examples, Tables, and Equations. My dsssl stylesheet 
> uses $generate-book-lot-list$ to list those elements that should get their 
> own list after the table of contents. But only the first one in the list 
> actually shows up in the pdf, for example List  of Tables but nothing for 
> figures or equations, even though they are included in 
> $generate-book-lot-list$
>
> In troubleshooting this, I found that the same things happen with a very 
> simple book.xml file and no customization in the dsssl stylesheets, i.e., 
> docobook2pdf book.xml using the default stylesheet.
>
> I realize this toolchain is very old, but I would really like to get it 
> working again. I have looked at other toolchains:
>
> dblatex places Part 1 on page 1, but only gives a List of Tables.
> xsltproc and fop give correct page numbers and Lists, but I'd be starting 
> over with xsl as far as stylesheet customizations.
> xsltproc and xep (free trial) also get the page numbers and Lists correct, 
> but again, I'd be starting over on my stylesheets.
>
> Any suggestions on fixing these issues?
> Thanks in advance,
> Kevin Dunn



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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 Transclusion in xslTNG

[Dave Pawson]

And (for some), in either requirement or defn, add a defn of
transclusion please.

transclusion is the inclusion of part or all of an electronic document
into one or more other documents by hypertext reference. Transclusion
is usually performed when the referencing document is displayed, and
is normally automatic and transparent to the end user.[1] The result
of transclusion is a single integrated document made of parts
assembled dynamically from separate sources, possibly stored on
different computers in disparate places.

src: Wikipedia

On Tue, 11 May 2021 at 11:05, Norm Tovey-Walsh  wrote:
>
> Dave Pawson  writes:
>
> > from your [1] https://docbook.org/docs/transclusion/transclusion.html
> > https://docbook.org/docs/transclusion-requirements/   is 404 Norm?
> >
> > Should it be the 2010 version?
> > https://docbook.org/docs/transclusion-requirements/transclusion-requirements.html
>
> I think so. Both those documents need another cleanup and formatting
> pass. I’ll try to get to that.
>
> Be seeing you,
>   norm
>
> --
> Norman Tovey-Walsh 
> https://nwalsh.com/
>
> > Time makes more converts than reason.--Tom Paine



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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 Transclusion in xslTNG

[Dave Pawson]

from your [1] https://docbook.org/docs/transclusion/transclusion.html
https://docbook.org/docs/transclusion-requirements/   is 404 Norm?

Should it be the 2010 version?
https://docbook.org/docs/transclusion-requirements/transclusion-requirements.html

regards

On Tue, 11 May 2021 at 10:16, Norm Tovey-Walsh  wrote:
>
> Good morning (well, in this locale anyway),
>
> I set out to implement DocBook Transclusion in the DocBook xslTNG
> Stylesheets the other day and discovered that a previous attempt to
> implement it was already in place.
>
> It appears to have been an attempt to implement the previous draft of
> DocBook Transclusion, not the most recent[1], and I don’t believe it
> works.
>
> If you’re using DocBook Transclusion with the DocBook xslTNG Stylesheets
> and you think it’s doing something useful, please let me know.
>
> I plan to revamp it completely in the next release. I’d be worried about
> doing a backwards incompatible change except, as I said, I don’t think
> the current implementation does anything remotely useful.
>
> Be seeing you,
>   norm
>
> [1] https://docbook.org/docs/transclusion/transclusion.html
>
> --
> Norman Tovey-Walsh 
> https://nwalsh.com/
>
> > Do not seek to follow in the footsteps of men of old; seek what they
> > sought.--Matsuo Basho



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Thumbnails?

[Dave Pawson]

Perfect Bob, thank you.

regards

On Fri, 7 May 2021 at 22:51, Bob Stayton  wrote:
>
> I think you might be looking to set the stylesheet parameter 
> link.to.self.for.mediaobject="1".
>
> http://docbook.sourceforge.net/release/xsl/current/doc/html/link.to.self.for.mediaobject.html
>
> That produces the image in place scaled per attributes, and also wraps the 
> image in a direct link to the image file, which would show it unscaled (or 
> full scale) in the browser window.
>
> Bob Stayton
> b...@sagehill.net
>
> On 5/7/2021 12:27 AM, Dave Pawson wrote:
>
> I've a set of photographs of document pages.
> With small text if the page is zoomed to make the text readable
> the main page text is ... too big.
>
> html output, is it possible to insert the thumbnail with a link to the
> full size image please?
>
> TiA
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Thumbnails?

[Dave Pawson]

I've a set of photographs of document pages.
With small text if the page is zoomed to make the text readable
the main page text is ... too big.

html output, is it possible to insert the thumbnail with a link to the
full size image please?

TiA

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Separated indices for webhelp & epub3 output

[Dave Pawson]

Well, if you work for nothing, I'm sure others will too?
(or is there some failure in logic there?)


On Thu, 4 Mar 2021 at 12:58, Thomas Schmiedl  wrote:
>
> I thought a pro can "pretty easy" work in the index.on.type behavior in
> other formats (it exists in the recent snapshot for xhtml-1_1, html, fo
> and xhtml).
>
> Thanks,
> Thomas
>
> Am 04.03.2021 um 10:47 schrieb Kerry, Richard:
> >
> > When you asked "could someone customize", did you mean:
> >
> > "will someone write this customization for me?"
> >
> > Or did you mean
> >
> > "is it possible to customize, and could someone advise how I might go about 
> > doing it?".
> >
> > If it's the former case, then you should expect to have to pay someone.
> > If it's the latter, please clarify, and then someone might be able to 
> > advise you.
> >
> >
> > Regards,
> > Richard.
> >
> >
> > -Original Message-
> > From: Thomas Schmiedl 
> > Sent: 03 March 2021 17:53
> > To: Dave Pawson 
> > Cc: docbook-apps 
> > Subject: Re: [docbook-apps] Separated indices for webhelp & epub3 output
> >
> > Caution! External email. Do not open attachments or click links, unless 
> > this email comes from a known sender and you know the content is safe.
> >
> > I have no budget for this private project sorry.
> >
> > Am 03.03.2021 um 17:53 schrieb Dave Pawson:
> >> What would you pay for this service Thomas?
> >>
> >> regards
> >>
> >> On Wed, 3 Mar 2021 at 16:52, Thomas Schmiedl  
> >> wrote:
> >>>
> >>> Hello,
> >>>
> >>> could someone customize the docbook-xsl stylesheets to support
> >>> "index.on.type" (separated indices) for webhelp and epub3 output? I
> >>> need it for a private project and I have very few xslt knowledge.
> >>>
> >>> Thanks for help,
> >>> Thomas
> >>>
> >>> -
> >>> 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
> >
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Separated indices for webhelp & epub3 output

[Dave Pawson]

What would you pay for this service Thomas?

regards

On Wed, 3 Mar 2021 at 16:52, Thomas Schmiedl  wrote:
>
> Hello,
>
> could someone customize the docbook-xsl stylesheets to support
> "index.on.type" (separated indices) for webhelp and epub3 output? I need
> it for a private project and I have very few xslt knowledge.
>
> Thanks for help,
> Thomas
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Re: dblite v1.19, derived from docbook vsn 4.1?

[Dave Pawson]

On Sat, 6 Feb 2021 at 10:21, Dave Pawson  wrote:
>
> I think from docbook 4.1
>
> This from an O'Reilly xml source.
>
> The current docbook 'upgrade' options
> http://doccookbook.sourceforge.net/html/en/dbc.structure.db4-to-db5.html

oops
That page links to
https://github.com/docbook/docbook/blob/main/relaxng/tools/db4-upgrade.xsl

which is 404?

regards


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] dblite v1.19, derived from docbook vsn 4.1?

[Dave Pawson]

I think from docbook 4.1

This from an O'Reilly xml source.

The current docbook 'upgrade' options
http://doccookbook.sourceforge.net/html/en/dbc.structure.db4-to-db5.html

Anyone know if this is OK with the O'Reilly version of docbook please?

TiA


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Generating markdown output from DocBook

[Dave Pawson]

As always, the question remains, which markdown?
   Such a long processing chain may cause problems?
regards

On Wed, 27 Jan 2021 at 02:11, Peter Desjardins
 wrote:
>
> I'm finding that more documentation tools are optimized for consuming 
> markdown these days. For example, some commercial API portal frameworks and 
> site-generation tools use markdown as their default input formats.
>
> Does anyone have a nice solution for using tools that consume markdown when 
> you write and maintain your documentation source in DocBook XML format?
>
> I have considered using a utility like Pandoc as a final processing step. So 
> the chain would be something like DocBook > XSLT > HTML > Pandoc > markdown.
>
> I have also wondered whether anyone has built DocBook XSLT that directly 
> converts the XML to markdown.
>
> Do you have something that works well for you?
>
> Thanks!
>
> Peter



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Validating against Schematron

[Dave Pawson]

On Tue, 28 Jul 2020 at 22:55, Richard Hamilton  wrote:
>
> This is a question for the group.
>
> What do you currently use for validating DocBook agains both RelaxNG and 
> Schematron?
>
> I’ve been looking around and downloading and trying some 10-to-15 year old 
> solutions, but I figure there has to be something newer (or an update to one 
> of the older ones) that does the job.

Jing? Fast and accurate. Does the job well IMHO.


regards


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] using olinks everywhere?

[Dave Pawson]

Sorry all.
 My bad.

Regards

On Sun, 12 Jul 2020 at 17:54, Norman Tovey-Walsh  wrote:
>
> Dave Pawson  writes:
> > (Waiting for @ndw to read your post)
> > I think he is playing with an alt to such links, build for Summer conf 
> > present.
> > I couldn't find it searching his blog posts...
>
> I’m afraid I haven’t tackled the more interesting corners of olink yet.
>
> Be seeing you,
>   norm
>
> --
> Norman Tovey-Walsh 
> https://nwalsh.com/
>
> > There is no such thing as a moral or immoral book. Books are well
> > written or badly written.--Oscar Wilde



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] using olinks everywhere?

[Dave Pawson]

(Waiting for @ndw to read your post)
I think he is playing with an alt to such links, build for Summer conf present.
I couldn't find it searching his blog posts...

  Hang fire until (if) he responds.

For me, such inter-doc links were a bit of a kludge.

regards

On Fri, 10 Jul 2020 at 16:00, Barton Wright  wrote:
>
> Thanks, Tony.
>
> As I said, PDF-fu. You work for Antenna House, Masters of the PDF Universe. 
> Case, rested.
>
> But, the question for us is whether the DocBook XSL supports generating these 
> links, and does so without using (forgive me) a very expensive FO processor. 
> A quick find -exec grep tells me our doc set has about 10,500 olinks. No one 
> is going to fix those manually.
>
>
> On Jul 10, 2020, at 10:28 AM, Tony Graham  wrote:
>
> On 10/07/2020 14:17, Barton Wright wrote:
> ...
>
>  * PDFs. Yeah, you can’t cross-ref from one PDF into a page or section
>inside another PDF — or not without profound PDF-fu above my level.
>
>
> There's more options than you ever thought possible.  See the example
> URLs at:
>
>   https://www.antenna.co.jp/AHF/help/v70e/ahf-ext.html#pdf-link
>
> and the eight-page (four pages of actual content) "PDF Open Parameters"
> spec at:
>
> https://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/PDFOpenParameters.pdf
>
> Regards,
>
>
> Tony Graham.
> --
> Senior Architect
> XML Division
> Antenna House, Inc.
> 
> Skerries, Ireland
> tgra...@antenna.co.jp
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Building docbook instances.

[Dave Pawson]

I've been using ant for a number of years, quite happily.
I note @ndw has moved on to another build system.

I am wondering if anyone has used xproc with docbook,
and if so, how have you found it?


TiA

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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]

[Dave Pawson]

Is there a calabash / xproc list? Seems it would make more sense?

HTH

On Fri, 28 Feb 2020 at 16:40, aanno  wrote:
>
> Hello,
>
> I'm looking for an example how to use/apply  xmlcalabash
> extension step (https://github.com/ndw/xmlcalabash1-xslthl) on a docbook
> programlistingelement when using the xslt20 stylesheets.
>
> I know some XSLT 1.0 and there is a description how to use xslthl
> directly there (https://sourceforge.net/p/xslthl/wiki/Usage/). But I'm a
> bit lost on how to 'translate' that to an XProc calabash extensions step.
>
> My best guess so far was:
>
> 
>   
> 
>
> But this leads to the error message:
>
> > [main] ERROR com.xmlcalabash.util.DefaultXProcMessageListener -
> > src/main/resources/docbook-xsl20/db2html-db-toolchain.xpl:36:16:Required
> > option not specified: highlighter
> > [main] ERROR com.xmlcalabash.util.DefaultXProcMessageListener -
> > src/main/resources/docbook-xsl20/db2html-db-toolchain.xpl:36:16:err:XS0018:Required
> > option not specified: highlighter
>
> Kind regards,
>
> Thomas
>
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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 builds? Which is favourite?

[Dave Pawson]

Thanks Erik - fits well with github.
   I never did get on well with xproc, so I'll give that a miss!

regards

On Mon, 9 Sep 2019 at 08:49, Erik Rask  wrote:
>
> Hi Dave,
>
> Since we store all our sources in GitLab, I went ahead and implemented a CI 
> pipeline based on xsltproc and fop. Very neat once you have a workflow with 
> all the branching abilities of git. Once you're familiar with it, a lot of 
> logic can be applied there that offloads a writing team.
>
>
> Best,
>
> /Erik
>
> ________
> From: Dave Pawson 
> Sent: Sunday, February 24, 2019 10:14:08 AM
> To: docbook-apps
> Subject: [docbook-apps] Docbook builds? Which is favourite?
>
> I started using ant as my docbook builds became more complex.
> I stayed with it.
>
> Recently noted others requesting Maven - then ndw with Gradle.
>
> Wondering which tools you find most convenient for docbook?
>
> Dave
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] html table, create wrapper div with class

[Dave Pawson]

Put multiple @class on the table?

HTH

On Thu, 29 Aug 2019 at 14:28, Tim Arnold  wrote:
>
> Hi,
> I'm converting DocBook 5 to html (docbook-xsl-1.79.2) with a customization 
> layer.
> I now need to wrap my table elements inside a div with a particular class 
> (say 'tabular-wrapper' for example).
> My tables in the DocBook XML source are HTML tables.
>
> Currently the tables are rendered by the stylesheet as:
> 
> 
>... 
> 
> 
>
> I want the tables to look like this:
> 
> 
>... 
> 
>  
>
> or perhaps
> 
> 
>... 
> 
>  
>
> It appears that the $class variable the formal.xsl stylesheet 
> (htmlTable.with.caption template) refers to is blank.
> 
>
> As a last resort, I can copy the template into my customization layer with 
> appropriate edits.
>
> My question is whether that is the best I can do?
> Or is there a way to populate the $class variable just for tables?
>
> thanks for any ideas!
> --Tim



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] How to use a catalog for an entity declaration file?

[Dave Pawson]

t;>  >> "http://someHost/Common/commonentityID; >
> >
> > would be resolved by a catalog entry like this:
> >
> >>  http://someHost/Common/commonentityID;
> >> uri="file:///C:/Activity/Cogent/Docs/DocsOx/Source/Common/commonentit
> >> i
> >> es.ent"/>
> >
> > Also in practice no absolute file references should be in the catalog.xml.
> > So the catalog.xml would be placed as close as possible to the DTDs,
> > for example in the "DocsOx/Source/Common" folder, meaning that the
> > @uri attribute value would be something like this:
> >
> >> 
> >
> >
> > Regards,
> > Radu
> >
> > Radu Coravu
> >  XML Editor
> > http://www.oxygenxml.com
> >
> > On 3/11/2019 10:33 PM, Bob McIlvride wrote:
> >> Dear friends,
> >>
> >>
> >>
> >> I am trying to implement this guidance from Chapter 23. Modular
> >> DocBook files of Bob Stayton's DocBook XSL: The Complete Guide - 4th
> > Edition:
> >>
> >>
> >>
> >> "If all of your modules and document files have the same entity
> >> declaration and reference, then they will all share the same set of
> >> entities. You can use an XML catalog to map the filename to a
> >> specific pathname on a system so it can be in a central location."
> >>
> >> http://www.sagehill.net/docbookxsl/ModularEntities.html#entities.in.d
> >> t
> >> d
> >>
> >>
> >>
> >> My problem is that I don't know the correct syntax for the system
> >> entity declaration.  For example, this doesn't work:
> >>
> >>
> >>
> >>  >>
> >> 
> >>
> >> %commonentities;
> >>
> >> ]>
> >>
> >> ...
> >>
> >>
> >>
> >> My catalog looks like this:
> >>
> >>
> >>
> >> 
> >>
> >>  >> uri="file:///C:/Activity/Cogent/Docs/DocsOx/Source/Common/commonentit
> >> i
> >> es.ent"/>
> >>
> >> 
> >>
> >>
> >>
> >> The catalog validates in Oxygen.
> >>
> >>
> >>
> >> Without attempting to use the catalog, this is what we normally use:
> >>
> >>
> >>
> >>  >>
> >> 
> >>
> >> %commonentities;
> >>
> >> ]>
> >>
> >> ...
> >>
> >>
> >>
> >> This also validates and produces correct output.  How can we get this
> >> working using a catalog?  Any suggestions would be most helpful.
> >>
> >>
> >>
> >> Best regards,
> >>
> >>
> >>
> >> Bob
> >>
> >>
> >>
> >>
> >>
> >> COGENT <http://cogent.ca/>
> >>
> >>
> >>
> >> *Bob McIlvride **   Communications Manager*
> >>
> >> Cogent Real-Time Systems Inc., a Skkynet company
> >>
> >> T   1 905 702 7851 ext 103
> >>
> >> cogent.ca <http://cogent.ca/>
> >>
> >>
> >>
> >
> >
> >
> > -
> > 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
> >
>
>
>
> -
> 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
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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 builds? Which is favourite?

[Dave Pawson]

I started using ant as my docbook builds became more complex.
I stayed with it.

Recently noted others requesting Maven - then ndw with Gradle.

Wondering which tools you find most convenient for docbook?

Dave

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] I have paragraphs that contains MarkDown. Is there a way in the XSLT to process them as markdown?

[Dave Pawson]

Neat Jirka.
Of note, "Md2doc supports canonical Markdown specification by John Gruber"

regards

On Mon, 11 Feb 2019 at 14:14, Jirka Kosek  wrote:
>
> On 7.2.2019 17:22, Loren Cahlander wrote:
> > The entry for the param of $files is in MarkDown format.  Is there a way 
> > for the MarkDown to be processed when generating the PDF?
>
> Hi Loren,
>
> student of my wrote XSLT 2 transform that can parse Markdown and convert
> it to DocBook:
>
> https://github.com/MSmid/markdown2docbook
>
> You can add preprocessing step that would expand Markdown to DocBook
> prior normal DocBook processing.
>
> Jirka
>
> --
> --
>   Jirka Kosek  e-mail: ji...@kosek.cz  http://xmlguru.cz
> --
>  Professional XML and Web consulting and training services
> DocBook/DITA customization, custom XSLT/XSL-FO document processing
> --
> Bringing you XML Prague conferencehttp://xmlprague.cz
> --
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] pubwork does not include a thesis

[Dave Pawson]

On Mon, 19 Nov 2018 at 10:31, Bernhard Kleine  wrote:
>
> Hi,
>
> I am surprised that the attribute of citetitle does not include any form of a 
> thesis. This is a serious flaw.

Docbook wasn't created for academic works.
You can extend the schema quite readily as per your example?

HTH


> Isolierung und  ... 
>
> Any choice is not appropriate for thesis:
> value of attribute "pubwork" is invalid; must be equal to "article", "bbs", 
> "book", "cdrom", "chapter", "dvd", "emailmessage", "gopher", "journal", 
> "manuscript", "newsposting", "part", "refentry", "section", "series", "set", 
> "webpage" or "wiki"
>
> How long will it take to change the behaviour?
>
> Regards Bernhard
>
> --
>
> spitzhalde9
> D-79853 lenzkirch
> bernhard.kle...@gmx.net
> www.b-kleine.com, www.urseetal.net
> -
> thunderbird mit enigmail
> GPG schlüssel: D5257409
> fingerprint:
> 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Seriesinfo tag not respected

[Dave Pawson]

It's not in 5.0 either Bernhard?

Dave
On Mon, 19 Nov 2018 at 09:17, Bernhard Kleine  wrote:
>
> Or the RNG changed since a seriesinfo tag was obviously intended.
>
> Regards
>
> Bernhard
>
> Am 19.11.2018 um 07:54 schrieb Radu Coravu:
> > Hi Bernhard,
> >
> > I looked at the DocBook 5.1 RNG located on their web site:
> >
> > https://docbook.org/xml/5.1/rng/docbook.rng
> >
> > and there is no "seriesinfo" element defined in it so probably the
> > example here needs to be updated:
> >
> > https://tdg.docbook.org/tdg/5.1/ch02.html#s.bibliography
> >
> > Regards,
> > Radu
> >
> > Radu Coravu
> >  XML Editor
> > http://www.oxygenxml.com
> >
> > On 11/18/2018 11:38 AM, Bernhard Kleine wrote:
> >> I am using Oxygen xml editor 20.1.
> >>
> >> Am 18.11.2018 um 10:36 schrieb Dave Pawson:
> >>> How are you validating the xml instance please Bernhard?
> >>>   Simple method, against the .rng schema, using Jing
> >>> (https://github.com/relaxng/jing-trang)
> >>>See if you still get an error?
> >>>
> >>> HTH
> >>>
> >>>
> >>> On Sun, 18 Nov 2018 at 09:22, Bernhard Kleine  >>> <mailto:bernhard.kle...@gmx.net>> wrote:
> >>>
> >>> This is the header for the biblioentry shown in the previous mail.
> >>>
> >>> 
> >>> http://docbook.org/xml/5.1/rng/docbook.rng;
> >>> <http://docbook.org/xml/5.1/rng/docbook.rng>
> >>> schematypens="http://relaxng.org/ns/structure/1.0;
> >>> <http://relaxng.org/ns/structure/1.0>?>
> >>> http://docbook.org/xml/5.1/sch/docbook.sch;
> >>> <http://docbook.org/xml/5.1/sch/docbook.sch>
> >>> type="application/xml"
> >>> schematypens="http://purl.oclc.org/dsdl/schematron;
> >>> <http://purl.oclc.org/dsdl/schematron>?>
> >>>
> >>>  >>> xmlns="http://docbook.org/ns/docbook;
> >>> <http://docbook.org/ns/docbook>
> >>> xmlns:xlink="http://www.w3.org/1999/xlink;
> >>> <http://www.w3.org/1999/xlink>
> >>> xmlns:ns="http://docbook.org/ns/docbook;
> >>> <http://docbook.org/ns/docbook>>
> >>>
> >>> Am 18.11.2018 um 09:56 schrieb Dave Pawson:
> >>>> https://tdg.docbook.org/tdg/5.1/
> >>>>
> >>>> Again, no seriesinfo element?
> >>>> IIRC the tdg is generated from the schema?
> >>>>
> >>>> Bob / Norm would need to state which is definitive.
> >>>>
> >>>> https://tdg.docbook.org/tdg/5.1/set.html is set any more
> >>>> helpful?
> >>>>
> >>>> regards
> >>>>
> >>>>
> >>>> On Sun, 18 Nov 2018 at 08:13, Bernhard Kleine
> >>>> mailto:bernhard.kle...@gmx.net>> wrote:
> >>>>
> >>>>     Hi Dave,
> >>>>
> >>>> in https://tdg.docbook.org/tdg/5.1/ch02.html#s.bibliography
> >>>> there is the seriesinfo tag, however, there is an validation
> >>>> error with seriesinfo:
> >>>>
> >>>> 
> >>>>
> >>>>
> >>>>
> >>>> IsabelVarelaNieto
> >>>> Julie
> >>>> A.Chowen
> >>>>
> >>>> 
> >>>> 
> >>>> THE GROWTH
> >>>> HORMONE/INSULINLIKE GROWTH FACTOR AXIS DURING
> >>>> DEVELOPMENT
> >>>> 2005
> >>>> 
> >>>> 
> >>>> ADVANCES IN EXPERIMENTAL MEDICINE AND
> >>>> BIOLOGY
> >>>> 
> >>>> 10.1007/b106814
> >>>>  >>>> class="isbn">9780387251196
> >>>> 
> >>>>
> >>>> Regards
> >>>>
> >>>> Bernhard
> >>>>
> >>>> Am 18.11.2018 um 07:31 schrieb Dave Pawson:
> >>>>> https://tdg.docbook.org/tdg/5.1/
> >>

Re: [docbook-apps] Seriesinfo tag not respected

[Dave Pawson]

How are you validating the xml instance please Bernhard?
  Simple method, against the .rng schema, using Jing
(https://github.com/relaxng/jing-trang)
   See if you still get an error?

HTH


On Sun, 18 Nov 2018 at 09:22, Bernhard Kleine 
wrote:

> This is the header for the biblioentry shown in the previous mail.
>
> 
> http://docbook.org/xml/5.1/rng/docbook.rng;
> <http://docbook.org/xml/5.1/rng/docbook.rng> schematypens=
> "http://relaxng.org/ns/structure/1.0;
> <http://relaxng.org/ns/structure/1.0>?>
> http://docbook.org/xml/5.1/sch/docbook.sch;
> <http://docbook.org/xml/5.1/sch/docbook.sch> type="application/xml"
> schematypens="http://purl.oclc.org/dsdl/schematron;
> <http://purl.oclc.org/dsdl/schematron>?>
>
>  xmlns="http://docbook.org/ns/docbook; <http://docbook.org/ns/docbook>
> xmlns:xlink="http://www.w3.org/1999/xlink;
> <http://www.w3.org/1999/xlink>
> xmlns:ns="http://docbook.org/ns/docbook;
> <http://docbook.org/ns/docbook>>
>
> Am 18.11.2018 um 09:56 schrieb Dave Pawson:
>
> https://tdg.docbook.org/tdg/5.1/
>
> Again, no seriesinfo element?
> IIRC the tdg is generated from the schema?
>
> Bob / Norm would need to state which is definitive.
>
> https://tdg.docbook.org/tdg/5.1/set.html is set any more
> helpful?
>
> regards
>
>
> On Sun, 18 Nov 2018 at 08:13, Bernhard Kleine 
> wrote:
>
>> Hi Dave,
>>
>> in https://tdg.docbook.org/tdg/5.1/ch02.html#s.bibliography there is the
>> seriesinfo tag, however, there is an validation error with seriesinfo:
>>
>> 
>>
>>
>> IsabelVarelaNieto
>> Julie
>> A.Chowen
>>
>> 
>> 
>> THE GROWTH HORMONE/INSULINLIKE
>> GROWTH FACTOR AXIS DURING DEVELOPMENT
>> 2005
>> 
>> 
>> ADVANCES IN EXPERIMENTAL MEDICINE AND
>> BIOLOGY
>> 
>> 10.1007/b106814
>> 9780387251196
>> 
>>
>> Regards
>>
>> Bernhard
>> Am 18.11.2018 um 07:31 schrieb Dave Pawson:
>>
>> https://tdg.docbook.org/tdg/5.1/
>>
>> There is no series element Bernhard?
>>
>> regards
>> On Sat, 17 Nov 2018 at 20:12, Bernhard Kleine  
>>  wrote:
>>
>> I found another identifier which I cannot find in docbook5: series
>>
>> 
>>
>> 
>> IsabelVarelaNieto
>> Julie 
>> A.Chowen
>>
>> 
>> 
>> THE GROWTH HORMONE/INSULINLIKE GROWTH 
>> FACTOR AXIS DURING DEVELOPMENT
>> 2005
>> ADVANCES IN EXPERIMENTAL MEDICINE AND BIOLOGY
>> 
>> 10.1007/b106814
>> 9780387251196
>> 
>>
>> Series throws an error in validation: 'not allowed'.
>>
>> I would like to know how to place the series field.
>>
>> Thanks a lot!
>>
>> Bernhard
>>
>> --
>> spitzhalde9
>> D-79853 lenzkirchbernhard.kle...@gmx.netwww.b-kleine.com, www.urseetal.net
>> -
>> thunderbird mit enigmail
>> GPG schlüssel: D5257409
>> fingerprint:
>> 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
>>
>>  --
>> spitzhalde9
>> D-79853 lenzkirchbernhard.kle...@gmx.netwww.b-kleine.com, www.urseetal.net
>> -
>> thunderbird mit enigmail
>> GPG schlüssel: D5257409
>> fingerprint:
>> 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
>>
>>
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.
>
> --
> spitzhalde9
> D-79853 lenzkirchbernhard.kle...@gmx.netwww.b-kleine.com, www.urseetal.net
> -
> thunderbird mit enigmail
> GPG schlüssel: D5257409
> fingerprint:
> 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
>
>

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

Re: [docbook-apps] Chapter number in a edited book

[Dave Pawson]

https://tdg.docbook.org/tdg/5.1/

Again, no seriesinfo element?
IIRC the tdg is generated from the schema?

Bob / Norm would need to state which is definitive.

https://tdg.docbook.org/tdg/5.1/set.html is set any more
helpful?

regards


On Sun, 18 Nov 2018 at 08:13, Bernhard Kleine 
wrote:

> Hi Dave,
>
> in https://tdg.docbook.org/tdg/5.1/ch02.html#s.bibliography there is the
> seriesinfo tag, however, there is an validation error with seriesinfo:
>
> 
>
>
> IsabelVarelaNieto
> Julie
> A.Chowen
>
> 
> 
> THE GROWTH HORMONE/INSULINLIKE
> GROWTH FACTOR AXIS DURING DEVELOPMENT
> 2005
> 
> 
> ADVANCES IN EXPERIMENTAL MEDICINE AND
> BIOLOGY
> 
> 10.1007/b106814
> 9780387251196
> 
>
> Regards
>
> Bernhard
> Am 18.11.2018 um 07:31 schrieb Dave Pawson:
>
> https://tdg.docbook.org/tdg/5.1/
>
> There is no series element Bernhard?
>
> regards
> On Sat, 17 Nov 2018 at 20:12, Bernhard Kleine  
>  wrote:
>
>
> I found another identifier which I cannot find in docbook5: series
>
> 
>
> 
> IsabelVarelaNieto
> Julie 
> A.Chowen
>
> 
> 
> THE GROWTH HORMONE/INSULINLIKE GROWTH 
> FACTOR AXIS DURING DEVELOPMENT
> 2005
> ADVANCES IN EXPERIMENTAL MEDICINE AND BIOLOGY
> 
> 10.1007/b106814
> 9780387251196
> 
>
> Series throws an error in validation: 'not allowed'.
>
> I would like to know how to place the series field.
>
> Thanks a lot!
>
> Bernhard
>
> --
> spitzhalde9
> D-79853 lenzkirchbernhard.kle...@gmx.netwww.b-kleine.com, www.urseetal.net
> -
> thunderbird mit enigmail
> GPG schlüssel: D5257409
> fingerprint:
> 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
>
>
>
>  --
> spitzhalde9
> D-79853 lenzkirchbernhard.kle...@gmx.netwww.b-kleine.com, www.urseetal.net
> -
> thunderbird mit enigmail
> GPG schlüssel: D5257409
> fingerprint:
> 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
>
>

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

Re: [docbook-apps] Chapter number in a edited book

[Dave Pawson]

https://tdg.docbook.org/tdg/5.1/

There is no series element Bernhard?

regards
On Sat, 17 Nov 2018 at 20:12, Bernhard Kleine  wrote:
>
> I found another identifier which I cannot find in docbook5: series
>
> 
>
> 
> IsabelVarelaNieto
> Julie 
> A.Chowen
>
> 
> 
> THE GROWTH HORMONE/INSULINLIKE GROWTH 
> FACTOR AXIS DURING DEVELOPMENT
> 2005
> ADVANCES IN EXPERIMENTAL MEDICINE AND BIOLOGY
> 
> 10.1007/b106814
> 9780387251196
> 
>
> Series throws an error in validation: 'not allowed'.
>
> I would like to know how to place the series field.
>
> Thanks a lot!
>
> Bernhard
>
> --
> spitzhalde9
> D-79853 lenzkirch
> bernhard.kle...@gmx.net
> www.b-kleine.com, www.urseetal.net
> -
> thunderbird mit enigmail
> GPG schlüssel: D5257409
> fingerprint:
> 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] List of tables (LoT)

[Dave Pawson]

do you actually need the  element in the doc body?
to position the toc's.

regartds
On Wed, 31 Oct 2018 at 10:50, Peter Fleck  wrote:
>
> HI Bernhard,
>
> http://www.sagehill.net/docbookxsl/TOCcontrol.html
>
> Check that you have included tables in the generate.toc parameter.
>
> For example:
>
> 
> appendix  toc,title
> article/appendix  nop
> article   toc,title
> book  toc,title,figure,table,example,equation
> chapter   toc,title
> part  toc,title
> preface   toc,title
> qandadiv  toc
> qandaset  toc
> reference toc,title
> sect1 toc
> sect2 toc
> sect3 toc
> sect4 toc
> sect5 toc
> section   toc
> set   toc,title
> 
>
>
> Peter
>
>
> On 31/10/2018 07:23, Bernhard Kleine wrote:
>
> I checked Docbook 5: the Definitive Guide and Docbook XSL: the complete
> Guide for LoT and I did not find it.
>
> Adding tocentry="1" to selected tables did not generate a List of Tables
> either. What do I miss? How to make it appear? How to place it?
>
> Regards
>
> Bernhard
>
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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 content review process/tools?

[Dave Pawson]

https://web.hypothes.is/

AFAIK - meant to 'comment' on html (and could be used that way.)
  Unsure if you want to mark up / comment on XML or some more 'user
friendly' version
of same?

Just a suggestion.

Dave
On Tue, 23 Oct 2018 at 17:53, Peter Desjardins
 wrote:
>
> Hi! Does anyone have a document content review process you can
> recommend? One that allows non-DocBook users to easily provide input
> and see each other's comments?
>
> My team uses Google docs for content review because reviewers can
> comment easily and see each other's input (this is at a company that
> uses Google email/docs). It's error-prone and tedious to transform
> DocBook content to Google documents though. I would love to find a
> better solution.
>
> We keep content in GitHub and I love the pull request content review
> tools there. Most of our subject matter experts do not use GitHub
> though, and it's not practical to review all DocBook content by
> reading the source XML.
>
> The conversion to Google doc format that works the best for us (so
> far) is DocBook > HTML > LibreOffice OpenDocument > Upload to Google
> drive and convert to Google doc format. We lose important formatting
> like bold for guilabel elements and bullet characters for
> itemizedlists disappear. Preparing a document for review is painful.
>
> Do you have a great DocBook-based review process?
>
> Thanks!
>
> Peter
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Combining para role templates

[Dave Pawson]

You might try attribute-sets?

they may do what you want?
Combine them as necessary at the xml to fo stage?

HTH


On Fri, 12 Oct 2018 at 15:16, Peter Fleck  wrote:
>
> I have a number of templates that add some formatting to xsl:fo, they
> are in the format of:
>
>   
>  
>
>  
>
>
>
>  
>
>  
>
>
> I want to be able to combine these various templates, something like this:
>
> ..
>
> But only the last "role" in the list gets applied to the output. Is this
> combining of roles feasible or do I need to write a combo template (for
> each combination)?
>
> priority="9">
>  
>
>  
>
>
> ..
>
> Thanks,
>
> Peter
>
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] How to make chemical structure automatically numbered

[Dave Pawson]

I.e. Semantically marked up docbook is clearly the wrong tool then.

Dave
On Fri, 12 Oct 2018 at 14:20, Peter Desjardins
 wrote:
>
> I think the table is adding valid semantic structure here. It allows the 
> figure numbering to exist at the Docbook level, not in SVG.
>
> Maybe use  elements inside an ? You could wrap the 
> informaltable in an example to give the entire set of diagrams a title.
>
> Peter
>
>   
> 
>   
> 
>   
>   Chemical One
>   
> 
>   
> 
>   
> 
>
>   
>   Chemical Two
>   
> 
>   
> 
>   
> 
> 
>   
> 
>   
>
>
> On Fri, Oct 12, 2018, 08:28 Thomas Schraitle  wrote:
>>
>> Hi,
>>
>> Am Freitag, 12. Oktober 2018, 14:12:15 CEST schrieb Bernhard Kleine:
>> > In my second mail to this threat a showed a complex table with
>> > structures, arrows labeling etc. I cannot envisage this without a table
>> > structure.
>>
>> As Dave already pointed out, a table might not be the appropriate way to
>> layout things.
>>
>> Have you considered SVG? With SVG (or any other vector format) you can do all
>> the fancy stuff (arrows, labeling etc.) that you need.
>>
>>
>> --
>> Gruß/Regards
>>   Thomas Schraitle
>>
>>
>>
>>
>> -
>> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
>> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] How to make chemical structure automatically numbered

[Dave Pawson]

I might question if the table (as layout) is necessary for your purposes?
  That would allow more flexibility in markup?
Dave
On Fri, 12 Oct 2018 at 12:57, Bernhard Kleine  wrote:
>
> Hi Jirka,
>
> This works but raises an error: equation must not occur among the
> children or descendants of table
>
> It transforms anyhow.
>
> Thanks for the hint.
>
> Bernhard
>
>
> Am 11.10.2018 um 16:45 schrieb Jirka Kosek:
> > On 11.10.2018 16:26, Bernhard Kleine wrote:
> >> unfortunately, using figures does not work in my example for the
> >> following reasons. It seems not possible to arrange a couple of figure
> >> inside a table: I show to you an example of a table containing
> >> structures and errors and labelling:
> > You can use  element for this. It can appear almost anywhere
> > in block context.
> >
>
> --
> spitzhalde9
> D-79853 lenzkirch
> bernhard.kle...@gmx.net
> www.b-kleine.com, www.urseetal.net
> -
> thunderbird mit enigmail
> GPG schlüssel: D5257409
> fingerprint:
> 08 B7 F8 70 22 7A FC C1 15 49 CA A6 C7 6F A0 2E D5 25 74 09
>
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] seek best practice using xinclude and imagedata/fileref

[Dave Pawson]

You might like a level of indirection provided by xml catalog.
http://www.sagehill.net/docbookxsl/WriteCatalog.html

Particularly if you think you may modify the layout as the system develops?

HTH
On Sun, 7 Oct 2018 at 00:01, Otto Hirr  wrote:
>
> Greetings,
>
> I'm looking for best practice on how to modularize using xinclude and access 
> image files using imagedata/fileref.
>
> I have a tree of resources, mostly various image files, such as scanned 
> documents.
> These are in a rather large tree of folders based upon either a kind of 
> date/time of occurrence or by topic.
>
> These need to be composed to tell a story.
>
> The textual content, along with inclusion of images, is placed in docbook xml 
> files that are also scattered around the tree.
>
> Some of the store line is time based and will have dcbkxml interspersed in 
> say the chronological folders.
> So a given year story line dcbkxml will be xinclude'ing subfolder dcbkxml 
> files, which have textual components and imagedata stored in current 
> directory or sub*directories.
>
> Other story lines are topical and span across the time line, hence the 
> dcbkxml will be in a Topic/subtopic folder, but needs access to image data 
> spread across the time line folders.
>
> After various attempts, I had settled on simply setting the xml:base to be 
> the root location of the whole tree, with a path from the top of the 
> file-system hierarchy.
>
> The enabled a simple referencing system:
>
> for  xinclude/href the path simply specified the relative location below the  
> xml:base location,
> for  imagedata/fileref the path likewise simply specified the relative 
> location below the  xml:base location
>
> It has been suggested that this is a less robust method, and one alternative 
> was to suggest setting a  xml:base using relative paths.
>
> At the time the method was being considered, the tree was not well defined, 
> and undergoing some changes.
>
> To have used relative paths, e.g.  xml:base="../../" would present problems 
> if a part of the tree needed to move.
>
> To do a global change across xml files of a specified relative path from the  
> xml:base would be easy.
> To do a global change across xml files of a specified relative path in the 
> form of "../../" would be problematic.
>
> The downside of the this whole approach is the  xml:base is in every dcbkxml 
> file, yet it is the same, so easy to change, i.e. global replacement, should 
> the root need to be relocated.
>
> What is the best practice for managing this?
>
> Best regards,
>
> ..Otto
>
>


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Catching up.

[Dave Pawson]

Typo still there Bob, from Sourceforge?

VERSION file

docbook-xsl-ns
1.78.1
9732
$Revision: 9732 $
$URL:
svn+ssh://bobstay...@svn.code.sf.net/p/docbook/code/trunk/xsl/VERSION.xsl
$

On 30 June 2018 at 21:52, Bob Stayton  wrote:
> Hi Dave,
>
> You can still get docbook-xsl-ns-1.79.1 (the namespaced version for DocBook
> 5) from the SourceForge site:
>
>   https://sourceforge.net/projects/docbook/files/docbook-xsl-ns/1.79.1/
>
> The stylesheets have never included the schema files, which are available
> from docbook.org:
>
>   https://docbook.org/xml/5.1/
>
> Sorry for the disarray on the GitHub site.  Stefan Seefeld did a great job
> transitioning from SourceForge, but I need to make more content
> improvements.  I'm finally getting back to DocBook work, so you can expect a
> new XSL release and better doc, coming soon.
>
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
>
> On 6/30/2018 10:31 AM, Dave Pawson wrote:
>
> Sorry, docbook 5 I believe.
>
> 1.79.1 from
> https://github.com/docbook/xslt10-stylesheets/releases/tag/release%2F1.79.1
>
> Assume complete with schema etc.
>
> Thanks Bob
>
> regards
>
> On 30 June 2018 at 17:34, Bob Stayton  wrote:
>
> Hi Dave,
>
> Download the 1.79.1 zip file.  Are you using DocBook 4 or 5?
>
> https://github.com/docbook/xslt10-stylesheets/releases/tag/release%2F1.79.1
>
> There is a 1.79.2 release, but it is functionally the same as 1.79.1 but was
> built differently and a few issues came up with it, so I would use 1.79.1.
>
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
>
> On 6/30/2018 6:59 AM, Dave Pawson wrote:
>
> Some oddities with my current (quite old) stylesheets.
> What is the preferred install method please?
>
> git clone / download zip?
>
> Is build needed?
>
> Of note:
> xslt10-stylesheets-master/  seems to differ
> from older installs?
>
> Is any of this documented please?
>
>
> TiA
>
>
>
>
>
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] typo + Missing files? 1.79.1

[Dave Pawson]

Sorry Bob, my bad.
I'll try again.
   Fun playing with param.xweb and tangle.xsl!

regards

On 1 July 2018 at 16:53, Bob Stayton  wrote:
> Hi Dave,
>
> Yes, param.xsl is built prior to making a distribution.  So you are looking
> at the source directories, not the distribution.  As I said, you can
> download the already-built distribution from here:
>
>   https://sourceforge.net/projects/docbook/files/docbook-xsl-ns/1.79.1/
>
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
>
> On 7/1/2018 1:07 AM, Dave Pawson wrote:
>
> Typo?
>
> file: VERSION
> docbook-xsl
> 1.78.1
> 9732
> $Revision: 9732 $
> $URL:
> svn+ssh://bobstay...@svn.code.sf.net/p/docbook/code/trunk/xsl/VERSION.xsl
> $
>
>
> file: html/docbook.xsl
>
> 
> 
> etc
>
> param.xsl not provided in the download - is it built please?
>
>
> regards
>
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] typo + Missing files? 1.79.1

[Dave Pawson]

Typo?

file: VERSION
docbook-xsl
1.78.1
9732
$Revision: 9732 $
$URL:
svn+ssh://bobstay...@svn.code.sf.net/p/docbook/code/trunk/xsl/VERSION.xsl
$


file: html/docbook.xsl



etc

param.xsl not provided in the download - is it built please?


regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Relative layout

[Dave Pawson]

In the 1.79.1 xsl stylesheets,
I see


(root)
   xsl   ;; then one of
   xsl-saxon
   xsl-libxslt
   xsl-xalan

Is this the only required layout please?
xsl-saxon for the saxon java extensions etc.

Is there any common practice for schema inclusion
in such a layout?
E.g.
(root)
   docbook.5.2b4
   docbook.5.1
   etc?

regards




-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Catching up.

[Dave Pawson]

Thanks Bob.

I'll try and do as Niels said and pull the stylesheets from 79.1

regards

On 30 June 2018 at 21:52, Bob Stayton  wrote:
> Hi Dave,
>
> You can still get docbook-xsl-ns-1.79.1 (the namespaced version for DocBook
> 5) from the SourceForge site:
>
>   https://sourceforge.net/projects/docbook/files/docbook-xsl-ns/1.79.1/
>
> The stylesheets have never included the schema files, which are available
> from docbook.org:
>
>   https://docbook.org/xml/5.1/
>
> Sorry for the disarray on the GitHub site.  Stefan Seefeld did a great job
> transitioning from SourceForge, but I need to make more content
> improvements.  I'm finally getting back to DocBook work, so you can expect a
> new XSL release and better doc, coming soon.
>
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
>
> On 6/30/2018 10:31 AM, Dave Pawson wrote:
>
> Sorry, docbook 5 I believe.
>
> 1.79.1 from
> https://github.com/docbook/xslt10-stylesheets/releases/tag/release%2F1.79.1
>
> Assume complete with schema etc.
>
> Thanks Bob
>
> regards
>
> On 30 June 2018 at 17:34, Bob Stayton  wrote:
>
> Hi Dave,
>
> Download the 1.79.1 zip file.  Are you using DocBook 4 or 5?
>
> https://github.com/docbook/xslt10-stylesheets/releases/tag/release%2F1.79.1
>
> There is a 1.79.2 release, but it is functionally the same as 1.79.1 but was
> built differently and a few issues came up with it, so I would use 1.79.1.
>
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
>
> On 6/30/2018 6:59 AM, Dave Pawson wrote:
>
> Some oddities with my current (quite old) stylesheets.
> What is the preferred install method please?
>
> git clone / download zip?
>
> Is build needed?
>
> Of note:
> xslt10-stylesheets-master/  seems to differ
> from older installs?
>
> Is any of this documented please?
>
>
> TiA
>
>
>
>
>
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Catching up.

[Dave Pawson]

Sorry, docbook 5 I believe.

1.79.1 from 
https://github.com/docbook/xslt10-stylesheets/releases/tag/release%2F1.79.1

Assume complete with schema etc.

Thanks Bob

regards

On 30 June 2018 at 17:34, Bob Stayton  wrote:
> Hi Dave,
>
> Download the 1.79.1 zip file.  Are you using DocBook 4 or 5?
>
> https://github.com/docbook/xslt10-stylesheets/releases/tag/release%2F1.79.1
>
> There is a 1.79.2 release, but it is functionally the same as 1.79.1 but was
> built differently and a few issues came up with it, so I would use 1.79.1.
>
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
>
> On 6/30/2018 6:59 AM, Dave Pawson wrote:
>
> Some oddities with my current (quite old) stylesheets.
> What is the preferred install method please?
>
> git clone / download zip?
>
> Is build needed?
>
> Of note:
> xslt10-stylesheets-master/  seems to differ
> from older installs?
>
> Is any of this documented please?
>
>
> TiA
>
>
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Re: Catching up.

[Dave Pawson]

ion/docbook/xslt10-stylesheets-master 18:09 >

On 30 June 2018 at 17:41, Bob Stayton  wrote:
> The build doc on Github is still in development, and it will explain ~/.xmlc
> when it is done.  In the mean time, here is a link to the sample file:
>
> https://github.com/docbook/xslt10-stylesheets/blob/master/.travis/xmlc
>
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
>
> On 6/30/2018 7:03 AM, Dave Pawson wrote:
>
> Tried a build (Fedora 64 bit)
>
>  >  make XSLTENGINE=saxon
> make -C xsl
> make[1]: Entering directory
> '/data/installation/docbook/xslt10-stylesheets-master/xsl'
> for d in common lib html fo manpages htmlhelp javahelp eclipse
> roundtrip slides website extensions xhtml xhtml-1_1 webhelp xhtml5
> epub3 ; do make -C $d; done
> make[2]: Entering directory
> '/data/installation/docbook/xslt10-stylesheets-master/xsl/common'
> /data/installation/docbook/xslt10-stylesheets-master/buildtools/xslt
> -saxon
> /data/installation/docbook/xslt10-stylesheets-master/gentext/locale/en.xml
> /data/installation/docbook/xslt10-stylesheets-master/gentext/xsl/xsl.xsl
> af.xml locale.file=af.xml
> Cannot read config: /home/dpawson/.xmlc
>
>
> What is expected at ~/.xmlc please?
>
> Dave
>
> On 30 June 2018 at 14:59, Dave Pawson  wrote:
>
> Some oddities with my current (quite old) stylesheets.
> What is the preferred install method please?
>
> git clone / download zip?
>
> Is build needed?
>
> Of note:
> xslt10-stylesheets-master/  seems to differ
> from older installs?
>
> Is any of this documented please?
>
>
> TiA
>
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.
>
>
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Re: Catching up.

[Dave Pawson]

Tried a build (Fedora 64 bit)

 >  make XSLTENGINE=saxon
make -C xsl
make[1]: Entering directory
'/data/installation/docbook/xslt10-stylesheets-master/xsl'
for d in common lib html fo manpages htmlhelp javahelp eclipse
roundtrip slides website extensions xhtml xhtml-1_1 webhelp xhtml5
epub3 ; do make -C $d; done
make[2]: Entering directory
'/data/installation/docbook/xslt10-stylesheets-master/xsl/common'
/data/installation/docbook/xslt10-stylesheets-master/buildtools/xslt
-saxon 
/data/installation/docbook/xslt10-stylesheets-master/gentext/locale/en.xml
/data/installation/docbook/xslt10-stylesheets-master/gentext/xsl/xsl.xsl
af.xml locale.file=af.xml
Cannot read config: /home/dpawson/.xmlc


What is expected at ~/.xmlc please?

Dave

On 30 June 2018 at 14:59, Dave Pawson  wrote:
> Some oddities with my current (quite old) stylesheets.
> What is the preferred install method please?
>
> git clone / download zip?
>
> Is build needed?
>
> Of note:
> xslt10-stylesheets-master/  seems to differ
> from older installs?
>
> Is any of this documented please?
>
>
> TiA
>
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Catching up.

[Dave Pawson]

Some oddities with my current (quite old) stylesheets.
What is the preferred install method please?

git clone / download zip?

Is build needed?

Of note:
xslt10-stylesheets-master/  seems to differ
from older installs?

Is any of this documented please?


TiA


-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Fwd: xslt2 stylesheets experience?

[Dave Pawson]

On 5 June 2018 at 13:58, Jirka Kosek  wrote:
> On 4.6.2018 17:14, Dave Pawson wrote:
>> AFAIK (speak up Jirka!) they have not been completely ported to XSLT 2.0
>>  Most, but not all of the templates.
>
> Norm is one who wrote most of them, so you should ask him ;-)
>
> You should give it a try. There is no 1:1 correspondence between
> available features -- there are some features missing in XSLT 2.0 based
> stylesheets, but also there many new ones. Depends on what you need.
> I think that if you target HTML output then you should be in general
> satisfied with XSLT 2.0 stylesheets. XSLT 2.0 stylesheets for XSL-FO has
> never been finished.

Guess please? Norm, Jirka
html: 80% finished?
PDF: 50%

Any better guesses

regards



>
> Jirka
>
> --
> --
>   Jirka Kosek  e-mail: ji...@kosek.cz  http://xmlguru.cz
> --
>  Professional XML and Web consulting and training services
> DocBook/DITA customization, custom XSLT/XSL-FO document processing
> --
> Bringing you XML Prague conferencehttp://xmlprague.cz
> ------
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Gradle to crave?

[Dave Pawson]

https://so.nwalsh.com/2018/03/05/easy

An interesting read on building docbook.

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Fwd: xslt2 stylesheets experience?

[Dave Pawson]

AFAIK (speak up Jirka!) they have not been completely ported to XSLT 2.0
 Most, but not all of the templates.

If you want to help???

regards

On 4 June 2018 at 14:54, Tim Arnold  wrote:
> Hi again,
> Just checking to make sure--is nobody on the list using the XSLT2.0
> stylesheets in production yet?
>
> I'm pretty conservative when it comes to code changes and I don't want to be
> on the bleeding edge!
>
>
> thanks,
> --Tim
>
> -- Forwarded message --
> From: Tim Arnold 
> Date: Fri, Jun 1, 2018 at 9:25 AM
> Subject: xslt2 stylesheets experience?
> To: DocBook Apps 
>
>
> hi,
> I've been using the xslt1 docbook 5 stylesheets for a few years. Works fine,
> and I have a medium size customization layer. But the time has come to
> rewrite some of my templates (technical debt accrued last year).
>
> I wonder about switching to the xslt2 stylesheets since I'm recoding anyway.
> Has anyone been through the process and have any comments or tips?
>
> thanks,
> --Tim
>
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Re: XML databases

[Dave Pawson]

Declaration: I'm not a db user (never found a real use for them).
My docbook (primary) use is the accretion of files over time.
Mostly less than a few hundred.
Build tool is plain text (ant / xslt).

My logic (not wishing to call Norm a liar) is that a file system can fail
(I do take care).
Adding another point of failure (the db logic...) makes a db 'worse' i.e.
more likely to fail.

I get indexing via XSLT (thanks docbook team) where I need it.
I believe Norm when he says that a db indexes 'better' (for some
definition of better - what of secondary terms / index term != content?)

So for my 'small' (relative) number of files, coupled with my db ignorance
(I did spend time once playing with one of the XML db products, v.easy
to import)
I'm biassed towards simplicity... One less point of failure.

I'm sure there is a gray area in between high file count / low complexity etc
where both are 'equal'. Forward planning perhaps?

Not wishing to tempt fate, I won't say "No failures in n years!"  :-)

Dave




On 7 April 2018 at 09:06, Peter Fleck <peterfl...@gmail.com> wrote:
> This is a useful discussion.
>
> We make extensive use of git, especially at the beginning of a project.
>
> Do you have any tips for integrating the database approach with a vcs like
> git?
>
> Peter
>
>
> On 06/04/2018 12:35, Norman Walsh wrote:
>>
>> Camille Bégnis <cami...@neodoc.biz> writes:
>>>
>>> thanks for this interesting discussion, what DB would you use or suggest
>>> for XML?
>>
>> I’m strongly biased to suggest a particular commercial database, one
>> that you can download and use for free from developer.marklogic.com.
>>
>> But I hear good things about BaseX as well and eXist has been around
>> for ages.
>>
>>  Be seeing you,
>>norm
>>
>
>
> -----
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Re: XML databases

[Dave Pawson]

Thanks Norm.
   It's the fear of losing it all that holds me back.

Agree with your logic. Good for thousands (hard to index)
Less so for hundreds (I use db indexing)

Also agree with the backup (in either case).

I'd hate to have the data in a corrupt database

regards

On 5 April 2018 at 16:59, Norman Walsh <n...@nwalsh.com> wrote:
> Dave Pawson <dave.paw...@gmail.com> writes:
>> What use cases are there for dropping a few hundred
>> XML files into a (purpose built for XML) database?
>
> I put XML in a database for the ability to index and search it,
> primarily. Here’s a screenshot of my personal “evernote clone” that
> stores a combination of XML and other formats.
>
>
>
> The documents that contained the word DocBook (stemmed appropriately,
> so DocBooking and DocBooked, if they were words, would also have
> matched) are found quickly. The facets are constructed from other
> fields in the those documents.
>
> The ability to quickly search and use indexes to build facets allows
> me to make an application that would be more difficult without a
> database.
>
>>  I can see a risk (db failure) above the file system
>> failure risks.
>
> Backups. You want to have backups!
>
>> Has anyone done that assessment and decided in
>> favour of a database over the file system?
>
> For a few hundred documents, it’s probably hard to make a compelling
> argument for a database unless you want to build applications like the
> one I described above.
>
> For a few hundred thousand documents, ti’s probably hard to make a
> compelling case for the filesystem.
>
> Be seeing you,
>   norm
>
> --
> Norman Walsh <n...@nwalsh.com> | The finest amusements are the most
> http://nwalsh.com/| pointless ones.--Jacques Chardonne
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] XML databases

[Dave Pawson]

Just wondering.
Recent announcement of BaseX update.
What use cases are there for dropping a few hundred
XML files into a (purpose built for XML) database?
 I can see a risk (db failure) above the file system
failure risks.

Has anyone done that assessment and decided in
favour of a database over the file system?

Just curious.

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Re: Using the DocBook XSLT 2.0 stylesheets with Gradle

[Dave Pawson]

On 6 March 2018 at 09:06, Niels Müller Larsen <neinalw...@gmail.com> wrote:
> Sorry to intrude.
> The cross platform comment on bash triggered me.
> My students use a bash shell on Windows. It is included, I think, in the git 
> download for Windows.
>
> /Niels


Yes, though I do wonder how many of todays Windows users would be
comfortable working
with a bash script Niels? CS students  yes, others, I'm less sure.

 It was probably quite a while since Norm used Windows!

regards Dave


>
> Greetings
> Niels Müller Larsen
> Senior Lecturer IBA Kolding
> Bachelor of Web Development Program
>
>
>
>> On 5 Mar 2018, at 17.54, Norman Walsh <n...@nwalsh.com> wrote:
>>
>> Dave Pawson <dave.paw...@gmail.com> writes:
>>> I stopped at "you don't have to understand it" Norm?
>>> ... rude words.
>>
>> Apologies. No disrespect intended.
>>
>>> I got as far as ant for builds. I can understand most of that.
>>> Bash script... similar? Maybe
>>> gradle? Wozzat.
>>>
>>> Why make it deeper than needs be?
>>
>> Well…I’m not sure I agree that it’s deeper than it needs to be.
>> I’ve been building toolchains for ages: make, ant, bash, perl,
>> ruby, python, sbt, etc. etc. etc.
>>
>> I settled on Gradle because of the advantages I outlined in that
>> posting: it’s significantly better than ant for dealing with Maven and
>> for extensibility; it’s cross platform (unlike bash); it’s relatively
>> easy to install on most platforms (unlike make, perl, etc.); and it
>> transparently deals with a whole lot of the backend infrastructure.
>>
>>    Be seeing you,
>>  norm
>>
>> --
>> Norman Walsh <n...@nwalsh.com> | The finest amusements are the most
>> http://nwalsh.com/| pointless ones.--Jacques Chardonne



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Using the DocBook XSLT 2.0 stylesheets with Gradle

[Dave Pawson]

Fair comment David.

Tempted to ask just how many are in that camp vs  like us who do
odd things with docbook.
(for some defn of odd).

My position.
  1. I don't stretch the schema (db simple would likely suffice)
  2. I haven't updated my stylesheets in ages
  3. I build html / pdf with svg ... (500k + words)
  4. I want (need?) to validate as an option.
  5. All files are on my hard drive

ant lets me pick / choose bits|all
Am I odd? Minority? Majority?

 Who needs steenkin
esisinternet 

Sorry - that quote stuck from dsssl days Norm - bet you've forgotten it.

regards



On 5 March 2018 at 17:24, David Cramer <da...@thingbag.net> wrote:
> On 3/5/18 10:14 AM, Dave Pawson wrote:
>>
>> I got as far as ant for builds. I can understand most of that.
>>
>> Bash script... similar? Maybe
>>
>> gradle? Wozzat.
>>
>> Why make it deeper than needs be?
>
>
> Dave,
>
> The idea is to make it super easy for someone (e.g. an author) who just
> wants to build the doc. They don't want to install a ton of stuff _at the
> right version_ and keep track of it.
>
> From an end-user's perspective, setting up the whole tool chain and building
> the doc at most three steps:
>
> # You only have to do this once (or use apt-get/yum or whatever windows
> # users do to install software):
> brew install gradle
>
> # Get DocBook xml source from whatever source control system
> # it lives in...
> git clone  && cd somedoc
>
> # This installs the DocBook toolchain and builds the doc:
> gradle somedoc
>
> Even as new versions of the underlying tools come out, "somedoc" continues
> to build because your gradle file indicates what versions it depends on.
> However, you easily can switch to newer versions if you need to.
>
> Regards,
> David
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Re: Using the DocBook XSLT 2.0 stylesheets with Gradle

[Dave Pawson]

On 5 March 2018 at 16:54, Norman Walsh <n...@nwalsh.com> wrote:
> Dave Pawson <dave.paw...@gmail.com> writes:
>> I stopped at "you don't have to understand it" Norm?
>> ... rude words.
>
> Apologies. No disrespect intended.

None taken Norm, just a bit... odd?
Especially with our docbook users!

>
>> I got as far as ant for builds. I can understand most of that.
>> Bash script... similar? Maybe
>> gradle? Wozzat.
>>
>> Why make it deeper than needs be?
>
> Well…I’m not sure I agree that it’s deeper than it needs to be.
> I’ve been building toolchains for ages: make, ant, bash, perl,
> ruby, python, sbt, etc. etc. etc.
>
> I settled on Gradle because of the advantages I outlined in that
> posting: it’s significantly better than ant for dealing with Maven and
> for extensibility; it’s cross platform (unlike bash); it’s relatively
> easy to install on most platforms (unlike make, perl, etc.); and it
> transparently deals with a whole lot of the backend infrastructure.

>From my reading, it sounds like it works, for Norms setup?


My 2009 build (ant) still works.

I do wonder how wide the network of users are?
  What versions are in use etc?

Hence how gradle / maven etc will work for us?

I'll shut up now.

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Using the DocBook XSLT 2.0 stylesheets with Gradle

[Dave Pawson]

I stopped at "you don't have to understand it" Norm?

... rude words.

I got as far as ant for builds. I can understand most of that.

Bash script... similar? Maybe

gradle? Wozzat.

Why make it deeper than needs be?

Dave




On 5 March 2018 at 15:34, Norman Walsh <n...@nwalsh.com> wrote:
> Hello,
>
> Of possible interest to the readers of this list:
>
>   https://so.nwalsh.com/2018/03/05/easy
>
> (I found a couple of bugs so there’ll be updates within a day or two,
> but I still think it might be of interest.)
>
> Be seeing you,
>   norm
>
> --
> Norman Walsh <n...@nwalsh.com> | Sun System & Network Admin manualIt is
> http://nwalsh.com/| important to realize that any lock can
>       | be picked with a big enough hammer.



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.

-
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] Re: Including a variable in an xlink:href value

[Dave Pawson]

Is this a case of the simpler the docbook, the more chance of
understanding what's happening?
Add a 'framework', and as Mark explains you need to understand two
levels of complexity?

I rate docbook as 'hard sums', and fight shy of adding more - though I'm sure
others find it adds its own benefits.

regards

On 10 January 2018 at 13:55, Mark Craig <mark.cr...@gmail.com> wrote:
> Hello Janice,
>
> Since you're using Maven, as a workaround you could use bare Maven
> expressions and perform Maven filtering on the source before using the
> docbkx plugin.
>
> Maven filtering replaces expressions like ${project.version} with the values
> of their Maven properties. For example, in a 1.0.0-SNAPSHOT project,
> ${project.version} would be replaced with 1.0.0-SNAPSHOT. Unlike docbkx,
> which works on the XML, Maven filtering works with the files as if they were
> plain text.
>
> In the source, no need to figure out how to embed a processing instruction
> inside an attribute value. Just use the Maven expression. In your example:
> xlink:href="https://mycompany.com/directory/file-name-${project.version}.tar.gz;
>
> In the  of your Maven pom.xml:
>
> Use the Maven resources plugin before docbkx-tools to make a filtered copy
> of your DocBook sources. You can use the
> https://maven.apache.org/plugins/maven-resources-plugin/copy-resources-mojo.html
> goal to be able to set the output directory, ignore image files, escape
> literal ${...}s in your docs, etc.
> Configure docbkx-tools to use the filtered sources in the output directory
> of the Maven resources plugin, rather than the original (unfiltered)
> sources.
>
> Hope it helps. Regards,
>
> Mark
>
>
> On Wed, Jan 10, 2018 at 2:10 PM, Janice Manwiller <jan...@sqrrl.com> wrote:
>>
>> I probably should clarify that the  notation is
>> specific to the Maven docbkx plugin, which we use to generate the output.
>>
>> I also tried to create an entity file containing a version entity using
>> the info from http://www.sagehill.net/docbookxsl/Db5Entities.html. When I
>> tried to add the DOCTYPE element to refer back to the entity file, Oxygen
>> rejected it as not being well-formed. So I couldn't test whether I could use
>> an entity reference to incorporate the version number in the link target.
>>
>>
>>
>> On Thu, Jan 4, 2018 at 11:14 AM, Janice Manwiller <jan...@sqrrl.com>
>> wrote:
>>>
>>> In my docs, I currently use  to indicate to
>>> insert the current product version number into the text.
>>>
>>> I'm adding a link to a URL that includes the version number in the file
>>> name, but if I try to include the version number variable in the link, like:
>>>
>>> xlink:href="https://mycompany.com/directory/file-name->> ${project.version}?>.tar.gz"
>>>
>>> I get an error that the link cannot include the < character.
>>>
>>> Is there any way to include the variable in the link, so that the version
>>> number portion of the URL is populated automatically? Right now I'm stuck
>>> having the link be to the enclosing directory, with the file name referred
>>> to separately:
>>>
>>> file-name-.tar.gz in
>>> >> xlink:href="https://mycompany.com/directory/;>https://mycompany.com/directory/
>>>
>>> Thanks,
>>>
>>> Janice
>>
>>
>>
>>
>> --
>> Janice Manwiller
>> Principal Technical Writer
>> Sqrrl Data, Inc.
>> www.sqrrl.com | @SqrrlData
>
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] REST API description

[Dave Pawson]

http://vrici.lojban.org/~cowan/XML/tagsoup/#tsaxon is available if you want to
use XSLT with an html source.

Dave

On 7 December 2017 at 21:25, Peter Desjardins
<peter.desjardins...@gmail.com> wrote:
> I'm using NPM Bootprint (https://www.npmjs.com/package/bootprint) to
> convert OpenAPI YAML definititions to HTML. Then I use Jsoup
> (https://jsoup.org/) to convert the resulting HTML to XHTML. Then I
> use XSLT to insert the XHTML API documentation into my DocBook
> webhelp.
>
> I'm not too happy about this Rube Goldberg system. An OpenAPI YAML to
> DocBook utility would be so handy.
>
> Peter
>
> On Thu, Dec 7, 2017 at 3:45 PM, Jan Tosovsky <j.tosov...@email.cz> wrote:
>> On 2017-12-07 David Cramer wrote:
>>> On 2017-12-05 Jan Tosovsky wrote:
>>> > Is there any recommended DocBook tag set for describing REST API?
>>>
>>> I don't think DocBook is the right vocabulary for modeling a REST API.
>>> There's an XML schema, WADL (Web Application Description Language) that
>>> is designed for that
>>> ...
>>> These days non-xml vocabularies for modeling REST apis are more popular.
>>> Each has its own strengths and weaknesses, depending on your needs.
>>>
>>
>> I've ended up in very similar conclusion :-)
>>
>> I haven't heard about WADL yet, but right now I am investigating ways how to 
>> convert Swagger's OpenAPI (subset) to my DocBook structure.
>>
>> Jan
>>
>>
>> -
>> 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
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] change default HTML encoding to UTF-8

[Dave Pawson]

No Bob, no change here, though I would benefit (on occasion) from utf-8

regards

On 14 August 2017 at 17:48, Bob Stayton  wrote:
> We have a bug report suggesting that the default output encoding for the
> DocBook html stylesheet be changed from ISO-8859-1 to UTF-8.  Note this only
> applies to the original HTML 4 output from the "html" directory. The "xhtml"
> and "xhtml5" outputs already output UTF.
>
> The original HTML 4 standard said ISO-8859-1 was the default encoding, but
> that UTF-8 would be acceptable.  It isn't difficult for a user to change the
> output to UTF-8, but it does require a customization.  The question here is
> whether to change the default output encoding to UTF-8.
>
> This would change the HTML output to replace character references like
> 

Re: [docbook-apps] Gradle build cross-platform - trouble with Saxon 6.5.5 params under Windows

[Dave Pawson]

Worth asking on the docbook-apps list Peter?
I use 2 for other parts, but for my main (quite large) docbook build I use 1.
  I use ant.
HTH

On 10 August 2017 at 05:14, Peter Desjardins
<peter.desjardins...@gmail.com> wrote:
> Hi! I have a working Gradle build system that transforms DocBook 5.1
> (using an assembly) to a few output mediums. I'm using Saxon 6.5.5 and
> the DocBook XSLT 1.0 stylesheets (latest version). When a new writer
> chose to use Windows, the Gradle build broke when she ran it locally.
>
> Problem #1 is that the Gradle exec task that assembles the DocBook
> assembly using Saxon 6.5.5 won't work under Windows. Saxon complains
> that there's "no output file name." Gradle has a terrible problem
> consuming the "-o myoutputfile.xml" argument.  If I present the "-o"
> argument separately, Saxon claims that the output file name is
> missing. If I present a "-o myoutputfile.xml" argument, Saxon
> complains that  "-o myoutputfile.xml" isn't a recognized argument. Has
> anyone built a Gradle Exec task that runs Saxon 6.5.5 on Windows? It
> works just fine on Linux and MacOS.
>
> Question #2 is: Has anyone had trouble using Saxon9HE with the DocBook
> XSLT v1.0 stylesheets? The way the arguments for the later version of
> Saxon are structured work much better with Gradle.
> (-o:myoutputfile.xml.)
>
> I'm considering switching to the DocBook XSLT 2.0 stylesheets to work
> around this problem. That avoids mixing Saxon9HE with the DocBook XSLT
> 1.0 stylesheets. Has anyone had any trouble migrating to XSLT 2.0?
>
> Thanks for your help!
>
> Peter
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] xslt 3.0

[Dave Pawson]

AFAIK current stylesheets are 1.0?

My setup has absolute docbook ss references

Asking on xsl-list Mike offers





which would let me define the 'disk' (which in my case will change)
then change in one place (good indirection?)

Except... this is an xslt 3.0 feature.

MK says It doesn't even warn you any more (there's no need for the
warning in 3.0 because the level of compatibility is very high).

Has anyone run saxon with 3.0 defined on the docbook stylesheets?

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Do not process.

[Dave Pawson]

I'm using docbook for a committee meetings minutes.
These are to be made public, but some sections (various
elements, appendix down to para) require to be not
shown (not processed through to PDF).

Suggestions please for a suitable attribute (to add or use),
then match on *[@redacted] etc

TiA

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] fo output, simplesect/title

[Dave Pawson]

Thanks Bob. It seems to be falling back to a default font,
changed that and it went away.
  There's a font selection somewhere which is catching me out.
I'll chase it further and let you know if I find it.

regards

On 28 June 2017 at 18:00, Bob Stayton <b...@sagehill.net> wrote:
> Hi Dave,
> The title in simplesect should be handled exactly as for other section
> titles at the equivalent level.  There is no separate attribute-set for it.
> Do you get the same font for regular section titles?
>
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
>
> On 6/28/2017 5:52 AM, Dave Pawson wrote:
>>
>> Where is the font selected please?
>> Parameter?
>> I'm using "title.font.family yet getting a font
>> from some fallback (serif).
>>
>> Suggestions please
>>
>> regards
>>
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] fo output, simplesect/title

[Dave Pawson]

Where is the font selected please?
Parameter?
I'm using "title.font.family yet getting a font
from some fallback (serif).

Suggestions please

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Section titles bottom of a print page when there is as subtitle

[Dave Pawson]

On 22 May 2017 at 14:45, sknorr <skn...@suse.de> wrote:
> Hi all,
>
> so, we have a similar problem in our documents.
> And just adding a page break before each section does not
> really cut it imo: I would like to allow
> multiple sections to start on the same page.
> However, what I'd like to avoid is sections in the
> bottom 25% of the page.

Can't be done in xsl-fo.

>
> Additionally, the dbfo-need-height PI in the past
> was not compatible with FOP


> I wonder if there is maybe some hacky solution involving
> an invisible fo:block with height=25% page height?

Not to my knowledge.

regards


>
> Stefan.
>
>
> --
> SUSE LINUX Products GmbH, Maxfeldstraße 5, D-90409 Nürnberg
> Geschäftsführer: Jeff Hawn, Jennifer Guild, Felix Imendörffer
> HRB 16746 (Amtsgericht Nürnberg)



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Section titles bottom of a print page when there is as subtitle

[Dave Pawson]

Yes, though looking at it, it may be easier
to update section.level1.properties
which calls section.properties.
  That looks like a good place to add your 'specials'

HTH

On 22 May 2017 at 10:46, Peter Fleck <peterfl...@gmail.com> wrote:
> Sorry Dave, I'm struggling.
>
> You mean  in this stylesheet -
> http://cdn.docbook.org/release/xsl/current/fo/sections.xsl ?
>
> Thanks,
>
> Peter
>
>
>
> On 22/05/17 09:10, Dave Pawson wrote:
>>
>> find the section template.
>> Add break-before='page' to a custom template
>> based on that. Refine selection further if needed?
>>
>> regards
>>
>> On 22 May 2017 at 07:48, Peter Fleck <peterfl...@gmail.com> wrote:
>>>
>>> Hi,
>>>
>>> How do you stop section titles being at the bottom of a print page when
>>> there is as subtitle? ie. If there isn't space for at least one or two
>>> lines
>>> for the following paragraph the section title moves to the following
>>> page.
>>>
>>> Here's the xml:
>>>
>>> 
>>>   
>>>  The Title
>>>  The Subtitle
>>> 
>>>   
>>>
>>> So at the bottom of the page is the  followed by the 
>>> and
>>> then the  starts on a new page.
>>>
>>> I'm using 1.79.2 with Apache FOP 2.2.
>>>
>>> I know I can use  but would rather not have to
>>> put it in XML if there is an XSL solution.
>>>
>>> Thanks,
>>>
>>> Peter
>>>
>>> -
>>> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
>>> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>>>
>>
>>
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Section titles bottom of a print page when there is as subtitle

[Dave Pawson]

find the section template.
Add break-before='page' to a custom template
based on that. Refine selection further if needed?

regards

On 22 May 2017 at 07:48, Peter Fleck <peterfl...@gmail.com> wrote:
> Hi,
>
> How do you stop section titles being at the bottom of a print page when
> there is as subtitle? ie. If there isn't space for at least one or two lines
> for the following paragraph the section title moves to the following page.
>
> Here's the xml:
>
> 
>  
> The Title
> The Subtitle
> 
>  
>
> So at the bottom of the page is the  followed by the  and
> then the  starts on a new page.
>
> I'm using 1.79.2 with Apache FOP 2.2.
>
> I know I can use  but would rather not have to
> put it in XML if there is an XSL solution.
>
> Thanks,
>
> Peter
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] tagged and accessible PDF document with DocBook

[Dave Pawson]

On 27 April 2017 at 17:49, Tony Graham <tgra...@antenna.co.jp> wrote:

> Which brings me to...
>
> 8. You have a comment about preferring a flat rather than nested ToC
> structure.  You can represent a hierarchical ToC structure in Tagged
> PDF, but I don't know whether flat or hierarchical is better for people
> using assistive technology.  Dave Pawson may know.

I think 'visual' presentation isn't an issue?
When text is read by a machine, one line with indent x is the same as
one with indent y.

I'd suggest a flat structure would be more readily accessible, unless
each entry is numbered etc?

HTH



>
> Regards,
>
>
> Tony Graham.
> --
> Senior Architect
> XML Division
> Antenna House, Inc.
> 
> Skerries, Ireland
> tgra...@antenna.co.jp
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] tagged and accessible PDF document with DocBook

[Dave Pawson]

;> feature, and DocBook XSL had to support all three extensions.  When XSL
>>>> 1.1 standardized the markup for bookmarks, then all the XSL-FO
>>>> processors eventually implemented that standard and so did DocBook XSL.
>>> ...
>>>> I would be interested in adding PDF tagging to DocBook XSL.  It would
>>>> help if there were a clear spec for how to do so.  If I have to figure
>>>> it out for each of three XSL-FO processors, that's going to take some
>>>> time.
>>>
>>> There is no current W3C Working Group for XSL-FO. There is the Print and
>>> Page Layout Community Group (https://www.w3.org/community/ppl/), of
>>> which I am the Chair, but it takes more than just a venue to produce a
>>> spec with enough impetus to convince multiple vendors/teams to implement
>>> it.
>>>
>>> Regards,
>>>
>>>
>>> Tony Graham.
>>
>> -
>> 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
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] tagged and accessible PDF document with DocBook

[Dave Pawson]

I think you've summed it up Holger.

http://www.pdf-accessibility.com/ is of little help.

I can only suggest you override the xsl-fo templates to add structural
information
from the source.

(which assumes you need printable content?)

HTH

On 3 April 2017 at 14:25, Holger Bast <holgerb...@gmx.de> wrote:
> Dear all,
> I'm trying to generate "tagged" and "accessible" PDF documents, via docbook5 
> -> xsfl:fo -> pdf (with Apache FOP and docbook-xsl v1.79.1). I tried both 
> FOP-parameters (accessibility/PDF-UA) and received a tagged PDF file. But I 
> found out that there is no structural information inside the pdf; 
> 'everything' is tagged as p(aragraph). The xsl:fo also lacks this kind of 
> information. The Apache FOP Accessibility help recommends using the role 
> attribute for tagging information inside the document:
>
> I. A Level 1 Heading
>
> Did I miss something (parameter, wrong stylesheet)?
> Has anyone already generated accessible PDF documents based on DocBook?
>
> Thanks, Holger
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Conversion: xml:lang not added to root element of Epub/XHTML1/XHTML5 files

[Dave Pawson]

On 15 February 2017 at 01:48, Bob Stayton <b...@sagehill.net> wrote:
> Hi Leif,
> This can be easily done by adding the following to your customization layer:
>
> 
>   
> 
>
> This makes use of two utility templates.  The 'root.attributes' template is
> called right after the opening tag of , and it should output
> xsl:attribute elements.
>
> The 'xml.language.attribute' will generate an xml:lang attribute name and
> value.
>
> I'd like to hear from members of the mailing list about whether you think
> this should be default behavior or not.


Fair request IMHO. Every element? Suggest that is too much.
A parameter on the root element, then customisation thereafter perhaps?
Pareto: suggest most documents will major in one language with (small?)
parts in another?

regards




>> Can the official XSLT converstion files for Epub/XHTML5/XHTML1 be
>> updated to add the xml:lang attribute to the root element of all HTML
>> documents?
>>
>> And/Or how can I at least make it happen in my local version of the XSLT
>> files?
>>
>> If XSLT has technical limiations that prevents this behavior, then at
>> the very least - as a workaround, xml:lang should in addition to be
>> added to the (in this case) HTML  elemewnt, also be added to
>> the  element. (Or else, the title element would be 'hanging in
>> the air', as an element without language tag assigned.)
>>
>> Background:
>>
>> The (x)HTML XSLT conversion sheets for DocBook fails to add a
>> (xml:)lang) attribute to the  element. This happens for Epub,
>> XHTML1 and XHTMl5 conversion. (I have not tested HTML conversion.)
>>
>> For instance, if I (1) create an DocBook article document, adding
>> xml:lang="en" to the DocBook  element and then (2) apply
>> converstion to XHTML5 using the docbook.xsl file found at
>> cdn.docbook.org [1], then, (3) the end result is a XHTML5 file where
>> xml:lang is /not/ applied to  (and not to , for that matter
>> and not, as a workaround, to  or  either). The first
>> occurrence of xml:lang is found only on the  element.
>>
>> By the way: I consider this behavior a bug. And I belive that the reason
>> for this bug is mechanistic conversion of the DocBook root element (in
>> this case: ) to the HTML element that “we” have decided to
>> correspond to the root element (for Docbook  documents, then
>> ”we” have decided that the corresponding HTML element is the HTML
>>  element). The /correct/ behavior ought to have been to
>> /always/ add the xml:lang attribute of the Docbook root element (in this
>> case: ), to the HTML root element of ().
>>
>> [1] http://cdn.docbook.org/release/xsl/current/xhtml5/docbook.xsl
>> --
>> leif halvard silli
>>
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] does not number...

[Dave Pawson]

Comments inline

Bob - correct me if I'm wrong please.

On 12 February 2017 at 20:58,  <stim...@comcast.net> wrote:
> Hi,
>
> I'm curious about the mix of components for Saxon. In the original CLASSPATH
> I've been using with the Saxon jar files distributed with DocBook 5.1 and
> and the highlighter, I've used this:
> docbook5/stylesheet/docbook-xsl-ns-1.79.1/tools/lib/saxon.jar
> docbook5/stylesheet/docbook-xsl-ns-1.79.1/extensions/saxon65.jar
> xslthl-2.1.3/xslthl-2.1.3.jar
>
> I'm thinking "extensions/saxon65.jar" is probably the version 6.5, and that
> the implementation of "com.icl.saxon.StyleSheet" (which is what is called on
> the java command line) is from saxon.jar. I see that those files
> (distributed with DocBook 1.79.1) also make available "saxon9he.jar", so
> I've experimented with replacing "saxon.jar" with "saxon9he.jar". When I do
> this java is no longer able to find "com.icl.saxon.StyleSheet":
> Error: Could not find or load main class com.icl.saxon.StyleSheet
>

The second 'saxon' jar is extended to include docbook processing. It
is not the prime transform jar file AFAIK


> ...is there an alternate implementation for "com.icl.saxon.StyleSheet" when
> using saxon9he.jar, or am I going about getting saxon9 the wrong way? I have
> not been able to get a valid command line with direct java calls naming
> saxon9he.jar.

For understanding, write a 3 line docbook (or any xml file)
and transform it using xslt.
   use saxon 6.5 and you'll get xslt 1.0
Use saxon 7+ (ideally the latest from sourceforge) and you'll get
   xslt 2.0 (and the stylesheet will need to match)

Then you can start doing docbook processing.
Some (bit of research needed) docbook processing needs
java 'extensions' which are called up from the xslt.
That's where the second jar file comes in. *NOT* for the
prime transform?

>
> My installed Linux has "Saxon-HE 9.4.0.9J from Saxonica" by means of the
> Linux Fedora packages, and has a command line wrapper shell script "saxon".

I too use Fedora 25, 64 bit, but still install and access the
seperate saxon 9 file for transforms. Likely the same but
I can't confirm that.



> The syntax to use the Linux saxon 9 wrapper script is different than calling
> java jar files directly as an argument to "java". While trying to drop
> calling java directly, and to adapt to this newer wrapper script syntax, my
> experiments finally got past outright failure before starting...but then it
> fails immediately after starting with this message: warning: "Running an
> XSLT 1 stylesheet with an XSLT 2 processor".

Ask Bob or the team about that. You do need a 'version = 2.0'
declaration in the stylesheets, but note it is a warning?
  In theory, a 2.0 processor can process a 1.0 stylesheet, though
there are issues (odd cases).

IMHO you need to understand the xslt process. Basically
java -cp .. main.method, sourceXML, stylesheet, output.
See http://www.saxonica.com/html/documentation/using-xsl/commandline.html
for full detail


>
> Is DocBook 1.79.1 combined with xslthl-2.1.3 a mix of XSLT 1 and 2? I'm
> struggling to find the right tool combination...since DocBook 1.79.1 ships
> with both saxon.jar and saxon9he.jar perhaps some "magic combination" of jar
> files would solve the missing highlighting. Other people have had this work,
> so I must still be missing some detail about how I am using Saxon for
> highlighting.

I can't answer that - I don't peek into the corners so don't trip over
this issue.  Wait till Bob or the team answer?


HTH


>
> Thanks!
>
> - Original Message -
> From: Dave Pawson <dave.paw...@gmail.com>
> To: stim...@comcast.net
> Cc: Docbook <docbook-apps@lists.oasis-open.org>
> Sent: Sun, 12 Feb 2017 19:06:52 - (UTC)
> Subject: Re: [docbook-apps]  does
> not number...
> It would seem you need to switch to XSLT 2.0 (Saxon from Sourceforge?)
> to get your highlighting.
> 6.5 is xslt 1.0
> HTH
> you're not the only one to 'fight' through all the combinations
> before you get what you want :-)
>
> On 12 February 2017 at 17:31, <stim...@comcast.net> wrote:
>> Hi,
>>
>> "highlight.source" is set to "1" in "fo/param.xsl" (I'm creating an fo
>> file
>> which is then converted to pdf via fop...looking at the fo file I can
>> verify
>> it isn't fop skipping the highlighting...the original fo file does not
>> contain highlighting). Other changes in the param.xsl file show up, so I
>> know I'm using the right file. Still no highlighting.
>>
>> I have two exactly matching versions of xslthl-config.xml ("exactly
>> matching" verified with diff). I've tried spe

Re: [docbook-apps] does not number...

[Dave Pawson]

It would seem you need to switch to XSLT 2.0 (Saxon from Sourceforge?)
to get your highlighting.
   6.5 is xslt 1.0

HTH

you're not the only one to 'fight' through all the combinations
before you get what you want :-)


On 12 February 2017 at 17:31,  <stim...@comcast.net> wrote:
> Hi,
>
> "highlight.source" is set to "1" in "fo/param.xsl" (I'm creating an fo file
> which is then converted to pdf via fop...looking at the fo file I can verify
> it isn't fop skipping the highlighting...the original fo file does not
> contain highlighting).  Other changes in the param.xsl file show up, so I
> know I'm using the right file. Still no highlighting.
>
> I have two exactly matching versions of xslthl-config.xml ("exactly
> matching" verified with diff). I've tried specifying xslthl-config.xml with
> the "-Dxslthl.config=" parameter using either full path without URL notation
> and with URL notation (the file:// notation). FYI, one version of
> xslthl-config.xml is the one which came with DocBook 5.1, the other exactly
> matching xslthl-config.xml came with the sourceforge.net download of
> xslthl-2.1.3.
>
> The "language=" of the programlisting tag matches the id's of
> xslthl-config.xml (I've tried bourne and ini so far).
>
> Searching for other highlight.source info I grep'd through other files and
> saw file "highlighting/README". The content of this file has this excerpt:
> ...
> Note: Saxon 8.5 or later is also supported, but since it is an XSLT 2.0
> processor it is not guaranteed to work with DocBook-XSL in all
> circumstances.
> ...
>
> The version of Saxon being used came with DocBook 5.1 (the jar file), and
> should work:
> SAXON 6.5.5 from Michael Kay
>
> For reference the CLASSPATH contains:
> docbook5/stylesheet/docbook-xsl-ns-1.79.1/tools/lib/saxon.jar
> docbook5/stylesheet/docbook-xsl-ns-1.79.1/extensions/saxon65.jar
> xslthl-2.1.3/xslthl-2.1.3.jar
>
> Is there any way (short of editing source code) to find out if
> xslthl-2.1.3.jar is even called when language="bourne" or language="ini" are
> specified? Syntax highlighting would be a valuable tool, but it just feels
> like I'll end up skipping actual content writing if I have to debug at the
> source code level...and the issue is probably just something simple I've
> overlooked, but I do not have the experience to know what to look at.
>
> Thanks!
>
> - Original Message -
> From: Dave Pawson <dave.paw...@gmail.com>
> To: stim...@comcast.net
> Cc: Docbook <docbook-apps@lists.oasis-open.org>
> Sent: Sun, 12 Feb 2017 07:37:22 - (UTC)
> Subject: Re: [docbook-apps]  does
> not number...
> http://docbook.sourceforge.net/release/xsl/current/doc/html/highlight.source.html
> Have you 'switched it on' via the parameter settings?
> HTH
> On 11 February 2017 at 20:42, <stim...@comcast.net> wrote:
>> Hi,
>>
>> From the link on Saxon plus other information I put together the simplest
>> test case (which sort of works). The command is essentially this (other
>> commands validate the XML with jing and xmllint before calling Saxon):
>> CLASSPATH=${CLASSPATH};\
>> java \
>> -Dxslthl.config=${XSLTHL}/highlighters/xslthl-config.xml \
>> com.icl.saxon.StyleSheet \
>> -o ${OBJ}/${TITLE}_monolithic.fo \
>> ${OBJ}/${TITLE}_monolithic.xml \
>> ${XSLT}/fo/docbook.xsl \
>> use.extensions=1
>>
>> This does enable line numbering in programlisting tags, and options
>> related
>> to numbering do as expected. However, in attempting to get the syntax
>> highlighting to work (see
>> http://www.sagehill.net/docbookxsl/SyntaxHighlighting.html) nothing I've
>> tried has any effect (test cases were with "bourne" and "ini" files).
>>
>> The CLASSPATH contains the following files, and no error occurs (for the
>> sake of brevity I'm showing only the relative paths, but the full path is
>> used without error in the actual Makefile):
>>
>> docbook-xsl-ns-1.79.1/tools/lib/saxon.jar:docbook5/stylesheet/docbook-xsl-ns-1.79.1/extensions/saxon65.jar:xml/xslthl-2.1.3/xslthl-2.1.3.jar
>>
>> Since I get no errors, and because the Saxon processing is otherwise
>> working, is there any additional requirement to keep syntax highlighting
>> from failing as if the option did not exist? Is syntax highlighting
>> something which maybe requires the Xalan parser? Is there perhaps
>> something
>> from param.xsl which needs to change and not mentioned in the above URL on
>> syntax highlighting?
>>
>> Thanks!
>>
>> - Original Message -
>> From: Richard Hamilton &l

Re: [docbook-apps] does not number...

[Dave Pawson]

;> Sent: Fri, 10 Feb 2017 19:09:00 - (UTC)
>> Subject: Re: [docbook-apps]  does
>> not number...
>> Hi,
>> Did you read this section in my online book about line numbering? It
>> only works with Java-based processors.
>> Bob Stayton
>> Sagehill Enterprises
>> b...@sagehill.net
>> On 2/10/2017 11:01 AM, stim...@comcast.net wrote:
>> > Hi,
>> >
>> > Under DocBook 5.1 I've been able to list programs, but line numbering
>> > has no effect (and there is no error under xmllint or jing). Is there
>> > some ENTITY or other precondition required for line numbering under 5.1?
>> >
>> > Thanks!



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] does not number...

[Dave Pawson]

I can understand the hassle of setting this chain up.
Suggest you isolate each step?

Validation
Transformation to xsl-fo
fo processing to PDF.

for 2 I have


java -Xms1024m -cp
/myjava/saxonB.jar:/myjava/xercesImpl.jar:/myjava/xml-apis.jar:/myjava/resolver.jar:/sgml
-Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XIncludeParserConfiguration
net.sf.saxon.Transform -x
org.apache.xml.resolver.tools.ResolvingXMLReader -y
org.apache.xml.resolver.tools.ResolvingXMLReader
-r:org.apache.xml.resolver.tools.CatalogResolver -s:$1 -xsl:$2 -o:$3
$4

1 is the source,
2 the stylesheet
3 the output
4 any additional saxon params.


Adjust parms as necessary.


(may be out of date). My fop script is

export fophome=/apps/fop10
f=$fophome/lib
fop=$fophome/build/fop.jar

cp=$f/xmlgraphics-commons-1.4.jar:$f/batik-all-1.7.jar:$f/commons-logging-1.0.4.jar:$f/commons-io-1.3.1.jar:$f/avalon-framework-4.2.0.jar:$fop

java -cp $cp org.apache.fop.cli.Main -r -c $fophome/fop.conf -fo $1 -pdf $2

input fo is $1
output pdf is $2

HTH




On 10 February 2017 at 20:26,  <stim...@comcast.net> wrote:
> Hi,
>
> I was going by this reference as to requirements, and have not read the
> whole book (thus I did not yet see the Java requirement):
> http://tdg.docbook.org/tdg/5.1/programlisting.html
>
> Admittedly I'm trying to do something quicker than I should and not reading
> everything (I've been through a lot of material, but it's just a drop in the
> bucket for everything needed when I really just need to sit down and write
> content). I've had some frustrations getting the Java-based processors
> working and have tried to stick to the xmllint/jing/xsltproc family for that
> single reason. The Java-based processing answer likely also answers my
> earlier syntax highlighting question about whether to abandon my current
> approach with xmllint.
>
> To use Saxon or Xalan I would have to change the current build scheme, which
> I've never succeeded at:
> xmllint --output "${OBJ}/${TITLE}_monolithic.xml" --nonet --noent -xinclude
> "${CONTENT}/${TITLE}.xml"
> xsltproc --output ${OBJ}/${TITLE}_monolithic.fo ${XSLT}/docbook.xsl
> ${OBJ}/${TITLE}_monolithic.xml
> fop -c ${PREFIX}/fop.xconf -fo ${OBJ}/${TITLE}_monolithic.fo -pdf
> ${OUT}/${TITLE}.pdf
>
> I realize I'm probably asking a lot, but is there any advice I can get on
> editing that chain of commands to instead work with Saxon or Xalan? Getting
> past the tools on the command line (for a hand written Makefile) is just
> getting frustrating and is why the current chain of commands have never
> evolved to anything Java-based.
>
> I do plan on reading more (I'm not resisting reading), but there are other
> requirements which tend to require at least a draft to be available sooner
> rather than later.
>
> Thanks!
>
> - Original Message -
> From: Bob Stayton <b...@sagehill.net>
> To: stim...@comcast.net, Docbook <docbook-apps@lists.oasis-open.org>
> Sent: Fri, 10 Feb 2017 19:09:00 - (UTC)
> Subject: Re: [docbook-apps]  does
> not number...
> Hi,
> Did you read this section in my online book about line numbering? It
> only works with Java-based processors.
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
> On 2/10/2017 11:01 AM, stim...@comcast.net wrote:
>> Hi,
>>
>> Under DocBook 5.1 I've been able to list programs, but line numbering
>> has no effect (and there is no error under xmllint or jing). Is there
>> some ENTITY or other precondition required for line numbering under 5.1?
>>
>> Thanks!



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Odd Characters in UTF-8, Docbook 5.1

[Dave Pawson]

https://xmlgraphics.apache.org/fop/maillist.html is the fop mailing list,
if your issue is simply with fop?

regards

On 2 February 2017 at 22:19,  <stim...@comcast.net> wrote:
> This is turning out to be odd...I have to conclude that fop is not reading
> any configuration files...especially none named "fop.xconf". The short story
> is that I can intentionally introduce errors in fop.xconf (all occurrences
> on the computer as verified by updatedb and locate .xconf), introduce
> "true", and no mention of
> anything different occurs. I can run this under strace, and I see no calls
> at all referring to opening any xconf file (nor any attempt to do so).
> Somehow I need to figure out how fop is configured since the installed xconf
> files are ignored.
>
> Here's a summary of how I go there:
>
> The DejaVuSans fonts do contain the character glyphs, and this is what I've
> been trying to switch to instead of Helvetica for the sans-serif.
>
> It was determined that param.xsl picks between serif and sans-serif by
> naming one of these:
> serif
> sans-serif
>
> When changing between serif and sans-serif vi param.xsl edits, it is
> verified that that either Times or Helvetica are used upon switch. This
> works as expected.
>
> I added the fop option "-d" to debug...this did not indicate any error,
> though it was more explicit about not finding glyphs. After that I tried the
> strict-configuration modification. No change. I looked for any possible
> occurrence of fop.xconf, these two exist (I don't know how they differ), I
> intentionally tried to break both for warning information:
> /usr/share/fop/conf/fop.xconf
> /usr/share/publican/fop/fop.xconf
>
> This had no effect, so this is when I tried strace. It seems fop does not
> use external configuration file searches, and I don't know why...so I can't
> actually add DejaVuSans. I'm currently trying to figure out where there is a
> mailing list or other support for fop. Incidentally, the "fop -x" command to
> dump configuration fails...it wants an input file or it won't tell me
> anything about configuration.
>
> Thanks everyone for the help!
>
> - Original Message -
> From: Dave Pawson <dave.paw...@gmail.com>
> To: Richard Hamilton <hamil...@xmlpress.net>
> Cc: stim...@comcast.net, Docbook <docbook-apps@lists.oasis-open.org>
> Sent: Thu, 02 Feb 2017 06:37:36 - (UTC)
> Subject: Re: [docbook-apps] Odd Characters in UTF-8, Docbook 5.1
> Perhaps start where the problem is. Look for a font which contains
> the glyphs for the Unicode code points you want to use. Check the
> code points produce the glyphs you want.
> Find out how the app (fop and any others you use in your tool chain)
> selects fonts.
> Run the app knowing that the font has what you want and your code
> points are correct.
> HTH
> On 1 February 2017 at 23:44, Richard Hamilton <hamil...@xmlpress.net> wrote:
>> I’m getting out of my depth on fop, so maybe someone else on the list can
>> help here.
>>
>> However, diving in deeper than I should:-)I suspect the problem is number
>> 1.
>>
>> I suggest running fop with the -d (debug) mode, and you might also try -x,
>> which will dump the configuration; that way you can see if the configuration
>> fop uses is what you think it is using.
>>
>> Good luck,
>> Dick
>> ---
>> XML Press
>> XML for Technical Communicators
>> http://xmlpress.net
>> hamil...@xmlpress.net
>>
>>
>>
>>> On Feb 1, 2017, at 15:21, stim...@comcast.net wrote:
>>>
>>> Hi,
>>>
>>> So what my experimenting shows so far for trying to change font is that I
>>> can adjust param.xsl and switch between serif or sans-serif. The result
>>> depends on what is available in fop.xconf which lists Times-Roman for serif,
>>> and Helvetica for sans-serif. I've attempted to add an additional font
>>> definition for DejaVuSans by the following inside the  of fop.xconf:
>>>
>>> 
>>> 
>>> 
>>> 
>>>
>>> I am unable to name "DejaVuSans" instead of "sans-serif" in param.xsl (it
>>> falls back to Symbol). I see three possibilities...
>>> 1. My DejaVuSans declaration is wrong.
>>> 2. I have to remove Helvetica in fop.xconf from the sans-serif listings.
>>> 3. The Docbook parameters you mentioned are somewhere outside of
>>> fop.xconf or param.xsl.
>>>
>>> It seems unlikely I need to remove Helvetica, more likely there is
>>> another configuration elsewhere. However, I don't see any occurrence of
>>> &qu

Re: [docbook-apps] Odd Characters in UTF-8, Docbook 5.1

[Dave Pawson]

iven Docbook 5.1 installation which maps "Times Roman" to serif, and 
>> > "Helvetica" to sans-serif? I think this is the key to getting those box 
>> > drawing characters to work...perhaps if I can remap serif and sans-serif 
>> > to valid fonts other than Helvetica and Times Roman it would work with 
>> > those characters.
>> >
>> > Thanks!
>> >
>> > - Original Message -
>> > From: Bob Stayton <b...@sagehill.net>
>> > To: stim...@comcast.net, docbook-apps@lists.oasis-open.org
>> > Sent: Wed, 01 Feb 2017 18:51:04 - (UTC)
>> > Subject: Re: [docbook-apps] Odd Characters in UTF-8, Docbook 5.1
>> > Hi,
>> > If by system-wide you mean everyone sharing one DocBook XSL
>> > installation, you could edit the parameters file for that installation.
>> > Find the file named fo/param.xsl and change these stylesheet parameters:
>> > serif
>> > sans-serif
>> > All of the stylesheet params are documented here:
>> > http://docbook.sourceforge.net/release/xsl/current/doc/fo/index.html
>> >
>> > Bob Stayton
>> > Sagehill Enterprises
>> > b...@sagehill.net
>> > On 2/1/2017 10:22 AM, stim...@comcast.net wrote:
>> > > I just wanted to add some information from reading build logs for the
>> > > document. It turns out the error shows up under "fop" because the
>> > > particular font does not support this character (I'm surprised
>> > > Times-Roman does not have this by default since just about every
>> > > application on the system has the character):
>> > > WARNING: Glyph "├" (0x251c, SF08) not available in font 
>> > > "Times-Roman".
>> > >
>> > > The trouble here is I now want to change this for the system as a whole,
>> > > not just on the document (I want to avoid any project using
>> > > Times-Roman). I am curious if there is some simple way under Linux to
>> > > find out which fonts fop has available, and how to change the default
>> > > font family for all Docbook publishing via a system-wide setting? I've
>> > > found many documents on modifying Docbook behavior within source code,
>> > > but not much seems to exist on system-wide Docbook configuration from a
>> > > system administrator's point of view...if anyone has a URL for
>> > > information on specifics of tuning Docbook defaults under Linux I'd be
>> > > very happy!
>> > >
>> > > Thanks!
>> > >
>> > > - Original Message -
>> > > From: stim...@comcast.net
>> > > To: docbook-apps@lists.oasis-open.org
>> > > Sent: Tue, 31 Jan 2017 23:20:24 - (UTC)
>> > > Subject: [docbook-apps] Odd Characters in UTF-8, Docbook 5.1
>> > > Hi,
>> > >
>> > > I'm working on a Linux machine which has UTF-8 encoding. The docbook 5.1
>> > > I'm working with is declared:
>> > > 
>> > > > > > 
>> > > ]>
>> > >
>> > > Entities changed a while back (relaxng changed things), but so far as I
>> > > know I should still be able to work with numeric entities when using odd
>> > > characters which are part of UTF-8. I'm trying to get some box drawing
>> > > characters to work, specifically because I need to illustrate a file
>> > > directory structure which has been output like this from the "tree -d"
>> > > command. Here's a short sample:
>> > >> tree -d -L 2 /etc | tail -n 20 | tail -n 6
>> > > │ ├── pluginconf.d
>> > > │ ├── protected.d
>> > > │ └── vars
>> > > └── yum.repos.d
>> > >
>> > > As you can see the vertical and horizontal box drawing characters are
>> > > used. When I redirect this to a file or copy and paste into the document
>> > > all I get is a substitute...each shows as "#". So I tried to use numeric
>> > > entities instead. As an example "boxh" (horizontal box line) should work
>> > > as "". This does not work, and rendering still ends up as "#". I
>> > > tried the numeric code for the plus/minus character, "||", and
>> > > this does work. I don't know if it proves anything, but since my UTF-8
>> > > terminal shows all of the above characters just fine on a terminal, it
>> > > seems like the ability to output is not in question...perhaps this is an
>> > > invalid assumption.
>> > >
>> > > Btw, one reference on the Unicode numeric value is from:
>> > > http://www.oasis-open.org/docbook/documentation/reference/html/iso-box.html
>> > >
>> > > Under Docbook 5.1, what do I need to do to use this numeric entity other
>> > > than using UTF-8 and the numeric entity syntax? Is there an additional
>> > > XML declaration I need?
>> > >
>> > > Thanks!
>
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Getting started with chunking

[Dave Pawson]

On 7 December 2016 at 11:34, Radu Coravu <radu_cor...@sync.ro> wrote:
> Hi,
>
> I think the problem is this one:
>
>> I already import our custom FO xsl.
>
>
> because the stylesheets which produce customized XSL-FO output have nothing
> in common with the stylesheets which generate HTML output. Usually the HTML
> output is modified using a custom CSS.

Or using import precedence to override the standard docbook templates Radu?

regards Dave


>
> Regards,
> Radu
>
> Radu Coravu
>   XML Editor, Schema Editor and XSLT Editor/Debugger
> http://www.oxygenxml.com
>
> On 12/7/2016 12:20 PM, bergfrid.digitald...@gmail.com wrote:
>>
>> Hi, we are planning to add HTML to our output formats.  Have created PDFs
>> exclusively for years with custom FO styles sheets in an offline tech stack.
>> (1.79.1, db 5.1, oxygen 18.1)
>>
>> I tried to create a new transformation scenario in oxygen using
>> html/chunk.xsl and it spits up over 100 undeclared variables and nonexistent
>> templates.
>>
>> How do I troubleshoot this? The missing variables and templates are used
>> by chunk-common.xsl and chunk-code.xsl. I already import our custom FO xsl.
>> Do I need to import something else? Add something to our catalog.xml?
>>
>> Mvh. Bergfrid Skaara Dias
>> -
>> 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
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Automatically detecting which PDFs are affected by changes in a DocBook Git commit

[Dave Pawson]

Perhaps ask this question on an Adobe forum, if
the changes to the XML are not enough for your customers.

HTH

On 1 November 2016 at 14:42, Bergfrid Skaara
<bergfrid.digitald...@gmail.com> wrote:
> I´d like to know the overall difference between versions X and Y of a single
> PDF - automatically so we don't need to inspect and compare page by page
> manually (simplifying release process).
>
> I need to know all PDFs (and what content within them) that have changed as
> a result of commits X,Y, Z (simplifying review and release process).
>
> I´d like notifications if a commit targeted only at feature A ends up
> changing PDFs unrelated to feature A. This would typically indicate
> profiling errors or misplaced includes that need to be fixed.
>
> Inserting build numbers or some similar ID from the CI environment into the
> PDF metadata would also help.
>
> The challenge with comparing PDFs is all the noice you get from layout
> changes (white space) and info in headers and footers such as dates and
> version numbers.
>
> And if you go the convert-PDFto-text-before compare route, would it not be
> better to compare the intermediate FO files rather than waste time going
> through the entire publishing pipeline first?
>
> We are not looking to replace our current CI environment. Extending the
> current build-logic is not a problem, but I´m not sure what the new logic
> should look like.
>
> Bergfrid Skaara Dias
>
> On Wed, Oct 26, 2016 at 6:48 PM, Stefan Seefeld <ste...@seefeld.name> wrote:
>>
>> On 26.10.2016 11:04, Bergfrid Skaara wrote:
>> > Hi,
>> >
>> > We use Git to version control our modular DocBook XML code base. I´d
>> > like to enforce stricter change management than what simply inspecting
>> > the Git log manually offers. Specifically, I want to trace each
>> > modular DocBook XML fie that has been changed up to the PDFs that will
>> > be changed as a result.
>> >
>> > Tracing the ancestor files through a sequence of xi:includes is
>> > trivial. My challenges are:
>> >
>> > 1. Profiling. I need to trace ancestor elements taking profiling into
>> > consideration.
>> > 2. Entities. We use entities extensively for both aliases and reused
>> > text. Is there a way to track effects of changed entities without
>> > starting with a brute force search of all DocBook XML files using that
>> > entity?
>> >
>> > Are there any tools, standalone or add-ons to oXygen, that support
>> > this or similar behavior, or am I better off writing my own script? In
>> > case of script, which option is better: XSLT or any scripting language
>> > facilitating text parsing?
>>
>> I'm not quite sure what you mean by "change management", and what it is
>> that you want to enforce, and neither what exactly you want to trace.
>>
>> Generating a PDF from XML sources typically requires some build logic,
>> so I think the best you can do is use that very build logic and then
>> compare (or validate) the generated PDF (or any intermediate formats,
>> such as FO). That can easily be done in a CI environment (such as
>> Travis-CI), so you can fully automate that such that the same process is
>> executed for each push.
>>
>> Stefan
>>
>> --
>>
>>   ...ich hab' noch einen Koffer in Berlin...
>>
>>
>> -
>> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
>> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>>
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Custom ISO Schematron validation for modular Docbook XML with extensive profiling

[Dave Pawson]

On 26 October 2016 at 14:07, Radu Coravu <radu_cor...@sync.ro> wrote:
> Dear Bergfrid,
>
> Schematron is in the end translated to XSLT.
> And the XSLT can be applied directly over the XML content and it will
> generate messages for each assert.
> As you will do it outside of Oxygen you will not have fancy backmapping, you
> might not have a clear indication where the particular error was originally
> located.

Radu, can we use oXygen to run the Schematron checks please?
  (and add our own?)

regards


> On 10/26/2016 3:17 PM, Bergfrid Skaara wrote:
>>
>> What are our options for adding custom ISO Schematron validation to our
>> DocBook publishing pipeline ?
>>
>> The code base is large and extremely modular. We also use extensive
>> profiling to leverage single source reuse as much as possible. The
>> output is currently PDF only, but we might add HTML to the mix next
>> year. Our technical editors use oXygen, and we validate and transform
>> single documents there. In addition, we have a continuous integration
>> pipeline that builds all PDFs when something is committed to Git.
>>
>> On-the-fly Schematron validation seems doable in oXygen. However, I find
>> it tricky to combine profiling with validating after a commit to check
>> that changes did not break other documents and that business rules are
>> adhered to.
>>
>> Bergfrid Skaara Dias
>
>
>
>
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Alternatives to entities for referencing small substitutions

[Dave Pawson]

Excellent use of catalogs. Never ceases to amaze me just how useful they are.

regards Dave P

On 18 October 2016 at 22:44, Cathy Riely <cri...@apple.com> wrote:
> You could also use catalogs that point to two different entity files based
> on the target project passed in.
>
> On Oct 18, 2016, at 4:24 PM, Paul Hoadley <pa...@logicsquad.net> wrote:
>
> On 19 Oct 2016, at 2:44 AM, Thomas Schraitle <tom_s...@web.de> wrote:
>
> This sounds like profiling in combination with entities.
>
> You could define your foo entity like this:
>
> os='a'>Baros='b'>Baz">
>
> The  element is quite neutral and is allowed where inline elements
> are
> also allowed.
>
>
> Thanks Thomas, that looks like the approach I need.
>
>
> --
> Paul Hoadley
> http://logicsquad.net/
>
>
>
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>
>
> Regards,
>
> Cathy Riely
>
>
>
>
>
>
>
>
>
>
>
>
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Re: [docbook] future of DocBook XML Schema (XSD)?

[Dave Pawson]

+ for rng only.
I can honestly say I've never used xml schema for docbook (or anything
else for that matter)
   I do validate many instances though, using Jing / oXygen
regards

On 18 October 2016 at 19:51, Bob Stayton <b...@sagehill.net> wrote:
> The DocBook Technical Committee is considering dropping the XML Schema
> version of DocBook in a future version 6.  We would like to hear from any
> members of the DocBook community who would be affected by this change.
>
> Let me be clear that this change is not on the horizon, but part of our long
> term planning.  The DocBook TC takes great care in maintaining backwards
> compatibility on point releases because we know how much the DocBook
> community relies on stable sources.  When DocBook rolls to a new major
> version number, we treat that as an opportunity to introduce changes that
> are not backwards compatible.  The change from 4 to 5 was such.  If we
> foresee such changes coming, we give the DocBook community very advanced
> notice to prepare for them.
>
> We will continue to maintain the DocBook standard in RelaxNG with Schematron
> rules, and will continue to generate a compatible DTD.
>
> However, the process of maintaining the XSD version of DocBook is proving
> burdensome because it cannot be completely generated by a conversion
> program, and requires manual tweaking.  Because we are not sure if anyone is
> actually using the XSD version, we are wondering if this is worth the
> effort.  If you are using it, or have tools that depend on XSD, please let
> us know.
>
> You can reply directly to me if you don't want to discuss it on the mailing
> list.
>
> --
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
>
> -
> To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-h...@lists.oasis-open.org
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Alternatives to entities for referencing small substitutions

[Dave Pawson]

Paul, I now defer to Bob at
http://www.sagehill.net/docbookxsl/  which is a most excellent resource.

HTH

On 18 October 2016 at 11:08, Paul Hoadley <pa...@logicsquad.net> wrote:
> Hello,
>
> I’ve been out of the DocBook ecosystem for a few years, but I’ve got some
> documentation to write and I’m rolling up my sleeves! I would have thought
> the following would be a FAQ, but Dave Pawson’s page is giving me a 404
> right now.
>
> What is the state of the art for small text substitutions (basically just
> domain-specific terms) that can also be varied via the profiling machinery?
> I have an application that can run as more than one “product”, and each
> product shows domain-specific variations in labels, for example, in the user
> interface. There might be a generic term for some object “Foo”, but
> Application A will call this a “Bar”, and Application B calls it a “Baz”.
> What I want to be able to do is refer to a “Foo” throughout the source, but
> substitute “Bar” for App A’s output, and “Baz” for App B’s. What’s the best
> way to achieve this?
>
>
> --
> Paul Hoadley
> http://logicsquad.net/
>
>
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Xandocs?

[Dave Pawson]

Another view of transclusion?

Ted Nelson video
https://www.youtube.com/watch?v=72M5kcnAL-4
via Dan Brickley.

regards

-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] validating individual files in a document

[Dave Pawson]

http://stackoverflow.com/questions/36994308/how-to-create-a-new-entity-with-relax-ng-schema-in-docbook-v5-0

Internal DTD subset.

HTH

On 17 July 2016 at 02:12, Joseph Mingrone <j...@ftfl.ca> wrote:
> Hi,
>
> I'm working on setting up on-file-fly validation of FreeBSD documentation in
> Emacs with nxml-mode.  I've configured Emacs/nmxl-mode to use FreeBSD's nearly
> DocBook 5.0 compact relax NG schema.  Everything is working well, but there is
> one issue that I am stumped on.  If I am working on a file (e.g. a chapter) 
> that
> is included in a main document (book) and that file uses project-specific
> entities, the document will not validate.  I can put a DTD at the top of the
> file with the entities, and it will validate, but that's clearly the wrong 
> thing
> to do since the book file already has a DTD.
>
> Suggestions?
>
> Thanks,
>
> Joseph
>
> --
>
> Tree for FreeBSD's documentation: https://svnweb.freebsd.org/doc/
>
> Book file:
> https://svnweb.freebsd.org/doc/head/en_US.ISO8859-1/books/fdp-primer/
> Chapter file: editor-config/chapter.xml, which is included in book.xml
>
> The book is glued together with the Makefile there.  There are a few layers of
> includes, which eventually pulls in the .ent files:
> https://svnweb.freebsd.org/doc/head/share/xml/
>
> The compact relax NG schema:
> https://svnweb.freebsd.org/doc/head/share/xml/freebsd50.rnc?revision=43126=markup



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] Indexing.

[Dave Pawson]

I agree, the more I've used it the more I'm impressed with the coding,
for which many thanks to the docbook team.

regards

On 21 June 2016 at 23:06, Pc Thoms <pcth...@gmail.com> wrote:
> Hi Dave and Docbook-apps Company:
>
> In working with a legacy text, 1875, and it's index I entered five secondary
> entries, expecting an error, using the following:
>
> Index
> Admission to Seats in Synod
> Ven. Archdeacon McMurray
> Rev. Dr. Sullivan
> Rev. Dr. Stocking
> Wm. J. Harris
> W. B. Curran
> 
>
> And to my surprise and delight this validated and produced the desired
> entry.
> All I have to say is that the xslt stylesheets for DocBook are awesome!
> If this should not work - don't change anything.
>
> Grateful - Paul
>
>
> On Sat, May 5, 2012 at 4:40 AM, davep <da...@dpawson.co.uk> wrote:
>>
>> I'm about to start indexing a db5 book.
>> Reading up on the subject(Nancy C. Mulvany) and wondered if anyone has
>> been there and done that, got the tee-shirt and found the pitfalls in
>> docbook? Any advice from those with lots of experience of using
>> db indexes please?
>>
>>
>>
>> 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] Xsltproc with XInclude (Docbook 5)

[Dave Pawson]

Also on Fedora 23, 64bit

On 2 May 2016 at 01:43,  <stim...@comcast.net> wrote:
> Hi,
>
> I am trying to find a suitable combination of tools under Linux (currently
> Fedora 23) for validating and publishing from Docbook 5 to PDF, PostScript,
> RTF, and some variant of HTML (preferably xhtml strict, but most any variant
> will work).

Edit: Emacs.
Validate: Jing
to  PDF: One of the two commercial XSL-FO tools, Antenna House  or XEP
RTF: Steve? I can't find it (GIYF)
PS: Don't know.
HTML: Standard Docbook transforms.


 Some of my testing "almost" works via xsltproc using the
> sourceforge download for docbook.xsl, but apparently what I need is the "xi"
> version, docbookxi.xsl, which I have not been able to find. If I give up
> dividing into multiple files vi XInclude, and instead use a DTD and
> entities, or else create one large monolithic file, things work...however,
> this is very difficult to work with...I'd end up going back to less
> desirable less flexible tools.

You might want to shift from the DTD's to relax ng, then use the namespaced
version.

xsltproc might work, but I have bash shell scripts for all my conversions.


>
> For use of Docbook 5 under Linux and xsltproc, where would I find a suitable
> XInclude stylesheet (docbook.xsl)? Or is there some other recommended route
> for processing Docbook 5 books while splitting into separate files for each
> chapter?

I expand my includes using the resolver.jar file?

ava   -cp /sgml:/myjava/saxon655.jar:/myjava/xercesImpl.jar:/myjava/resolver.jar
 
-Djavax.xml.parsers.DocumentBuilderFactory=org.apache.xerces.jaxp.DocumentBuilderFactoryImpl

-Djavax.xml.parsers.SAXParserFactory=org.apache.xerces.jaxp.SAXParserFactoryImpl

-Dorg.apache.xerces.xni.parser.XMLParserConfiguration=org.apache.xerces.parsers.XIncludeParserConfiguration
com.icl.saxon.StyleSheet   -o op.html   -w1 .xml
docbook.html.xsl  "saxon.extensions=1"  $4 $5 $6

HTH



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] NVDL, DocBook, and MathML

[Dave Pawson]

The obvious question George - why doesn't the docbook
section need the attach?

Curious!
regards

On 9 February 2016 at 09:11, George Bina <geo...@oxygenxml.com> wrote:
> Hi Bob,
>
> Try adding an attach action on the MathML namespace. This will attach the
> content in MathML to the validation candidate triggered by the  schema="docbook.rng"/> action. Change the NVDL script as below:
>
> http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0;
> startMode="docbook">
> 
> http://docbook.org/ns/docbook;>
> 
> 
> http://www.w3.org/1998/Math/MathML;>
> 
> 
> 
> 
> 
>
> Best Regards,
> George
> --
> George Cristian Bina
>  XML Editor, Schema Editor and XSLT Editor/Debugger
> http://www.oxygenxml.com
>
>
> On 09/02/16 02:33, Bob Stayton wrote:
>>
>> I'm having a problem trying to process DocBook 5 documents using NVDL in
>> order to validate DocBook content that has MathML content within
>> equation or inlineequation.  The DocBook validation side is failing, but
>> only under NVDL.
>>
>> The DocBook rng schema for inlineequation is as follows:
>>
>> 
>>
>>   
>>  
>> 
>>  
>>  
>> 
>>  
>>   
>>   
>>  
>>   
>>
>> 
>>
>> This schema specifies either a) inlinemediaobject or mathphrase, or b)
>> some MathML elements.  It *allows* MathML, but it does not validate it
>> against the MathML DTD.  NVDL is capable of doing that.  But ...
>>
>> When I set up NVDL using a schema like this:
>>
>> http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0;
>> startMode="docbook">
>>  
>>  http://docbook.org/ns/docbook;>
>>  
>>  
>>  http://www.w3.org/1998/Math/MathML;>
>>  
>>  
>>  
>> 
>>
>> This DocBook content validates against docbook.rng:
>>
>> 
>>http://www.w3.org/1998/Math/MathML;>
>>  ...
>>
>> 
>>
>> But when processed with NVDL, it fails with this message:
>>
>> Engine name: Jing
>> Severity: error
>> Description: element "inlineequation" incomplete; expected element
>> "alt", "inlinemediaobject" or "mathphrase" or an element from another
>> namespace
>>
>> I think what is happening is that Jing has sent the  element to be
>> validated against the MathML schema, and then it sends the remains of
>> the inlineequation element to be validated against the DocBook schema.
>> But now inlineequation is empty, and fails validation.
>>
>> I find if I insert an empty  inside inlineequation, then I
>> can work around this error.  Does anyone have any other ideas? That is,
>> short of customizing the docbook equation elements to allow them to be
>> empty.
>>
>
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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] CSS3

[Dave Pawson]

https://rachelandrew.co.uk/archives/2015/07/17/css-grid-layout-at-css-d
ay/  and associated code http://gridbyexample.com/examples/#example4

New CSS3 grid layout. So easy to overlay on docbook and it looks so
good!

Well worth watching. 


regards Dave P

-
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] Oasis catalogs?

[Dave Pawson]

On 27 February 2013 13:41, John Brown johnbrown...@hotmail.com wrote:
 On Wed, 27 Feb 2013 10:24:33 +,Dave Pawson wrote:

 Given !DOCTYPE act SYSTEM \\lrctso.lawreform.ie\lrcdtd\Legislation.DTD

 How to remap this to a local file please?

 system
 systemId=file:\\lrctso.lawreform.ie\lrcdtd\Legislation.DTD
 uri=file:///files/schemas/Legislation.dtd /

 Is not working...

 java.net.UnknownHostException: lrctso.lawreform.ie
 Transformation failed: Run-time errors were reported

 Seems like the host isn't being recognised Is there a workaround please?


 With xsltproc the following works on Windows.

 system
 systemId=file:lrctso.lawreform.ie/lrcdtd/Legislation.DTD
 uri=file:///files/schemas/Legislation.dtd /

 That is, if there is no catalog entry, the DTD will be found. If the catalog
 entry and the DOCTYPE are written as in my suggestion, then the catalog
 will resolve it. You will have to change the DOCTYPE in your documents.
 If you investigate,you will probably be told that
 file:\\lrctso.lawreform.ie\lrcdtd\Legislation.DTD is not a legal system ID.

I was hoping not to have to change the doctype decl.
It is currently \\. which I believe is wrong.




 The rules that I use when constructing file:// paths:

 1) Start with file://
 2) If it is a path on drive (fixed or mapped),then add 
 /drive-letter:/path/to/file.ext, i.e.,
 replace \ with /
 e.g., file:///C:/path/to/file.ext

grin/ the url dance!


 3) If it is a network path (UNC share name) then write out the path just as 
 you would normally,
 replacing \ with / as above, e.g.
 file:myserver/myshare/path/to/file.ext.

so the unc \\share would show in the catalog as file:  doubling up?



 By the way, your URI assumes that the directory /files is in the root of the 
 active drive,
 so if the full path is C:\files\schemas\... and you are on D:, the your 
 command will not
 work.

Yes, I dislike Windows enough to only use c drive!



 All of this is assuming that you are on Windows, of course.

ONly as little as possible!

Thanks John.

I need to let the 'owners' know about \\share. I wonder if this is
common enough
to ask Norm to dance with Oasis again to add it?


regards



-- 
Dave Pawson
XSLT XSL-FO FAQ.
Docbook 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