Re: [docbook] Tabs and content model
On Mon, 5 Feb 2024 at 15:05, Norm Tovey-Walsh wrote: > > > From Norms comments, " ## A group of formal objects, for example subfigures" > > seems a bit off (my view), rather than 'formal objects' (I've a job > > relating to that), > > how about 'related' or 'closely related' then figures / subfigures > > matches (to me). > > Over time, a back-formation developed: if the things that didn’t have > titles were “informal”, then collectively, the things that *did* have > titles were “formal”. > > So we ended up with formalgroup: a group of “formal” objects. Is this made clear in TDG? https://tdg.docbook.org/tdg/5.2/formalgroup No? IMHO that might help (general use of 'formal' in db). History has its place etc. regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] Tabs and content model
On Mon, 5 Feb 2024 at 12:02, Thomas Schraitle wrote:
>
> Hi DocBook users,
>
> DocBook 5.2 contains the element [1] which has this content
> model:
>
>#
>db.formalgroup =
> ## A group of formal objects, for example subfigures
> element formalgroup {
>db.formalgroup.attlist,
>db.formalgroup.info,
>(db.figure+ | db.table+ | db.example+ | db.equation+)
> }
>From Norms comments, " ## A group of formal objects, for example subfigures"
seems a bit off (my view), rather than 'formal objects' (I've a job
relating to that),
how about 'related' or 'closely related' then figures / subfigures
matches (to me).
regards
>
> I'd like to use this element for a "tab structures". An example of a tab
> structure can be seen in "Litestar library documentation"[2] (scroll down a
> bit, see "Define a Controller for your data model").
>
> I would like to replicate this structure in DocBook. Of course the stylesheets
> need to be adapted/customized as well, but that's another issue. I'd like to
> focus on the markup only.
>
> The tab structure in Litestar could look like this in DocBook:
>
>
> Definition of a controller for your data model
>
>Python 3.8+
>... Code for 3.8 ...
>
>
>Python 3.9+
>... Code for 3.9 ...
>
>
>
> Not sure if this is the "right" way to do that in DocBook, but I face some
> questions:
>
> 1. What if I don't need the formalgroup title?
> I could use , but that's not the same. Perhaps this goes into
> the direction of a (which doesn't exist).
>
> 2. Why is not added to the content model?
> The would be the perfect fit if I just want to add
> a single paragraph. The other elements introduce a different semantic.
>
> 3. What about the other informal* elements?
> What if I don't need a title of the objects? In other words, wouldn't
> it make sense to allow the informal* elements as well?
> The stylesheets could create a default name ("Tab X"?) in such a case.
>
> Perhaps the way how I would like to use this element was not intended. :) But
> for me, the following sentence in the TDG[1] let me believe this would be the
> perfect fit for a tab structure:
>
>"Placing them in a container allows the processing system to style
>them together or place them as related elements."
>
> I don't think, there is any other DocBook element that has a similar role, is
> there?
>
> So... what's the "right" way to do that? Perhaps we could add an example to
> the
> TDG[1]? Or would the ideas above justify to amend the content model? Any
> alternative?
>
>
> What do you think? Thanks! :)
>
>
> --- References
> [1] https://tdg.docbook.org/tdg/5.2/formalgroup
> [2] https://docs.litestar.dev/2/#expanded-example
>
>
> --
> Gruß/Regards
>Thomas Schraitle
>
> -
> 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.
-
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org
[docbook-apps] Size?
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'?
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'?
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
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
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
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] How To Write Non-Unicode Symbol?
On Fri, 26 May 2023 at 15:54, Klaus Malorny wrote: > > On 26.05.23 16:12, Dave Pawson wrote: > > is simplest, assumes your document is utf-8 > > > > I hope that was only an example. U+1234 is a valid, existing > code point in Unicode, "ETHIOPIC SYLLABLE SEE". If you need a > placeholder until you know the code point in your custom font, use a > code point from the "private use areas", E000-F8FF, F-F or > 10-10FFFD. You didn't say. Options, use an entity or use xslt to 'map' that to something your presentation layer can understand? HTH -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] How To Write Non-Unicode Symbol?
is simplest, assumes your document is utf-8 HTH On Fri, 26 May 2023 at 15:01, Michael Urban wrote: > > What Unicode construct has the best semantics for representing an > oddball non-Unicode character? If I am writing a novel in which > there is a currency symbol, the Quatloo, represented by a glyph > from a custom font (say, a Q with three lines through it), how should > I write it? Q? > > It's inconsequential, since I can do whatever I please--this document > will not be exported to anyone, after all--but I'd like to get it 'right' > in some way. So, it's just a matter of my curiosity here. > > - > 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. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] Re: The semantics of mediaobject
On Thu, 6 Apr 2023 at 08:52, Norm Tovey-Walsh wrote: > > > In other words, I want a license to cheat and say that I can render that > > example above in HTML5 as a video element containing three sources, two > > videos and an image. What say you? > > Thank you, everyone, but the whole thing is predicated on a > misunderstanding. So forget it? Just one media as previously? regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] The semantics of mediaobject
On Thu, 6 Apr 2023 at 01:47, Bob Stayton wrote: > > It seems ok to me. The idea of a mediaobject is to contain markup for one or > more versions of the same content. Presenting more than one of those to the > end user would be redundant and annoying. If you consider the whole > rendering system to be the transformation from DocBook to HTML5 *and* the > browser rendering of that HTML5, then your use case does not seem to violate > the description because the consumer of the content sees only one version, > right? Relies on an odd (rare?) circumstance, despite being logical. Is there any backwards compatibility reason not to adopt Norms logic? regards > > Bob > > On 4/5/2023 9:27 AM, Norm Tovey-Walsh wrote: > > Hello world, > > The description of mediaobject states: > > This element contains a set of alternative “media objects.” Exactly > one object will be selected and rendered. … Under no circumstances > should more than one object in a mediaobject be used or presented at > the same time. > > Bearing in mind that this markup was invented 15 or 20 years ago, long > before any (widely used) web browser offered anything sophisticated in > the way of fallback, we anticipated that markup like this: > > > … > … > … > > > would be intepreted along the following lines: “… a mediaobject might > contain a video, a high-resolution image, a low-resolution image, a long > text description, and a short text description. In a ‘high-end’ online > system, the video is used. For print publishing, the high-resolution > image is used. For other online systems, either the high- or the > low-resolution image is used, possibly including the short text > description as the online alternative. In a text-only environment, > either the long or the short text description is used.” > > I observe that “possibly including the short text” is, by a very > narrow reading, a violation of the semantics we’ve already > asserted. > > Starting in V5.1 we allow more than one *data element in a *object > element[1] with the semantics that the downstream processor will pick > one. So now you can do: > > > > > > > … > … > > > And let the browser decide whether it wants to render MP4 or WebM. > > Trouble is, you can’t put imagedata in the videoobject wrapper, so > there’s no way to fallback to a still image. We could fix this by > changing videoobject (and audioobject) to allow imageobject, but at that > point, we might as well do away with the various flavors and just have > one wrapper. (That’s probably what we’d do today, if we were starting > over.) > > Rather than make the markup even more complicated, I’m tempted to squint > really hard at the semantics and try to persuade you that selecting > multiple objects from the same mediaobject is not a violation of the > semantics if the rendering system will only render one of them. > > In other words, I want a license to cheat and say that I can render that > example above in HTML5 as a video element containing three sources, two > videos and an image. What say you? > > Be seeing you, > norm > > [1] But the content model of imageobject weirdly forbids you from mixing > SVG and MathML and other formats. What is that about? > > -- > Norm Tovey-Walsh > https://norm.tovey-walsh.com/ > > Advancement is powered by the dynamic interaction of theory and > practice. -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook-apps] TOC placement in pdf
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
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
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] Allow as root element?
On Wed, 30 Nov 2022 at 20:16, Thomas Schraitle wrote: > Yes, it's always a balancing act between restricting the schema and to make it > flexible enough. > > I don't suggest nor endorse adding all and everything as start element. > However, maybe in the light of topic-oriented writing there might be elements > which could be useful to add like . > > I can fully understand that you don't want to change this. As another > alternative would be to offer two variants: the normal, DocBook schema and a > schema suited more for assembly and topic-oriented writing. Rather contrasting? You're not prepared to alter your schemas, your validation nor your stylesheets, yet you ask the group to alter docbook to suite your needs? regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] Allow as root element?
On Wed, 30 Nov 2022 at 12:51, Thomas Schraitle wrote: > > Your info 'root', I don't see how reasonable use would invalidate > > the use case (multiple) imports into n documents? > > Sure it can work. However, if I load a file with as root, my XML editor > _will_ complain. To avoid it, I'm forced to either a) make a DocBook > customization and allow , or b) wrap artificial structural DocBook > elements around. Both are problematic in their own ways as I was trying to > explain. I simply don't see how? Docbook is flexible and RNG allows v.easy customization? If your editor doesn't do what you want, use another tool? > > > > [...] > >> Yes, technically possible, but still a restriction. Additionally, I'm > >> forced to > >> add an XPointer expression into the element just to select the > >> info. Sounds like a detour to me. :) Sorry, not to me. Never used xpointer for such. Unsure why you need to link into the 'external' info section, especially the way you say you want to use it? > > > > No, sounds like you making use of xinclude and docbook for your own > > purposes? > > Something many of us do and have done for a long time. > > XIncludes aren't the problem per se. Maybe it works for your documents. I'm > glad it works for you. But not all documents are the same. If we can't use > as root, we are forced to do all sorts of workarounds. Perhaps it was > always the case. But you can with one line of rng? > > However, in terms of topic-oriented writing, it becomes annoying when you are > restricted by the schema. Which sounds like the schema is the problem? > > > > I'm not sure psychological 'barriers' are other than local use constraints? > > What I'm trying to say is, if we sell validation as sacred and as a good > thing, > we can't undermine this by allowing errors in another part, can we? Call it > constraints, psychological barriers, or whatever you like. :-) Validation is a tool to use for your own workflow. > > Probably it boils down to that DocBook allows many ways to process it. Some > produce valid results other invalid intermediate results or something in > between. DocBook doesn't define one way to do it, for the better or worse. For many of us (me included) it is for the better. I took the work the group did and adapted it for my use? Sounds like you could do the same and are quite resistant to such adaptation? regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] Allow as root element?
On Wed, 30 Nov 2022 at 10:55, Thomas Schraitle wrote: > > Hi, > > On 30.11.22 00:48, Richard Hamilton wrote: > IMHO, this is not a real technical issue (which could be theoretically solved > by adding to the list of start elements) but I suppose it's more of a > psychological factor. I fear, it would in a way undermine the trust of our > toolchain. Plus it creates some more burden on writers to dissect when to > ignore errors and when not. Or a burden on writers to take care what markup they use? Sounds reasonable? Your info 'root', I don't see how reasonable use would invalidate the use case (multiple) imports into n documents? > > > > The other thing you could do, if you’re using xinclude, is to put the info > > block into a valid root element, so you can validate it, then use xinclude > > to include just the info element when you build a deliverable. > > Yes, technically possible, but still a restriction. Additionally, I'm forced > to > add an XPointer expression into the element just to select the > info. Sounds like a detour to me. :) No, sounds like you making use of xinclude and docbook for your own purposes? Something many of us do and have done for a long time. I'm not sure psychological 'barriers' are other than local use constraints? regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] Direct rendering with CSS
Two stage? Do the linking in XSLT, then apply CSS? regards On Mon, 24 Oct 2022 at 17:46, David Cramer wrote: > > On 10/24/22 11:01 AM, Norm Tovey-Walsh wrote: > >> I haven't been paying attention recently: is anyone working on > >> rendering the original DocBook XML with CSS in the browser, and thus > >> bypassing the conversion stage altogether? > >> ... > >> I dunno. Maybe you could get pretty far. > > Is linking/cross-referencing also still a challenge with css and xml? I have > this memory of struggling with that long ago. > > If it's an option in your case, you could have a Saxon-JS viewer to do a > minimal amount of processing in the browser and avoid any build-time > conversion. https://www.saxonica.com/saxon-js/index.xml > > Regards, > > David > > > - > 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. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] R: [docbook] Attribute conditioning
Perhaps set a variable in the stylesheet (passed from the command line?) used to test when defining the output? Set to the output being processed? HTH On Mon, 12 Sept 2022 at 07:45, Matteo Regazzo wrote: > > Thank you Eric, > > I agree with you, the best solution in case of attributes that involve the > element output format is to act on the stylesheet and keep clean the xml > source of the document. > But what is the best solution when the attributes must be specified in the > document xml? > For example: > > For the pdf > For the html > > Thank you, > Matteo > > > > Matteo Regazzo > Service Coordinator > > Email: matteo.rega...@cmz.it | Web: www.cmz.it > Tel: +39 0422 447446 | Mob: > > CMZ Sistemi Elettronici srl > Via dell'Artigianato, 21 > Vascon di Carbonera (TV) > > The information transmitted, including attachments, is intended only for the > person(s) or entity to which it is addressed and may contain confidential > and/or privileged material. Any review, retransmission, dissemination or > other use of, or taking of any action in reliance upon this information by > persons or entities other than the intended recipient is prohibited. If you > received this in error please contact the sender and destroy any copies of > this information. > > > > -Messaggio originale- > Da: Eric Streit > Inviato: venerdì 9 settembre 2022 15:15 > A: > Oggetto: Re: [docbook] Attribute conditioning > > hi, > > I do exactly this, but I wrote 2 customization layers in the XSL parts one > for "fop" (pdf) and one for "html" html output. > > No need to add something in the original docbook (xml) file > > It's my solution; maybe your's is better > > Eric > > Le 09/09/2022 à 14:54, Matteo Regazzo a écrit : > > Hi everybody, > > > > I have a question (and I hope I’ll be able to explain my need). > > > > Is it possible to manage the attributes with a condition? > > > > For example (not real, just to simplify), imagine to have a long table as: > > > > > > > > … > > > > … > > > > … > > > > > > > > And you want to change one or more attributes of the element > > depending on the output format, something like > > > > if the output format is HTML > > > > if the output format is PDF > > > > Obviously, the solution of use a condition in the element is > > not praticable, because the whole table would be conditioned and we > > would need to write the entire table 2 times, one time per condition. > > > > > > > > … > > > > … > > > > … > > > > > > > > > > > > … > > > > … > > > > … > > > > > > > > Does it exists something similar to the following example, in the XLST > > world? > > > > > > > > > outputformat=”HTML”/> > > > > > outputformat=”PDF”/> > > > > … > > > > … > > > > > > > > Of course, I’m not asking a solution for ‘frame’ and ‘table’, but a > > generic one. Something I suppose could be a pre-processing, but in > > this case I should edit the toolchain, and I would prefer to avoid it… > > > > What is the best method to solve this problem? > > > > Thank you since now, > > > > Matteo > > > > > > > > Matteo Regazzo > > Service Coordinator > > Email: matteo.rega...@cmz.it| Web: www.cmz.it > > Tel: +39 0422 447446 CMZ Sistemi Elettronici srl > > Via dell'Artigianato, 21 > > Vascon di Carbonera (TV) > > 31050 ITALY > > <https://www.cmz.it> > > <https://www.sogaenergyteam.com/cmz/> > > > > > > <https://www.cmz.it/repairs/> > > From September 1, 2022 all products returned to CMZ must be approved > > in advance. > > Dal 1° Settembre 2022 tutti i materiali resi a CMZ devono essere > > approvati preventivamente. > > *www.cmz.it/repairs/* > > ------ > > -- The information transmitted, including attachments, is intended > > only for the person(s) or entity to which it is addressed and may > > contain confidential and/or privileged material. Any review, > > retransmission, dissemination or other use of, or taking of any action > > in reliance upon this information by persons or entities other than > > the intended recipient is prohibited. If you received this in error > > please contact the sender and destroy any copies of this information. > > > > - > 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. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook-apps] Language support in XSL-FO Stylesheets
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
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
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] RDFa Lite inside
The iAnnotate conf videos are online now. https://web.hypothes.is/blog/ianno21/ Quite a wide use. regards On Tue, 6 Jul 2021 at 07:36, Thomas Schraitle wrote: > > Hi, > > Am 03.07.21 um 11:21 schrieb Dave Pawson: > > [...] > > What's the logic for making metadata available in HTML please? > > (To me) metadata is for 'other purposes' than viewing? > > In an idea world, they would be extracted by search engines, for > example. Seems to some degree this is the case. > > > > > [...] > > > -- > Gruß/Regards > Thomas Schraitle -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook-apps] Do different xslt processors and parsers really make a difference for pdf output?
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] RDFa Lite inside
On Sun, 4 Jul 2021 at 12:53, Norm Tovey-Walsh wrote: > DocBook markup is a facility for making out-of-line > comments about a text. You can point from the annotation to the > annotated text, or from the annotated text to the annotation. What you > put *in* the annotations and what the annotations *mean* in the context > of *your document* is up to you! Which covers fully my wider definition. > > My intuitive feeling about them is that they’re something like > footnotes, but maybe not intended for the traditional presentation of > footnotes or maybe made by a third party and so not part of the actual > document, but about it. I agree with your caution Norm. What we do with them up to the user. Clever lot this docbook team :-) regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] RDFa Lite inside
On Sat, 3 Jul 2021 at 15:13, Peter Flynn wrote: > > > Why would I annotate book A with information about book B? > > Probably because they're in the same series, or you need to read one > before the other. Which is still information about this book, content refers to another? > Apart from title and author, IMNSHO metadata is often just tokens (like > the name="value" above) whereas annotations are more often more like > sentences. Yep, NSHO :-) IMO you're being parochial Peter? Far too narrow for a general use of annotations? regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] RDFa Lite inside
On Sat, 3 Jul 2021 at 10:35, Norm Tovey-Walsh wrote: > I’m quite pleased with the way the annotations are handled in the > annotated XML Catalogs specification I published last week: > https://xmlcatalogs.org/catalogs-1.1.html Agreed. Suggest s/handled/displayed/ :-) Very neat Norm. Is metadata a subset of annotations (or vice versa)? regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] RDFa Lite inside
Am I nitpicking? On Sat, 3 Jul 2021 at 10:35, Norm Tovey-Walsh wrote: > > And @ndw - what's your view on the relationship (difference) between > > metadata and annotations please? > > I tend to think of metadata as being about the document (this is it’s > title, this is it’s publication number, this is the set of keywords > related to it, etc.) and I tend to think of annotations as being > commentary for human readers. Of course, some metadata *is* usually for > human readers, like the document title, and you could write annotations > that weren’t intended for display. I can imagine using annotations, for > example, to track an editorial process but having them stripped out of > the final publication. I'd suggest both are (eventually) for human readers, and both are 'about' the document? Why would I annotate book A with information about book B? Graffitti? Redactions? Editorial notes? Study notes? All annotations. That's the broader interpretation I put on annotations now. > > I’m quite pleased with the way the annotations are handled in the > annotated XML Catalogs specification I published last week: > https://xmlcatalogs.org/catalogs-1.1.html I'll look more at that. regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] RDFa Lite inside
On Sat, 3 Jul 2021 at 10:17, Norm Tovey-Walsh wrote: > > Yes, the information should appear in the HTML source. If I'm not > > mistaken, RDFa Lite is currently not supported for the XSLT 1.0 > > stylehsheets. This would need a customization layer (which I already > > have). > > I’m pretty sure they’re supported by the xslTNG stylesheets. What's the logic for making metadata available in HTML please? (To me) metadata is for 'other purposes' than viewing? And @ndw - what's your view on the relationship (difference) between metadata and annotations please? regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] RDFa Lite inside
On Fri, 2 Jul 2021 at 10:00, Norm Tovey-Walsh wrote: > But that doesn’t answer your general question. > > > However, that feels like abusing the element. > > Yes, it does. > > > Maybe DocBook needs a general element soley for information that > > goes beyond the usual markup? Which could be used to distinguish between > > DocBook's own meta information and a foreign framework. Something like > > this: > > DocBook 5.2 introduces such an element which can either contain content > or be empty: > > https://tdg.docbook.org/tdg/5.2/meta.content.html > https://tdg.docbook.org/tdg/5.2/meta.empty.html > > It’s perhaps geared a little too strongly towards the HTML style of meta > element. It could probably be relaxed a little bit, so that name was > optional for example, to make it fit this use case a little better. Jon Udell and friends presented at https://iannotate.org/2021/ >From which I took a much more general meaning of annotations. For me, Thomas idea of using annotations within that wider definition makes sense. regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook-apps] insert.link.page.number in xsl stylesheets
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
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
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
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
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
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?
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?
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
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
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?
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?
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
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] Standard schema or format for product sheet
You might be better asking on the xsl list (mulberrytech) - a more general xslt list. HTH On Thu, 15 Oct 2020 at 08:57, Vincent Bouttard wrote: > > Hello Peter, > > Thank you for your answer. > > I'm working in a telescope dealer company in France. But I think that my > question is not specific to telescopes and astronomical items. this is > the case for all technical products, or generally all products (mainly > durable goods) which are sold over the Internet with E-Commerce > plateforms, from clothes to toasters. > > For many years, I wrote many product sheets about telescopes, > binoculars, accessories and all those product sheets look the same > structurally from a product to an other (short description, long > description, table of specifications and so on). And it could be applied > to other selling field like clothes, shoes, washing machines or > perfumes, perhaps with some little adjustment, from a dealer point of view. > So, I'm surprised not to find an XML "standard" for a "dealer" product > sheet. This is strange because all e-commerce platforms like Magento, > Prestashop, Wix (open-source) or Amazon, Aliexpress (closed systems) > organize their product sheets in the same way even in their databases > (at least for the open source ones). > > We have changed our e-business engine four times in my company, to > adjust our needs and our growth. Everytime, I had to format the product > sheets differently because the HTML output format for the new platform > was different (other HTML tags, other HTML attributes...). Reinventing > the wheel. > > So, in my opinion, XML is the best way to build "universal" product > sheets, due to its flexibility and the possibility to quickly and easily > convert XML document to another format for web or print purposes. And > DocBook is the best format I found for now to do that. > > Vincent > > > > Le 14/10/2020 à 17:36, Peter Flynn a écrit : > > On 14/10/2020 13:57, Vincent Bouttard wrote: > >> Hi all, I'm currently working in a company which sells technical > >> products through multiple distribution channels (shop, dealers and > >> e-shop) and I'm writing most of the product sheets. > > > > Are you able to say in what field of technology this is? > > > >> I would like to know if there is a standard or an existing schema to > >> format a product sheet in XML. I have created my own one few years > >> ago but I'm currently using DocBook to do that. It works fine but if > >> there is a "universal" and wide-used format for product sheet (with > >> schema and XSL/XSL-FO style sheets), I will consider to use it > >> instead of DocBook. > > > > We have done several for individual manufacturers over the years, in > > several different fields, but they have been bespoke proprietary > > layouts. I'm not aware of any global standard that covers everything, > > so if there is one, I'm missing something. > > > > There are certainly standards in specific industries (pharmaceuticals, > > chemistry, food, and others) with safety-related international > > standards which mandate many aspects of size, shape, and appearance > > for data sheets, like the Nutritional Information block on foodstuffs. > > These are usually mandatory, so it's an offence in law to do it wrong > > :-) There is ISO GUIDE 31:2015 "Reference materials" which is not a > > standard but a guide to how the information can be treated. > > > > There are also design trends over time: what was thought to be a very > > suitable product sheet in 1970 is possibly very different from what a > > designer would produce in 2020 (or maybe not — who knows?). > > > > But none of these would reference markup in any way, just appearance > > AFAIK. > > > > Peter > > > > - > > To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org > > For additional commands, e-mail: docbook-h...@lists.oasis-open.org > > > > > > > -- > Optique Unterlinden > 5, rue Jacques Daguerre > F-68000 Colmar > Phone : +33 3 89 24 16 05 > Fax : +33 3 89 29 33 10 > > > - > 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. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] Term DTD vs Schema in "DocBook V5.x XML DTD"
On Wed, 26 Aug 2020 at 13:37, Thomas Schraitle wrote: > > Additionally, even if we had a DTD for all versions, this wouldn't work > either. We have several, different schemas: DTD, RNG, SCH, NVDL, and XSD (5.0 > only). So I politely ask, if we could change that to a better term? What > about: > > DocBook V5.x XML Schemas > > Would that work? :) Thanks! I think so, and it would be (more) accurate. regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook-apps] Validating against Schematron
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?
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?
(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.
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]
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?
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
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?
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?
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?
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] Invalid links on page
Or https://www.w3.org/TR/xml-entity-names/ if appropriate On Mon, 7 Jan 2019 at 05:36, N. Raghavendra wrote: > > At 2019-01-05T18:51:39+01:00, Filippo Rusconi wrote: > > > I have many uses of Greek characters as I am currently converting a > > LaTeX document to DocBook. What is the most recent DocBook5 character > > entity listing available. I understand that people use the DB 4.5 > > version of the dbcent listing. Where can I find a reliable table of > > *all* the entities usable with DB 5.x ? > > Not specific to DocBook, and dated 2001, but you may find this useful: > > V. B. Gundersen and R. Mathisen, ISO character entities and their LaTeX > equivalents, http://www.bitjungle.com/isoent/index_files/isoent-ref.pdf > > Regards, > Raghu. > > -- > N. Raghavendra , http://www.retrotexts.net/ > Harish-Chandra Research Institute, http://www.hri.res.in/ > > - > 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. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook-apps] pubwork does not include a thesis
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
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
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
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
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)
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?
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] Inline address components
Not an address, as you say Peter. seems appropriate, since that's all it is? Happens to contain a village / town / city etc? HTH On Thu, 18 Oct 2018 at 09:16, Peter Fleck wrote: > > If I have some text like this: > > Lorem ipsum dolor sit amet, Edinburgh consectetur adipiscing Scotland > elit. Aenean eu finibus sapien. > > And I want to mark it up with semantic information for items like > or etc and not be displayed “verbatim”, to validate I currently would > need to put them in address: > > Lorem ipsum dolor sit amet, Edinburgh > consectetur adipiscing Scotland elit. > Aenean eu finibus sapien. > > For me, this context is not an address but I still want the semantic of > etc. Does it make sense to allow children to be a child of > as well? Or should I mark this type of semantic information > differently? For example, Edinburgh? > > Lorem ipsum dolor sit amet, Edinburgh consectetur > adipiscing Scotland elit. Aenean eu finibus sapien. > > Peter -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook-apps] Combining para role templates
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
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
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
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.
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
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
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
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.
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.
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.
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.
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.
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] Need help interpreting an error output
>From https://tdg.docbook.org/tdg/5.2/xref.html Under ordinary circumstances, the xref points to some element with its linkend attribute and the processing system generates appropriate cross-reference text. There are three ways for the author to influence the generated text: If the endterm attribute is specified on xref, the content of the element pointed to by endterm will be used as the text of the cross-reference. Otherwise, if the object pointed to has a specified xreflabel, the content of that attribute will be used as the cross-reference text. Finally, the author may specify a keyword (or other information) in the xrefstyle attribute. Unlike endterm and xreflabel which have rigid semantics, the content of the xrefstyle attribute is simply additional information for the processing system. What effect it has, if any, is dependent on the processing system. So the error is saying there is no text to 'make hot', e.g. Hot text HTH On Sun, 10 Jun 2018 at 07:54, openhab.doc wrote: > > Hi, > > > > wenn I run the following command for my docbook5 (relaxng) documents: > > > > xsltproc --xinclude --output Test.html > /usr/share/xml/docbook/xsl-ns-stylesheets-1.79.2/html/docbook.xsl > darktable.xml > > I get following error output: > > > > ERROR: xref linking to export_selected has no generated link text. > Error: no ID for constraint linkend: "export_selected". > ERROR: xref linking to lighttable_chapter has no generated link text. > Error: no ID for constraint linkend: "lighttable_chapter". > ERROR: xref linking to import has no generated link text. > Error: no ID for constraint linkend: "import". > ERROR: xref linking to export_selected has no generated link text. > Error: no ID for constraint linkend: "export_selected". > Error: no ID for constraint linkend: "image_information". > ERROR: xref linking to collect_images has no generated link text. > Error: no ID for constraint linkend: "collect_images". > ERROR: xref linking to recently_used_collections has no generated link text. > Error: no ID for constraint linkend: "recently_used_collections". > ERROR: xref linking to selected_images has no generated link text. > > > > What does it exactly mean? > > In the different documents I use for example the following commands: > > > > ./lighttable/panels/geotagging.xml:xml:id="geotagging"> > ./lighttable/panels/geotagging.xml: > > > ./lighttable/panels/panels.xml: xmlns:xi="http://www.w3.org/2001/XInclude"/> > > ./map/map.xml: geotagging > ./map/map.xml: (see ). > > > > Thanks for your help > > Pierre -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook-apps] Fwd: xslt2 stylesheets experience?
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?
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?
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] DTD from extended RNC
On 22 May 2018 at 02:17, N. Raghavendra <nyraghu27...@gmail.com> wrote: > That is Emacs for me. The choice is then between nXML mode and PSGML > mode. Since PSGML needs a DTD, since I have given up on writing a > customised DTD in favour of an RNC, and since `trang' does not convert > that RNC to a DTD, I have to give up on PSGML mode. So, I will > necessarily be using nXML mode. I am planning to separate out the nXML > code from the Emacs distribution into a local package, and modify it > incrementally in an attempt to add a few features Of note http://www.thaiopensource.com/download/ May be of use. The original nxml-mode, written for xml + rnc, NOT xhtml. HTH -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] DTD from extended RNC
On 21 May 2018 at 16:27, N. Raghavendra <nyraghu27...@gmail.com> wrote: > > Regarding a DTD for my extended schema, I have a few queries: > > 1. How difficult is it to start with a DocBook XML DTD, and extend it by > adding the elements I had mentioned, to get a new XML DTD? Can be done... I have not used a DTD for ... 10 years? > > 2. Is it possible to get a DTD for 5.1? The spec of DocBook 5.1 at > > http://docs.oasis-open.org/docbook/docbook/v5.1/os/docbook-v5.1-os.html > > says, "The Technical Committee provides the DocBook 5.1 schema in other > schema languages, including W3C XML Schema and an XML DTD, but the RELAX > NG Schema is the normative schema." The distribution at > > https://docbook.org/xml/5.1/ > > does not seem to have an XML DTD. DTD is yesterdays tool? > > 3. Is it important to use an editor that understands RELAX NG? I think so. YMMV? Sorry, many of us moved to RNG/C a long time ago, as a much better tool for more complex schemas? -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] DTD from extended RNC
On 21 May 2018 at 14:42, maxwell <maxw...@umiacs.umd.edu> wrote: > On 2018-05-21 08:17, Dave Pawson wrote: >> >>Anything you can do with a DTD you can do with rng/rnc. > > > But surely not in the opposite direction, correct? Which is presumably why > trang is complaining. Yes, rng is more recent / comprehensive than DTD's. > > FWIW, we had an analogous problem: we want to produce PDFs from XML > documents about linguistics. We chose DocBook as the base, and got rid of a > ton of things in the RNG/RNC that were irrelevant to our use case, then > added a few that we needed for linguistics. The authors of our linguistics > books use XMLmind (XXE), which I see someone else suggested. But you prefer > to stay with emacs, which is understandable. I myself use a programmer's > editor, but it doesn't do any schema validation (it does check for > well-formed XML); so I post-validate against the schema. Likewise. James Clarks original was syntax directed. I can't get that to work with the emacs version. If you want comprehensive syntax directed, oXygen is (IMHO) the best way to go. Do your transforms within the editor too. > > BTW, we looked into the usual XML-to-PDF via XSL stylesheets, and decided > they were not sufficient for our needs (right-to-left scripts embedded in > left-to-right text, complex scripts,...). Instead we use dblatex (not to be > confused with the older db2latex), which as the name suggests produces a > latex format, then use (xe)latex to produce the PDF. This of course also > needed modifications for our linguistic use case. There is one xsl-fo to PDF that might work for you, but it is pricy. HTH -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] DTD from extended RNC
On 21 May 2018 at 12:57, N. Raghavendra <nyraghu27...@gmail.com> wrote: > At 2018-05-21T12:45:46+01:00, Dave Pawson wrote: > >> There is a relax-ng mode in emacs? >> Spoiled somewhat from the James Clark original, >> but still usable? > > Yes, it is the nXML mode, originating from James Clark, and is a part of > Emacs. I have been using it in spite of its indentation quirks > https://lists.gnu.org/archive/html/help-gnu-emacs/2018-05/msg9.html > > However, I wanted to return to PSGML mode following some advice on > comp.text.xml: > https://groups.google.com/d/msg/comp.text.xml/SYhl-SKcKO0/q6oHMJhTBwAJ Peter is also on this list. IMHO he is biased :-) Anything you can do with a DTD you can do with rng/rnc. regards Dave > - > 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. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] DTD from extended RNC
There is a relax-ng mode in emacs?
Spoiled somewhat from the James Clark original,
but still usable?
HTH
On 21 May 2018 at 12:43, N. Raghavendra <nyraghu27...@gmail.com> wrote:
> I would like to use DocBook for a mathematics book. For that, I need to
> extend the DocBook 5.1 schema, to incorporate statements like
> "Definition", "Lemma", "Proposition", "Theorem", and "Corollary". I
> would like both RELAX NG and DTD versions of the extended schema; the
> DTD is necessary for the PSGML mode in Emacs.
>
> I have made a first attempt at extending the RNC. The resulting schema,
> which I've called `mono.rnc' is deemed valid by `jing':
>
> $ jing -c mono.rnc && echo "VALID"
> VALID
>
> I am also able to convert the RNC to an RNG with trang:
>
> $ trang mono.rnc mono.rng && echo "SUCCESS"
> SUCCESS
>
> Now, to use PSGML, I have to convert the RNC to a DTD. However, when I
> try to do that with `trang', the command aborts with several errors:
>
> $ trang mono.rnc mono.dtd
>
> /home/raghu/xml/xml/mono.rnc:14:1: error: sorry, combining definitions
> with combine="choice" is not supported
>
> /pkg/docbook/rng/docbookxi.rnc:264:6: error: sorry, ambiguous attribute
> choice not handled (attribute "type" from namespace
> "http://www.w3.org/1999/xlink;)
>
> [...]
>
> I have enclosed the schema `mono.rnc' below. I would be grateful if you
> have any suggestions. I have asked this question in an ongoing thread
> at comp.text.xml
>
> https://groups.google.com/d/msg/comp.text.xml/SYhl-SKcKO0/qpVJIKbCBQAJ
>
> but am posting it here, because this is the canonical place for the
> question.
>
> Thanks,
> Raghu.
>
> -- mono.rnc --
>
> # The namespace for all unqualified names. We use the prefix `db' for
> # it.
>
> default namespace db = "http://docbook.org/ns/docbook;
>
> ## Include the DocBook schema which allows XInclude.
>
> include "/pkg/docbook/rng/docbookxi.rnc"
>
> ## Add a new choice pattern `db.statement.blocks' to the pattern
> ## `db.formal.blocks'. This makes the `db.statement.blocks' pattern a
> ## valid option in any context where `db.formal.blocks' appears.
>
> db.formal.blocks |= db.statement.blocks
>
> ## The `db.statement.blocks' pattern is itself a choice pattern, whose
> ## values are the patterns that match definitions, theorems, etc.
>
> db.statement.blocks =
> db.corollary
> | db.definition
> | db.lemma
> | db.notation
> | db.observation
> | db.proposition
> | db.theorem
>
> ## Here is the definition of the individual values of the
> ## `db.statement.blocks' choice pattern.
>
> div {
> db.corollary = element corollary { db._statement.content }
>
> db.definition = element definition { db._statement.content }
>
> db.lemma = element lemma { db._statement.content }
>
> db.notation= element notation{ db._statement.content }
>
> db.observation = element observation { db._statement.content }
>
> db.proposition = element proposition { db._statement.content }
>
> db.theorem = element theorem { db._statement.content }
> }
>
> ## The content of an individual value of the `db.statement.blocks'
> ## choice pattern. Adapted from `db.example'.
>
> div {
> db._statement.content =
> db._statement.attlist
> , db._statement.info
> , db.all.blocks +
> , db.caption ?
>
> db._statement.attlist =
> db._statement.role.attribute ?
> & db.common.attributes
> & db.common.linking.attributes
> & db._statement.label.attribute ?
> & db._statement.floatstyle.attribute ?
> & ( db._statement.width.attribute | db._statement.pgwide.attribute ) ?
>
> db._statement.info = db._info.title.onlyreq
>
> db._statement.role.attribute = attribute role { text }
>
> db._statement.label.attribute = db.label.attribute
>
> db._statement.floatstyle.attribute = db.floatstyle.attribute
>
> db._statement.width.attribute = db.width.characters.attribute
>
> db._statement.pgwide.attribute = db.pgwide.attribute
> }
>
> -- mono.rnc ends here --
>
> -
> 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.
-
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] Which DocBook element to use for NICs?
Nothing obvious in https://tdg.docbook.org/tdg/5.2/ Not sure 'hardware' or ports are included in db? Extend db? Easy enough to do? HTH On 9 April 2018 at 11:10, David O'Brien <daobr...@redhat.com> wrote: > Anyone have any suggestions? > > e.g., eth0, docker0, eno1 > > Thanks > -- > > David > > "No one is dumb who is curious. The people who don't ask questions > remain clueless throughout their lives." > ~ Neil deGrasse Tyson > -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook-apps] Re: XML databases
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
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
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] Bad return address - is it yours?
Methinks thou hast! Thanks Chet. Dave On 12 March 2018 at 15:46, Chet Ensign <chet.ens...@oasis-open.org> wrote: > This reply is to test whether I have removed the culprit email subscriber. > > /chet > > On Sat, Mar 10, 2018 at 4:46 AM, Dave Pawson <dave.paw...@gmail.com> wrote: >> >> Each time I post I'm getting a wrng >> >> Your mail message to the following address(es) could not be delivered. >> This is a permanent error. Please verify the address(es) and try again. >> >> <goo...@outlook.com>: >> 104.47.41.33 does not like recipient. >> Remote host said: 550 5.5.0 Requested action not taken: mailbox >> unavailable. [DM3NAM03FT033.eop-NAM03.prod.protection.outlook.com] >> Giving up on 104.47.41.33. >> >> >> If it is you, please change it >> >> Tks >> >> -- >> Dave Pawson >> XSLT XSL-FO FAQ. >> Docbook FAQ. >> >> - >> To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org >> For additional commands, e-mail: docbook-h...@lists.oasis-open.org >> > > > > -- > > /chet > > Chet Ensign > Director of Standards Development and TC Administration > OASIS: Advancing open standards for the information society > http://www.oasis-open.org > > Primary: +1 973-996-2298 > Mobile: +1 201-341-1393 -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] copyright statement?
Thanks - so in a book with chapters / sections, I could repeat that for each chapter. I like that. regards On 10 March 2018 at 11:16, Thomas Schraitle <tom_s...@web.de> wrote: > Hi Dave, > > On Samstag, 10. März 2018 10:12:06 CET Dave Pawson wrote: >> Where's the most obvious place to put a copyright statement please? >> (or most usual?) >> root is book, db 5 > > I would use this: > > > > 2018 > Dave Pawson > > > > See also https://tdg.docbook.org/tdg/5.1/copyright.html > > -- > Gruß/Regards > Thomas Schraitle > > > > > - > 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. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
[docbook] Bad return address - is it yours?
Each time I post I'm getting a wrng Your mail message to the following address(es) could not be delivered. This is a permanent error. Please verify the address(es) and try again. <goo...@outlook.com>: 104.47.41.33 does not like recipient. Remote host said: 550 5.5.0 Requested action not taken: mailbox unavailable. [DM3NAM03FT033.eop-NAM03.prod.protection.outlook.com] Giving up on 104.47.41.33. If it is you, please change it Tks -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
[docbook] copyright statement?
Where's the most obvious place to put a copyright statement please? (or most usual?) root is book, db 5 TiA -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. - To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook] Once again tinkering with the DNS for docbook.org
Works for me Norm, 1930Z? docbook.org & www.docbook.org? regards On 6 March 2018 at 19:24, Norman Walsh <n...@nwalsh.com> wrote: > Hi folks, > > I was able to get the cdn.docbook.org and tdg.docbook.org subdomains > ported over to https: without changing the DNS servers for > docbook.org, but I think I am going to have to change it in order to > get docbook.org (and www.docbook.org) ported over. > > I think it’ll be relatively seamless, but in case it isn’t, fair > warning: I’ll be trying to make the changes next weekend > (10 March 2018). > > 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-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-h...@lists.oasis-open.org
Re: [docbook-apps] Re: Using the DocBook XSLT 2.0 stylesheets with Gradle
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
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
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
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
