[docbook-apps] [ANN] Call for proposals: XML Prague 2024
Dear XML enthusiasts, We are glad to announce that the call for proposals for the XML Prague 2024 conference is open now. The XML Prague conference is a three-day event on XML for developers, markup geeks, information managers and students. It will be held on June 6-8, 2024, at the Prague University of Economics and Business, W. Churchill sq., Prague, Czech Republic. The conference will include: - Two full days of single-track sessions on topics such as: * AI and markup * Markup and the Extensible Web * Semantic visions and the reality * Publishing for the 21st century * XML technologies and Big Data * State of the XML Union * XML success stories - A multitrack unconference day for informal discussions and networking The conference will provide an overview of successful technologies, with a focus on real-world applications versus theoretical exposition. You can find more information and submit your proposals on our conference website: https://www.xmlprague.cz CFP: https://www.xmlprague.cz/cfp/ Registration is open and you can enjoy early-bird prices: https://www.xmlprague.cz/conference-registration/ Please take note of the following important dates: April 2nd – End of CFP May 1st – Notification of acceptance/rejection May 27th – Final paper (for those who will provide it) June 6th–8th – XML Prague 2024 conference This year we would like to encourage new speakers. Full paper submission is no longer needed and there will be shorter slots available for those who would like to introduce or demo something “smaller”. If you have any questions, if you are interested in sponsorship or if you want to make a suggestion, please send an email to i...@xmlprague.cz We look forward to hearing from you and seeing you at the conference. Sincerely, Jirka Kosek on behalf of XML Prague crew OpenPGP_signature.asc Description: OpenPGP digital signature
Re: [docbook] Tagging social media IDs
On 15.09.2023 17:44, Peter Flynn wrote: In the absence of anything specific, I am temporarily using docbook without the "at" sign, and keeping the platform in the role attribute. Is it worth looking at adding Yet Another Element Type (eg ) with a controlled vocabulary for a "platform" attribute? or is it too early to define how we want to store and use these addresses? Hi Peter, you are right that there is not yet specific support for such kind of information in DocBook. Alternative to using element is to use @f...@mastodon.org You can also add @role attribute if you need to specify to which social platform username belongs. Alternatively as many social platforms provide URLs that corresponds to users you can use element, e.g. https://mastodon.org/@foo But I see that this might not very handy and you will have to customize stylesheets to strip leading part of URL for presentational purposes. Have a nice day, 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 -- OpenPGP_signature Description: OpenPGP digital signature
Re: [docbook-apps] Accented characters in HTML documentation
On 20.09.2023 21:47, Esteban Zimanyi wrote: In the resulting HTML on Github Pages https://mobilitydb.github.io/MobilityDB-workshop/ the accentuated characters have been replaced by � Any idea how to solve this? Most likely this is encoding issue. For legacy reasons DocBook stylesheets use ISO-8859-1 encoding whereas most current web serves expect that you upload content in UTF-8 encoding. Encoding can be easily changed, see http://www.sagehill.net/docbookxsl/OutputEncoding.html -- -- 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 -- OpenPGP_signature Description: OpenPGP digital signature
Re: [docbook] How to mark a programlisting non-translatable
On 19.05.2023 5:37, a.savch...@postgrespro.ru wrote: some program lines Please note that in HTML5 there is special attribute translate to indicate whether content should be translated or not: https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/translate some program lines in the declaration of the entire document. Could you please advice me how to command docbook to produce the HTML I need i.e. the pure class="programlisting highlight-shell notranslate">? Or maybe there's another way of marking a programlisting in docbook non-translatable? If you would like to prevent translation of all programlisting then the easiet is to modify stylesheets to emit translate="no" for each programlisting element transformed to . If you need fine grained control over each programlisting you can use its:translate attribute defined in ITS 2.0 (https://www.w3.org/TR/its20/): http://www.w3.org/2005/11/its; its:translate="on"> There is schema dbits.rng/rnc you could use instead of docbook.rng/rnc that included definitions of additional ITS elements/attributes. However I think that stylesheets currently doesn't support ITS attributes and they will not be propagated to HTML output. -- ------ 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 -- OpenPGP_signature Description: OpenPGP digital signature
Re: [docbook] The semantics of mediaobject
On 05.04.2023 18:27, 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? I think it's fair assumption given differences between HTML and DocBook content models and semantics. 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 -- OpenPGP_signature Description: OpenPGP digital signature
Re: [docbook-apps] DocBook xslTNG prerelease 2.0.7
On 07.02.2023 9:53, Norm Tovey-Walsh wrote: *Blink*. Really? I would not have expected language fixup to do that, but maybe it does. So xml:lang="" is equivalent to $default-language, I suppose. Well, I don't know if this is what XInclude spec says but IIRC there were some XInclude processors that did that. -- ------ 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 -- OpenPGP_signature Description: OpenPGP digital signature
Re: [docbook-apps] DocBook xslTNG prerelease 2.0.7
On 06.02.2023 20:07, Tony Graham wrote: If you look at line 145, $default-language is used if there's no $gentext-language and no @xml:lang. An empty @xml:lang would be used ahead of $default-language and would result in those empty values in the error message. Empty @xml:lang can be result of XInclude when included files do not explicitly specify @xml:lang. -- -- 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 -- OpenPGP_signature Description: OpenPGP digital signature
[docbook-apps] Re: ISO 690 bibliographies
On 31.12.2022 19:54, Norm Tovey-Walsh wrote: Back in 2012, there was some discussion of ISO 690 bibliography formatting. Someone named Jana Dvořáková apparently contributed a document with some proposed markup and the expected results to the DocBook wiki. That’s long lost, but I did manage to find an HTML version of that document in an email attachment from Jirka. Is Jana reading this list? Does anyone know how to reach them? Hi Norm, Jana was my student, I'm putting her on /cc. I’d like to put the document back on line, or get a pointer to where they’ve put it online. If it’s possible to get the DocBook source for that document, that would be nice too. I'm attaching file that I have found on my machine. It's from 2006, I'm not sure if there were some changes since that time that were lost when wiki version of doc has been lost. I’m about halfway through the examples from that document. I plan to support ISO 690 bibliographies in the DocBook xslTNG stylesheets. Cool! And Happy New Year. 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 -- Bibliography according to ISO 690 and ISO 690-2 standards Jana Dvořáková Introduction Examples are adapted from ISO 690 and ISO 690-2 standards. Elements marked with * are optional, + marks mandatory elements for online documents and optional for others. Monographs Non-serial bibliographic item, i.e. an item either complete in one part or complete (or intended to be completed) in a finite number of separate parts. ElementExample Primary responsibilityLOMINADZE, DG. TitleCyclotron waves in plasma *Subordinate responsibilityTranslated by AN. Dellis; edited by SM. Hamberger Edition1st ed. *Place of publicationOxford *PublisherPergamon Press Year of publication1981 *Extent206 p. *SeriesInternational series in natural philosophy *NotesTranslation of: Ciklotronnye volny v plasme Standard numberISBN 0-08-021680-3 DocBook source code Output according to ISO 690 standard LOMINADZE, DG. Cyclotron waves in plasma. Translated by AN. Dellis; edited by SM. Hamberger. 1st ed. Oxford: Pergamon Press, 1981. 206 p. International series in natural philosophy. Translation of: Ciklotronnye volny v plasme. ISBN 0-08-021680-3. Serials Publication, in any medium, issued in successive parts, usually having numeric or chronological designations, and intended to be continued indefinitely. ElementExample TitleCommunications equipment manufacturers ResponsibilityManufacturing and Primary Industries Division, Statistics Canada EditionPreliminary edition Issue designation (date and/or n°)1970- *Place of publicationOttawa *PublisherStatistics Canada Year of publication1971- *SeriesAnnual census of manufacturers *NotesText in English and French Standard numberISSN 0700-0758 DocBook source code Output according to ISO 690 standard Communications equipment manufacturers. Manufacturing and Primary Industries Division, Statistics Canada. Preliminary edition. 1970- . Ottawa: Statistics Canada, 1971- . Annual census of manufacturers. Text in English and French. ISSN 0700-0758. Parts of monographs ElementExample Primary responsibilityPARKER, TJ. and HASWELL, WD. Title of host documentA text-book of zoology Edition5th ed. Numeration of the partvol. 1 *Subordinate responsibilityrevised by WD. Lang *Place of publicationLondon *PublisherMacmillan Year of publication1930 Location within hostSection 12, Phylum Mollusca, p. 663-782 DocBook source code Output according to ISO 690 standard PARKER, TJ. and HASWELL, WD. A text-book of zoology. 5th ed., vol. 1. revised by WD. Lang. London: Macmillan, 1930. Section 12, Phylum Mollusca, p. 663-782. Contributions to monographs Contribution is independent unit forming part of a document. ElementExample for contribution: Primary responsibilityWRIGLEY, EA. TitleParish registers and the historian for host: Primary responsibilitySTEEL, DJ. TitleNational index of parish registers Edition *Place of publicationLondon *PublisherSociety of Genealogists Year of publication1968 Location within hostvol. 1, p. 155-167 DocBook source code Output according to ISO 690 standard WRIGLEY, EA. Parish registers and the historian. In STEEL, DJ. National index of parish registers. London: Society of Genealogists, 1968, vol. 1, p. 155-167. Articles, etc., in serials ElementExample Primary responsibilityWEAVER, William TitleThe collectors: command performances
Re: [docbook] State of topic oriented writing in DocBook?
On 30.11.2022 15:25, Jean-Christophe Helary wrote: It seems to me that there could be a mechanism where xi:include manages included IDs by generating some kind of "name space" over the whole document, maybe based on the "includee" part ID. I can see how linking to such IDs form other parts could be non-trivial, but conversely, I don't see the point of trying to link to an ID that will be included in multiple places in a document, so maybe the point is moot. Well this is already supported by XInclude and transclusion mechanism, see: https://docbook.org/docs/transclusion/transclusion.html#ex.6 xslTNG support this mechanism, when enabled by the following option: https://xsltng.docbook.org/guide/p_docbook-transclusion.html Does this solve your use-case? -- ------ 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 -- OpenPGP_signature Description: OpenPGP digital signature
Re: [docbook] State of topic oriented writing in DocBook?
On 30.11.2022 10:49, Thomas Schraitle wrote: It's sometimes frustrating to see that DocBook is halfway there but is missing this extra mile that you need. I would really like to see solutions in DocBook that supports a more topic oriented writing experience. I think that one of the reasons that topic oriented authoring is not 100% perfect in DocBook is that many core DocBook developers are not using this feature on their own projects. So unless there is report of missing or broken functionality there is no push to improve situation. May be good start would be if you will specifically list feature that you are missing or that are broken in some tool. 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 -- OpenPGP_signature Description: OpenPGP digital signature
Re: [docbook] Direct rendering with CSS
On 24.10.2022 18:01, Norm Tovey-Walsh wrote: You’d have to place elements (for example: title, subtitle, author, etc.) in the right order because CSS can’t reorder them. Any rendering that required reordering (footnotes, epigraph attributeions, some synopsis elements, some mediaobjects) wouldn’t work. Actually CSS flexbox and order property can be used for reordering. But images and links still will be problem. That would need Javascript. -- -- 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 -- OpenPGP_signature Description: OpenPGP digital signature
Re: [docbook] Attribute conditioning
On 09.09.2022 14:54, Matteo Regazzo wrote: if the output format is HTML if the output format is PDF You would usually use profiling for this, but for handling attribute values it is not very practical as profiling condition is attached to a whole element not only to single attribute. Does it exists something similar to the following example, in the XLST world? … … It would be better to use processing instruction for this, otherwise your document will not be valid DocBook, i.e. With such markup it would be quite easy to modify profiling step in the stylesheets to add desired attributes to a parent element. 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 -- OpenPGP_signature Description: OpenPGP digital signature
[docbook-apps] [ANN] Last week to submit for XML Prague 2022
Hi, there is still one week to think and work on your submission for XML Prague 2022. Call for proposals (open till April 12th): https://www.xmlprague.cz/cfp/ Instructions for authors: https://www.xmlprague.cz/instructions-for-authors/ Registration is open and early-bird tickets available till end of April: https://www.xmlprague.cz/conference-registration/ If you have any questions, interested in sponsorship or just want to make a suggestion please send email to: i...@xmlprague.cz Jirka Kosek on behalf of XML Prague -- -- 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 -- OpenPGP_signature Description: OpenPGP digital signature
[docbook-apps] [ANN] XML Prague 2022 - Call for Proposals
Hello,
we are glad to announce that call for proposals for XML Prague 2022
conference is open now.
The XML Prague conference will include two full days of single track
sessions as well as a multitrack unconference day.
The conference is held on the Thursday, Friday and Saturday (June
9-11, 2022),
located at the University of Economics, nam. W. Churchilla, Prague,
Czech Republic.
XML Prague is a conference on XML for developers, markup geeks,
information managers, and students. XML Prague focuses on markup and
semantic on the Web, publishing and digital books, XML technologies for
Big Data and recent advances in XML technologies. The conference
provides an overview of successful technologies, with a focus on real
world application versus theoretical exposition.
This years topics include the following:
* Markup and the Extensible Web
* Print publishing
* Semantic visions and the reality
* Publishing for the 21st century
* XML technologies and Big Data
* State of the XML Union
* XML success stories
Conference website: https://www.xmlprague.cz
Call for proposals: https://www.xmlprague.cz/cfp/
Registration: https://www.xmlprague.cz/conference-registration/
Please take note of the following important dates:
April 12th – End of CFP
May 9th – Notification of acceptance/rejection
June 1st – Final paper (for those who will provide it)
June 9–11 – XML Prague 2022 conference
This year we would like to encourage new speakers -- full paper
submission is no longer needed and there will be shorter slots available
for those who would like to introduce/demo something "smaller".
If you have any questions, interested in sponsorship or just
want to make a suggestion please send email to: i...@xmlprague.cz
Jirka Kosek
on behalf of XML Prague
--
--
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
--
OpenPGP_signature
Description: OpenPGP digital signature
[docbook-apps] [ANN] XML Prague 2022 - Call for Proposals
Hello,
we are glad to announce that call for proposals for XML Prague 2022
conference is open now.
The XML Prague conference will include two full days of single track
sessions as well as a multitrack unconference day.
The conference is held on the Thursday, Friday and Saturday (February
10-12, 2022),
located at the University of Economics, nam. W. Churchilla, Prague,
Czech Republic.
XML Prague is a conference on XML for developers, markup geeks,
information managers, and students. XML Prague focuses on markup and
semantic on the Web, publishing and digital books, XML technologies for
Big Data and recent advances in XML technologies. The conference
provides an overview of successful technologies, with a focus on real
world application versus theoretical exposition.
This years topics include the following:
* Markup and the Extensible Web
* Print publishing
* Semantic visions and the reality
* Publishing for the 21st century
* XML technologies and Big Data
* State of the XML Union
* XML success stories
Conference website: https://www.xmlprague.cz
Call for proposals: https://www.xmlprague.cz/cfp/
Registration will be opened soon.
Please read important info related to turbulent situation around covid
restrictions:
https://www.xmlprague.cz/2021/10/27/xml-prague-2022/
Please take note of the following important dates:
December 20th – End of CFP
January 9th – Notification of acceptance/rejection
January 31st – Final paper (for those who will provide it)
February 10-12 – XML Prague 2022 conference
This year we would like to encourage new speakers -- full paper
submission is no longer needed and there will be shorter slots available
for those who would like to introduce/demo something "smaller".
If you have any questions, interested in sponsorship or just
want to make a suggestion please send email to: i...@xmlprague.cz
Jirka Kosek
on behalf of XML Prague
--
------
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
--
-
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
On 11.5.2021 11:16, Norm Tovey-Walsh wrote: 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. Yep, it seems that the XSLT code wasn't updated to the latest translusions draft that is based on XInclude 1.1. As a namespace changed between drafts the most recent XSLT code isn't doing anything. But XSLT transformation at the end of DocBook Transclusion document should be doing right thing so using it as an almost drop-in replacement could do the trick. 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. I have one customer who uses original proposal with DocBook 4.3 and XSLT 1.0 stylesheets -- they will not be affected by any change for foreseable future ;-) -- -- 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 -- OpenPGP_signature Description: OpenPGP digital signature
Re: [docbook-apps] Thumb index
[Putting the discussion back to the list] On 23.7.2020 10:52, Bernhard Kleine wrote: > I am unable to locate the template named footer.table in the entire > Oxygen 20.1 directory. I am confused. Please where do I have to look? In fo/pagesetup.xsl file: https://github.com/docbook/xslt10-stylesheets/blob/master/xsl/fo/pagesetup.xsl > When I started a new template footer.table and inserted your code, it > choked on this line: variable not found! You have to copy original template from the file above into your customization layer and then add thumb register snippet above the following line: -- ------ 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 -- - 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] Thumb index
On 20.7.2020 18:20, Tony Graham wrote: > The 'mod 7' in Jirka's solution restarts the positioning after 7 > chapters. Have you tried it? Thanks Tony for further clarification. I have been in rush and haven't time to comment much on my example. For positioning of thumb index the following code is cruical: mm mod 7 -- means that after each 7 chapters/appendices/... thumb index will be moved back to the top of a page 28 -- is height of thumb index (in mm) 18 -- is intial offset (in mm) -- ------ 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Thumb register
On 19.7.2020 19:13, Bernhard Kleine wrote: > I have used a thumb register in a book produced with LaTeX. That was > fairly straight forward. I wonder whether this is also possible with > docbook -> PDF. Is there a solution already? I suppose your are using FO based output of DocBook XSLT 1.0 stylesheets. It depends on what you want to display in thumb index, but if you will put the following code into existing footer.table named template you will get chapter number and title in the thumb index (see https://books.google.cz/books?id=x93yCgAAQBAJ=PA1=big%20data%20a%20nosql%20datab%C3%A1ze=PA21#v=onepage=big%20data%20a%20nosql%20datab%C3%A1ze=false for preview): mm . -- ------ 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 -- - 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] More roles at one section
On 14.6.2020 9:26, Pavel Vávra wrote: > I need to hide some sections from TOC. It can be solved by assigning a role > to section, eg. role hideTOC. I need to print some sections together on one > page, which is now done by another role NoPgBreak (see my previous question). > Now I need to combine both roles at one section. Is it possible by > combining these roles? How to test it in xsl? I have an idea thet i set role > "NoPgBreak, hideTOC" and then I test if role *contains string* 'hideTOC' > instead *it is equal* to 'hideTOC' and vice versa. Is it possible in xsl > language? Searching in tutorials at web didn't bring me answer. Indeed, it's definitively possible in XSLT. Unfortunatelly stylesheets you are using are written in XSLT 1.0 where such easy comparision must be written in a rather awkward way (it would be much easier to do this in XSLT 2.0/3.0). Separate values in role attribute by spaces, e.g. Then in conditions use something like Be careful about spaces above. They make sure that tokens in role atttribute can be even substring of each other and condition will still work properly. -- ------ Jirka Kosek e-mail: ji...@kosek.cz http://www.kosek.cz -- Profesionální školení a poradenství v oblasti technologií XML. Podrobný přehled školení http://xmlguru.cz/skoleni/ -- http://docbook.czStránky o dokumentačním formátu DocBook http://xmlguru.czBlog mostly about XML for English readers -- smime.p7s Description: S/MIME Cryptographic Signature
Re: [docbook-apps] Section at new page with exceptions
On 10.6.2020 14:35, Pavel Vávra wrote: > > page > > > ... but some small set of sections is much shorter than one page and I want > print them on one page together with previous one. Is it possible to do it > e.g. marking these sections with a role 'NoPgBreak'? What I need to add to my > xsl transformation to make it work? You can use something like: auto page -- ------ Jirka Kosek e-mail: ji...@kosek.cz http://www.kosek.cz -- Profesionální školení a poradenství v oblasti technologií XML. Podrobný přehled školení http://xmlguru.cz/skoleni/ -- http://docbook.czStránky o dokumentačním formátu DocBook http://xmlguru.czBlog mostly about XML for English readers -- signature.asc Description: OpenPGP digital signature
[docbook-apps] Re: Using XSL parameter inside XSL attribute?
On 12.2.2020 17:26, oa...@docbook-autor.de wrote: > But I'm looking for a way to use the parameter $foo as part of an fo > attribute, e.g.: > > > > where "###" is the value of the parameter $foo. You can use attribute value template for this -- curly braces have special meaning inside attributes: -- ------ 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 -- smime.p7s Description: S/MIME Cryptographic Signature
Re: [docbook-apps] XSLT cannot find UnwrapLinks.so
On 11.12.2019 10:10, Frank Arensmeier wrote:
> When observing a HTML build with strace, I see a ridiculous large number of
> entries like this:
>
> stat("/usr/lib/libxslt-plugins/nwalsh_com_xslt_ext_com_nwalsh_saxon_UnwrapLinks.so",
> 0x7ffc9f117ee0) = -1 ENOENT (No such file or directory)
>
> That plugin seems dead
> (http://nwalsh.com/xslt/ext/com.nwalsh.saxon.UnwrapLinks
> <http://nwalsh.com/xslt/ext/com.nwalsh.saxon.UnwrapLinks>). Can someone shed
> some light on this? Why would you need that plugin? Can you download that
> plugin somewhere?
To me it seems that libxslt is trying to load Saxon extension -- perhaps
it does this during the following code
function-available('suwl:unwrapLinks')
As this extension is not suitable for libxslt nothing is done.
> We have very large HTML builds (80MB XML Docbook files). I am concerned that
> this might have a negative impact on build time.
I suppose with advanced filesystem caching available check for existence
of file should be very cheap operation. But if this is concern for you
you can try to delete all calls to
function-available('suwl:unwrapLinks') and corresponding branches in the
code and see if there is a difference.
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
--
signature.asc
Description: OpenPGP digital signature
Re: [docbook-apps] saxon6:output for running DocBook 1.0 xslts using Saxon 9.9
On 29.10.2019 2:11, David Cramer wrote: > I just stumbled on this (haven't tried it out yet though). It could be > I'm the last to hear about it, but I thought I'd post it just in case. > If you wanted to use your existing customization layer with Calabash, > for example, now you can :-) Hi David, thanks for pointing this out. It is interesting addition to Saxon, unfortunatelly available only PE/EE edition. Anyway I have created issue from this, so this is not being forgotten: https://github.com/docbook/xslt10-stylesheets/issues/172 But of course this doesn't imply that this will be fixed soon :-( 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 -- - 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] [ANN] XML Prague 2020 - Call for Proposals
Hello,
we are glad to announce that call for proposals for XML Prague 2020
conference is open now.
The XML Prague conference will include two full days of single track
sessions as well as a multitrack unconference day.
The conference is held on the Thursday, Friday and Saturday (February
13-15, 2020),
located at the University of Economics, nam. W. Churchilla, Prague,
Czech Republic.
XML Prague is a conference on XML for developers, markup geeks,
information managers, and students. XML Prague focuses on markup and
semantic on the Web, publishing and digital books, XML technologies for
Big Data and recent advances in XML technologies. The conference
provides an overview of successful technologies, with a focus on real
world application versus theoretical exposition.
This years topics include the following:
* Markup and the Extensible Web
* Print publishing
* Semantic visions and the reality
* Publishing for the 21st century
* XML technologies and Big Data
* State of the XML Union
* XML success stories
Conference website: https://www.xmlprague.cz
Call for proposals: https://www.xmlprague.cz/cfp/
Registration is already opened at:
https://www.xmlprague.cz/conference-registration/
Please take note of the following important dates:
December 9th – End of CFP
January 9th – Notification of acceptance/rejection
January 31st – Final paper (for those who will provide it)
February 13-15 – XML Prague 2020 conference
This year we would like to encourage new speakers -- full paper
submission is no longer needed and there will be shorter slots available
for those who would like to introduce/demo something "smaller".
If you have any questions, interested in sponsorship or just
want to make a suggestion please send email to: i...@xmlprague.cz
Jirka Kosek
on behalf of XML Prague
--
------
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
--
signature.asc
Description: OpenPGP digital signature
Re: [docbook] Status of XInclude 1.1?
On 14.5.2019 14:11, Thomas Schraitle wrote: > Unfortunately, it's still in candidate recommendation (June 2015, would > be 4 years). I also found a working group note[2]; does it replace(?) > the old document? Was the old spec downgraded from CR to a note? W3C usually publishes notes when there is no future work planned on some specification that hasn't yet reached Recommendation status. Unfortunatelly Norm has to left working group before reaching Recommendation status. (https://lists.w3.org/Archives/Public/public-xml-core-wg/2016Jun/0001.html) Because W3C terminated all XML related activities there is no working group that can finish this. > Norman, as you worked on this specification, do you know any details? > Is it still "valid"? Will it be implemented in some parsers? Can we > use it some day? Some tools already implement XInclude 1.1 -- I think that at least Calabash, oXygen and XML Mind. So as long as your toolchain support features you need from XInclude 1.1 you can use it. -- ------ 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Relative paths when processing DocBook 5 with DocBook 4 stylesheets
On 11.6.2019 23:19, Jan Tosovsky wrote: > In my case all relative images has become absolute. > Or are there better/built-in ways? Well this is tricky area. I would suggest switching to "ns" flavour of stylesheets where there is no such problem. Alternatively you can see whether the following parameter would work in your case: http://docbook.sourceforge.net/release/xsl/current/doc/html/keep.relative.image.uris.html -- ------ Jirka Kosek e-mail: ji...@kosek.cz http://www.kosek.cz -- Profesionální školení a poradenství v oblasti technologií XML. Podrobný přehled školení http://xmlguru.cz/skoleni/ -- http://docbook.czStránky o dokumentačním formátu DocBook http://xmlguru.czBlog mostly about XML for English readers -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Footnote marks missing
On 11.2.2019 10:03, Bernhard Kleine wrote: > I did as you advised. I found the offending template: > > anpassen -\-> This templates overrides the following template that injects footnote marks into the footnote: The easiest fix would be to change match attribute in your template to d:para[not(parent::d:footnote)] 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] I have paragraphs that contains MarkDown. Is there a way in the XSLT to process them as markdown?
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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Re: Some beginner questions for db xslt20-stylesheets
On 17.12.2018 9:11, Norman Walsh wrote: >> 4. Is it possible to do source code highlighting in docbook? > > In the browser, yes. I don’t think there’s a solution for doing it in > print at the moment. XSLTH library (https://sourceforge.net/projects/xslthl/) used by XSLT 1.0 stylesheets has Saxon9 connector, so in theory it can be integrated into XSLT 2.0 styleshets as well. -- ------ 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 -- signature.asc Description: OpenPGP digital signature
[docbook-apps] [ANN] XML Prague 2019 - Call for Proposals - deadline coming soon
Hi,
this is gentle reminder that you have this weekend to submit your
proposals for XML Prague.
The XML Prague conference will include two full days of single track
sessions as well as a multitrack unconference day.
The conference is held on the Thursday, Friday and Saturday (February
7-9, 2019),
located at the University of Economics, nam. W. Churchilla, Prague,
Czech Republic.
XML Prague is a conference on XML for developers, markup geeks,
information managers, and students. XML Prague focuses on markup and
semantic on the Web, publishing and digital books, XML technologies for
Big Data and recent advances in XML technologies. The conference
provides an overview of successful technologies, with a focus on real
world application versus theoretical exposition.
This years topics include the following:
* Markup and the Extensible Web
* Semantic visions and the reality
* Publishing for the 21st century
* XML technologies and Big Data
* State of the XML Union
* XML success stories
Conference website: http://www.xmlprague.cz
Call for proposals: http://www.xmlprague.cz/cfp/
Registration will be opened soon.
Please take note of the following important ates:
December 2nd – End of CFP
January 9th – Notification of acceptance/rejection
January 31st – Final paper (for those who will provide it)
February 7-9 – XML Prague 2019 conference
This year we would like to encourage new speakers -- full paper
submission is no longer needed and there will be shorter slots available
for those who would like to introduce/demo something "smaller".
If you have any questions, interested in sponsorship or just
want to make a suggestion please send email to: i...@xmlprague.cz
Jirka Kosek
on behalf of XML Prague
--
------
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
--
signature.asc
Description: OpenPGP digital signature
Re: [docbook] DocBook 5.1 Schematron schema
On 24.11.2018 7:47, N. Raghavendra wrote: > I am looking for a Schematron schema for DocBook 5.1, that has all the > rules from docbookxi.rng. The file docbookxi.sch that comes with the > DocBook distribution doesn't have, e.g., "Root must have version" rules. > Is a more complete Schematron schema available? Hi Raghu, this should be only rule missing in Schematron files. The problem was caused by a bug in the build system that has been recently fixed: https://github.com/docbook/docbook/commit/3b0b251c3094406c7f527828aa45303260dcb19f Any future releases would contain Schematron schemas with rules checking for version attribute. If you don't want to wait you can extract all Schematron rules from RELAX NG files by using tools like ExtractSchFromRNG.xsl 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] DocBook content review process/tools?
On 23.10.2018 18:53, Peter Desjardins wrote: > Do you have a great DocBook-based review process? oXygen Web Author https://www.oxygenxml.com/xml_web_author.html provides editing, revision tracking and commenting features running in the browser. They have also git backend. Recently they have introduced tool that handles whole review workflow: https://www.oxygenxml.com/content_fusion.html 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 -- signature.asc Description: OpenPGP digital signature
[docbook-apps] [ANN] XML Prague 2019 - Call for Proposals
Hello,
we are glad to announce that call for proposals for XML Prague 2018
conference is open now.
The XML Prague conference will include two full days of single track
sessions as well as a multitrack unconference day.
The conference is held on the Thursday, Friday and Saturday (February
7-9, 2019),
located at the University of Economics, nam. W. Churchilla, Prague,
Czech Republic.
XML Prague is a conference on XML for developers, markup geeks,
information managers, and students. XML Prague focuses on markup and
semantic on the Web, publishing and digital books, XML technologies for
Big Data and recent advances in XML technologies. The conference
provides an overview of successful technologies, with a focus on real
world application versus theoretical exposition.
This years topics include the following:
* Markup and the Extensible Web
* Semantic visions and the reality
* Publishing for the 21th century
* XML technologies and Big Data
* State of the XML Union
* XML success stories
Conference website: http://www.xmlprague.cz
Call for proposals: http://www.xmlprague.cz/cfp/
Registration will be opened soon.
Please take note of the following important ates:
December 2nd – End of CFP
January 9th – Notification of acceptance/rejection
January 31st – Final paper (for those who will provide it)
February 7-9 – XML Prague 2019 conference
This year we would like to encourage new speakers -- full paper
submission is no longer needed and there will be shorter slots available
for those who would like to introduce/demo something "smaller".
If you have any questions, interested in sponsorship or just
want to make a suggestion please send email to: i...@xmlprague.cz
Jirka Kosek
on behalf of XML Prague
--
------
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
--
signature.asc
Description: OpenPGP digital signature
Re: [docbook-apps] How to make chemical structure automatically numbered
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. -- ------ 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 -- signature.asc Description: OpenPGP digital signature
[docbook] New schema release V5.2b05
Hi, I'm glad to announce that new beta schema release is available at: https://docbook.org/xml/5.2b05/ Implemented changes are comming from the following issues: https://github.com/docbook/docbook/issues/91 https://github.com/docbook/docbook/issues/102 https://github.com/docbook/docbook/issues/94 Please report any bugs and comments here on using github issues. Have a great day, 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook] Help needed with screeninfo and informaltable in docbook5
On 5.6.2018 21:17, openhab.doc wrote: For your explanation. I'm a little surprised that width is possible on docbook > 4.5. Is there a other possibility to set the table width in CALS tables > (docbook 5)? Bob provided the working solution. Just to explain why this was possible on DocBook 4.5 -- HTML tables were added into 4.5 as well (I forgot that) and thus width attribute was available on table. But because limitations of DTD validation was not perfect and can't detect situation when attribute from HTML tables has been used on CALS table. 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Convert CSL styles to Docbook stylesheet
On 6.6.2018 20:22, Peter Fleck wrote: > I wonder if it would be much work to convert the wealth of resources of > Bibliography styles using the CSL XML (Citation Style Language) on Zotero > to Docbook templates in the same manner as the ISO690 . There is over 9000 > styles there at the moment - https://www.zotero.org/styles/ but if we could > even get a few of the main styles like APA, MLA, Chicago, they would be of > immense benefit. > > Here for example is Chicago - > https://www.zotero.org/styles/chicago-fullnote-bibliography?source=1 Looking at the examples it should be possible to write transformation that would convert CSL style into XSLT customization of DocBook citation styles (similar to ISO690 support in the stylesheets). But this would take significant effort. -- ------ 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook] Help needed with screeninfo and informaltable in docbook5
On 5.6.2018 7:58, openhab@web.de wrote:
> _docbook5 apaption:_
> /
> /
> /
>
> The map view
>
>/
> /
>
> width="80%" />
>
>/
> /
>/
Seems correct. It's not necessary to wrap title inside info element.
> *2.)* My second Problem is that emacs mark "width" in an informaltable as non
> valid.
> / /
> How do I change this to make it docbook5 compliant?
In DocBook 5.0 you can use either HTML table model or CALS table model.
In DocBook 4.x you were limited to CALS only. In your example you are
mixing both models -- width is allowed only in HTML table model, whereas
frame="none" is allowed in CALS. If you want to use HTML table model you
have to change to frame="void" as values allowed for frame attribute
differ between CALS and HTML table models.
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
--
signature.asc
Description: OpenPGP digital signature
Re: [docbook-apps] Fwd: xslt2 stylesheets experience?
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. 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Chinese Index
On 1.6.2018 14:28, Maxime Bégnis wrote: > but that class is missing from the archive given in the page from the > DocBook wiki. i18n_support.jar does not contain it. I found some > references to it in the sources but it's not there. > > So the stylesheet terminates with with the xsl:message on line 69 > (docbook-xsl-ns-1.75.2) I would suggest using more recent stylesheet distribution. Also you might find additional clues in a recent related thread: https://markmail.org/search/?q=docbook%20kosek#query:docbook%20kosek%20list%3Aorg.oasis-open.lists.docbook-apps%20from%3A"Jirka%20Kosek"%20order%3Adate-backward+page:1+mid:um5p2ru2xdym7cxh+state:results 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook] Help needed to use ENTITY in docbook5 (convert from docbook4)
On 25.5.2018 9:23, victory wrote: > I think this is caused by this change: > https://github.com/docbook/docbook.org/issues/17 Please note that there were not made change. The problem is that with DocBook 4 people usually used external entities to break document into several smaller files. If this approach is used entities defined in the main file are inherited to files included via entity mechanism. For DocBook 5 XInclude is usually used for modularity. With XInclude situation is different. Each xincluded file is parsed separately and does not inherit entity declarations from the main file. So with XInclude entity declarations has to be repeated at the beginning of each file. But in fact this is not directly related to differences between DocBook 4 and 5. You can use XInclude with DocBook 4 or external entities with DocBook 5. But using entities for accented characters in 2018 seems really wrong. Appropriate Unicode characters should be used directly in the files. 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Japanese index
On 25.4.2018 11:57, Tony Graham wrote: > Sorry, but I've never used it, so all that I know is what's on the website. I see. After digging some old emails I have been able to find this link: https://www.antennahouse.com/i18n-support-library-2/ It contains open-source part of library that should be working with "kimber" method in the stylesheets. This could provide Jan with correct Japanese indexing. -- -- 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Japanese index
On 24.4.2018 21:53, Tony Graham wrote: >> But it is still unclear how to tweak the index code to generate groups >> from >> non-latin characters. > > I don't know, either. DocBook stylesheets support three methods of indexing, see: http://www.sagehill.net/docbookxsl/IndexIntl.html In "kosek" method you can easily define groups based on the first or first two characters of indexed words. Unfortunately there is currently no suitable definition for Japanese. And my Japanese knowledge is not enough to create such definition. But internals of this methods are described in the following paper: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.131.2069=rep1=pdf This might give you enough clue to adapt it to Japanese. If you will be successful it would be great if you can contribute definitions back to the stylesheets. Feel free to contact me if you need more info. > It's probably not what you want to hear, but Antenna House does have a > commercial product for doing DocBook indexes: > > https://www.antennahouse.com/antenna1/i18n-index-library/ Isn't this newer version of library that is needed for "kimber" indexing method? I though that Elliot intended to convince AH to make this library open-source, but it seems that my memory is wrong. -- ------ 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook] Re: Which DocBook element to use for NICs?
On 20.4.2018 7:46, Thomas Schraitle wrote: > An alternative notation would be: > > eth0 OP asked about DocBook V4.5 -- otherclass has been introduced in DocBook V5.x. > What about adding "interface" to the available values of the class > attribute for future DocBook versions? You are free to fill new issue ;-) -- ------ 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 -- signature.asc Description: OpenPGP digital signature
[docbook] Re: Which DocBook element to use for NICs?
On 9.4.2018 12:10, David O'Brien wrote: > Anyone have any suggestions? > > e.g., eth0, docker0, eno1 Definitively systemitem. For DocBook 4.x reference page is at: https://tdg.docbook.org/tdg/4.5/systemitem.html eth0 You can use class attribute to be more specific about value inside systemitem. If there is nothing suitable for you in this list, you can still use rola attribute and invent your own types, e.g. eth0 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Including local Image in pdf output
On 20.12.2017 14:27, Nothen, Christian wrote: > This is not working yet.. maybe the select "'file:/N:/test.png'" is wrong (I > tried many different formats here), so > any help on this Problem would be very much appreciated. What error message you have received? If you have to include drive letter into URL, you usually need to use more slashes to separate it from the protocol, e.g. file:///n:/test.png -- ------ 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] xincludes and graphics
On 23.11.2017 16:56, Shikareva, Ekaterina wrote: > Processing is done like described here: > http://www.sagehill.net/docbookxsl/Xinclude.html in "Using Xerces to resolve > XIncludes". The error is that image paths are always wrong whatever settings > I'm trying to use. Basically, doc1, doc2, doc3 are always missing in the > final path. > > Could you please give some hints, what I'm missing here? Do I need to define > xml:base manually somewhere? Can you make available sample files demonstrating your problem? -- ------ 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 -- signature.asc Description: OpenPGP digital signature
[docbook-apps] [ANN] Reminder: XML Prague 2018 - Call for Proposals
Hello,
there are still seven days to submit your proposal for XML Prague.
The XML Prague conference will include two full days of single track
sessions, as well as a multitrack unconference day.
The conference is held on the Thursday, Friday and Saturday (February
8-10, 2018),
located at the University of Economics, nam. W. Churchilla, Prague,
Czech Republic.
XML Prague is a conference on XML for developers, markup geeks,
information managers, and students. XML Prague focuses on markup and
semantic on the Web, publishing and digital books, XML technologies for
Big Data and recent advances in XML technologies. The conference
provides an overview of successful technologies, with a focus on real
world application versus theoretical exposition.
This years topics include the following:
* Markup and the Extensible Web
* Semantic visions and the reality
* Publishing for the 21th century
* XML technologies and Big Data
* State of the XML Union
* XML success stories
Conference website: http://www.xmlprague.cz
Call for proposals: http://www.xmlprague.cz/cfp/
Registration: http://www.xmlprague.cz/conference-registration/
Please take note of the following important ates:
November 30th – End of CFP
January 8th – Notification of acceptance/rejection
January 31st – Final paper (for those who will provide it)
February 8-10 – XML Prague 2015 conference
This year we would like to encourage new speakers -- full paper
submission is no longer needed and there will be shorter slots available
for those who would like to introduce/demo something "smaller".
If you have any questions, interested in sponsorship or just
want to make a suggestion please send email to: i...@xmlprague.cz
Jirka Kosek
on behalf of XML Prague
--
------
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
--
-
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] Current version of DocBook and relationship between OASIS / Doc
On 6.11.2017 15:39, Dave Pawson wrote: > One small (0bvious?) addition: >5.1 is being developed outside of Oasis, prior to submission to Oasis > as a candidate standard. No, all schema changes are discussed and decided by DocBook TC. But because OASIS doesn't provide good technical infrastructure new requirements and beta version of schemas are managed on GitHub. So it seems that only final committee specification or standard is published by OASIS. 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 -- signature.asc Description: OpenPGP digital signature
Re: [docbook] Current version of DocBook and relationship between OASIS / Doc
On 5.11.2017 20:48, Eitan Adler wrote: > What is the relationship between OASIS and DocBook? Both from an > organizational and specification perspective. Hi, I will try to explain, but others feel free to add more information. OASIS (https://www.oasis-open.org/) is organization that develops standards. DocBook schema is developed by DocBook Technical Committee (https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=docbook) following OASIS process (https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26). DocBook TC develops only schema for DocBook. There are other important assets like stylesheets or documentation -- these are developed independently from OASIS, usually by few volunteers on open-source basis. > What is prompting this question: > - http://docs.oasis-open.org/docbook/docbook/v5.1/os/docbook-v5.1-os.html > claims that 5.1 is a OASIS Standard That's true > - http://docbook.org/xml/5.1/ appears to be exist, but lacks > docbook-5.1.zip and does not say "There is a specification for this > release." > - http://docbook.org/xml/5.0/ has the zip file and specification sentence I agree that difference might be confusing but it's not intentional. Most likely change is caused by change in build system used and people involved in the process. If you miss ZIP distribution and link to specification please fill issue for this at: https://github.com/docbook/docbook.org/issues > - http://www.oasis-open.org/docbook/xml/ shows 5.0 but not 5.1 > - http://www.oasis-open.org/docbook/xml/5.0/index.xml says "This > version has not been released yet." > - http://www.oasis-open.org/docbook/xml/5.0/index.xml says has an > ancient rcsdate and references alpha1 even though > http://www.oasis-open.org/docbook/xml/ lists newer versions (betas and > releases) Umm, well. Outdated info on oasis-open.org is hard to explain to outsider. The short story is that process for updating these pages is not very convenient and thus these pages are outdated. I suggest using http://docbook.org/xml/ instead. docbook.org domain is under control of DocBook community. Folders at http://www.oasis-open.org/docbook/xml/ should be mirror of http://docbook.org/xml/ -- but this setup never worked for reasons explained above. Hope this helps little bit, 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 -- signature.asc Description: OpenPGP digital signature
[docbook-apps] [ANN] XML Prague 2018 - Call for Proposals
Hello,
we are glad to announce that call for proposals for XML Prague 2018
conference is open now.
The XML Prague conference will include two full days of single track
sessions, as well as a multitrack unconference day.
The conference is held on the Thursday, Friday and Saturday (February
8-10, 2018),
located at the University of Economics, nam. W. Churchilla, Prague,
Czech Republic.
XML Prague is a conference on XML for developers, markup geeks,
information managers, and students. XML Prague focuses on markup and
semantic on the Web, publishing and digital books, XML technologies for
Big Data and recent advances in XML technologies. The conference
provides an overview of successful technologies, with a focus on real
world application versus theoretical exposition.
This years topics include the following:
* Markup and the Extensible Web
* Semantic visions and the reality
* Publishing for the 21th century
* XML technologies and Big Data
* State of the XML Union
* XML success stories
Conference website: http://www.xmlprague.cz
Call for proposals: http://www.xmlprague.cz/cfp/
Registration: http://www.xmlprague.cz/conference-registration/
Please take note of the following important ates:
November 30th – End of CFP
January 8th – Notification of acceptance/rejection
January 31st – Final paper (for those who will provide it)
February 8-10 – XML Prague 2015 conference
This year we would like to encourage new speakers -- full paper
submission is no longer needed and there will be shorter slots available
for those who would like to introduce/demo something "smaller".
If you have any questions, interested in sponsorship or just
want to make a suggestion please send email to: i...@xmlprague.cz
Jirka Kosek
on behalf of XML Prague
--
------
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
--
signature.asc
Description: OpenPGP digital signature
Re: [docbook-apps] Enable FOP's PCL duplexing feature with DocBook XSL stylesheet customization?
On 7.9.2017 17:46, Warren Young wrote: > Unfortunately, grepping the DBX FO XSL files in the version of the > stylesheets packaged for my OS turns up no instances of “duplex”. That's because XSL-FO and DocBook stylesheets are dealing with formatting and pagination. How these pages are printed onto physical paper is out of scope of these technologies. Usually you will produce PDF not PCL and then instruct PDF viewer together with print driver to do things like duplex printing, or two pages on one sheet printing, etc. > 3. Maybe there is a trick with XSL customization files to insert arbitrary > directives? There is template setup-pagemaster which you can redefine, or you can just create additional pagemaster using user.pagemasters template. You can add pcl:duplex-mode attribute in your customization. > 4. Prevail on those maintaining the standard DocBook stylesheets to add a way > to turn this feature on in a standard way, so that in about a decade’s time > when all my machines with outdated docbook-style-xsl RPMs are replaced, I’ll > be able to turn it on with a one-line XSL directive. :) Patches are welcomed. But it's first time I hear that someone is using PCL backend in FOP. ;-) -- ------ 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 -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook] DocBook 5 & Schematron Rules: title vs. s:title (Bug?)
On 11.4.2017 13:24, Thomas Schraitle wrote: > I guess the element is incorrect, right? According to the > namespace definition it belongs the the RNG namespace. Of course, it should be s:title. This code is automatically generated. I have fixed this and created PR with fix: https://github.com/docbook/docbook/pull/89 > However, RNG doesn't know any title element. I assume it's a typo and > it should be , right?. According to the Schematron RNG > schema[2], s:pattern allows an s:title... Fortunatelly Schematron allows foreign elements so it will simply ignore title element in the wrong namespace. This is also why this hasn't been spotted for a while as no tools were reporting any problems with the schema. > I've checked that for 5.1 and 5.2b01. Both contains this problem. > For 5.0, there is still an invalid @name attribute which causes oXygen It's probably not good idea to replace existing copies of 5.1 and 5.0 schemas. Seems like releasing 5.1.1 and 5.0.1 would be more proper approach. Definitively something for DocBook-TC to discuss. Thanks for catching this. 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 -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
[docbook] [ANN] XML Prague 2017 - Call for Papers Reminder
Hello, this is gentle reminder that there is still 10 days for completing submission for XML Prague conference. The XML Prague conference will include two full days of single track sessions, as well as a multitrack pre-conference day. The conference is held on the Thursday, Friday and Saturday (February 9-11, 2017), located at the University of Economics, nam. W. Churchilla, Prague, Czech Republic. XML Prague is a conference on XML for developers, markup geeks, information managers, and students. XML Prague focuses on markup and semantic on the Web, publishing and digital books, XML technologies for Big Data and recent advances in XML technologies. The conference provides an overview of successful technologies, with a focus on real world application versus theoretical exposition. This years topics include the following: * Markup and the Extensible Web * Semantic visions and the reality * Publishing for the 21th century * XML technologies and Big Data * State of the XML Union Conference website: http://www.xmlprague.cz Call for papers: http://www.xmlprague.cz/call-for-papers/ Registration is already open and you can take advantage of early bird prices until January 8th: http://www.xmlprague.cz/conference-registration/ Also if you have idea for organizing users meeting unconference call is also open till December 15th: http://www.xmlprague.cz/pre-conference-call/ Please take note of the following Important Dates: December 15th -- end of CFP January 8th -- notification of acceptance/rejection January 29th -- final paper February 9-11 -- XML Prague 2017 conference If you have any questions, interested in sponsorship or just want to make a suggestion please send email to: i...@xmlprague.cz Jirka Kosek on behalf of XML Prague 2017 Committee -- -- 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 -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
[docbook] Announce: DocBook V5.2b01
Hi, if everything goes well DocBook V5.1 should be soon OASIS Standard. Meanwhile DocBook TC started looking into future and considering new request for enhancements. First beta release of DocBook V5.2b01 is available for testing at: http://docbook.org/xml/5.2b01/ If you will find any issues with this release please report them on this mailing list or raise new issue on GitHub (https://github.com/docbook/docbook/issues). Summary of changes made since V5.1: - Added danger element - Allow modifier within paramdef - Added otherclass to article - Allow block elements inside abstract - Allow void inside funcdef Enjoy! 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 -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Eclipse Help generation - anchor IDs
On 5.3.2015 8:19, Shikareva, Ekaterina wrote: I generate Eclipse HTML Help from my DocBook files with xsltproc, and every generation leads to attribute (ID) changes in anchor tags. Because of this we get a lot of warnings during code reviews. Our current solution is to mark such changes as unimportant in Beyond compare, but is there a way to minimize anchor ID changes during HTML files generation? Apart from what Bob suggested you can put xml:id attribute on all structural elements that produce anchors -- like chapters, sections, ... 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 -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Strategies for Migrating DocBook Customization in a Mixed DB4/5 Environment?
On 17.2.2015 10:27, Thomas Schraitle wrote: (Of course, I could feed my new DocBook 5 sources into my existing XSL customizations. This works, but it takes too much time because of the internal convertion of DocBook 5 to DocBook 4.) And what about converting V4 documents to V5 (for example with different filename) prior running DocBook XSL stylesheets? You automate this using make or ant, only changed files will be converted again and you will gain significant speed up. However, we have some some hefty DocBook XSL customizations; a DocBook XSL Transition Guide would be helpful. :) How would you deal with such migration of old DocBook 4 XSL customization layers? Adding namespace prefix in front of element names inside XPath expressions should be enough. 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 -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
[docbook-apps] Re: [docbook] Google Summer of Code 2015 -- Last call for participants
On 9.2.2015 22:32, Richard Hamilton wrote: So far, I've only received one message expressing interest in having the DocBook project apply to participate in the Google Summer of Code this year. I can server as a mentor again. 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 -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook] LaTeX math inside docbook, on-the-fly MathML conversion?
On 29.1.2015 20:46, Marco Giebel wrote: Can this be done? Or do I have to parse my documents, find all latexmath elements, process their contents with LatexML and write the MathML output back into the document? Sure, you can invoke some conversion library like SmuggleTeX directly from XSLT code to do on-the-fly conversion. -- -- 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 -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
[docbook-apps] Re: [docbook] Restrictive Docbook XML editor which enforces Docbook schema?
On 15.1.2015 16:12, Dan Shelton wrote: No, what I need is that users are completely prevented from creating tags which do not belong there. No red text or something like that. We need something which really prevents the creation in the first place. You forgot to mention whether you are looking for editor working with XML source or visual one. There are couple of visual editors running in browser that provide simplified and controlled editing environment. 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 -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Non translatable content in Docbook 4.x
On 13.1.2015 20:50, Jan Tosovsky wrote: I'd like to mark some text as non translatable. I could add a common attribute to all elements in original DTDs, but I like the idea of utilizing ITS standard for this purpose, which seems to be supported in CAT tools. I've found this explanatory article, but I'd like to use it in old 4.x DTD. http://xmlguru.cz/2013/05/docbook-and-its2 You should definitively use DocBook 5.x. There are already schemas for DocBook 5.0+ITS and in DocBook V5.1 schemas will support ITS out-of-the box. Is there any way? Some extension like for xi:includes ? You can customize DTD yourself, but it's painful compared to RELAX NG based customization of DocBook 5: http://docbook.org/tdg/en/html/ch05.html You can crate your own DTD, something like: !ENTITY % local.common.attrib its:translate (yes|no) #IMPLIED xmlns:its CDATA #FIXED 'http://www.w3.org/2005/11/its' !ENTITY % DocBookDTD PUBLIC -//OASIS//DTD DocBook V4.5//EN http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd; %DocBookDTD; Btw, there is no ROI to switch to Docbook 5. It's usually pretty straightforward to switch to V5. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://www.kosek.cz -- Profesionální školení a poradenství v oblasti technologií XML. Podrobný přehled školení http://xmlguru.cz/skoleni/ -- http://docbook.czStránky o dokumentačním formátu DocBook http://xmlguru.czBlog mostly about XML for English readers -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Multi-footnote reference
On 19.12.2014 15:12, Matteo Regazzo wrote: do you know if is it possible to link a single footnote to more than a line? Yes, use footnoteref/ element: http://www.docbook.org/tdg5/en/html/footnoteref.html -- -- 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 -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Image scaling in Eclipse help
On 17.12.2014 6:59, Shikareva, Ekaterina wrote: I've tried various combinations of stylesheet parameters regarding graphicshttp://docbook.sourceforge.net/release/xsl/current/doc/html/graphics.html, as well as applying CSS styles (width and max-width parameters) to img, .mediaobject, .informalfigure, and .figure. Can't find the correct combination or find the solution online. This is currently not supported in stylesheets in a fully automated way. If you know, which images are big and should be scaled down, you can specify width=100% on them. Don't use any other attributes. The problem is that users can open documentation in windows of different sizes and thus it's impossible to know in advance which images should be scaled down and which not. In recent browsers you can solve this very elegantly by specifying max-width: 100% for all images. 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 -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Image scaling in Eclipse help
On 17.12.2014 13:15, Jirka Kosek wrote: scaled down and which not. In recent browsers you can solve this very elegantly by specifying max-width: 100% for all images. I forgot to mention that max-witdh is CSS property so you need to put this into custom CSS style for your generated HTML/Eclipse output. 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 -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Why is italic text not displayed in html files generated from Docbook/Oxygen ?
On 12.12.2014 11:02, Radu Coravu wrote: Indeed it seems that the default Docbook stylesheets indeed do not output i tags for emphasys with italic role. And a possible solution would either mean CSS customizations or XSLT customizations to add the i tag. Just to clarify -- role=bold has special support as it was always almost standard way to generate bold text. However as italic was default rendering of emphasis element there was never support for role=italic in stylesheets. If you will use emphasis without attributes you will get em element in HTML output. Unless $emphasis.propagates.style is set which doesn't output em and rather expects that user will map roles to visual presentation in CSS as roles will be turned into appropriate class values. 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 -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] epub3 and named entities
On 22.10.2014 18:48, Richard Hamilton wrote: It looks as though the next version of epubcheck may reject epub3 files that use named character entities (amp;, etc.). Any source for this information? It's hard to believe that amp; will be refused as it can't be written directly (same with lt; and to some extent with gt;, quot; and apos;). Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Tests Framework for DocBook Stylesheets Customizations?
On 16.10.2014 10:56, Thomas Schraitle wrote: I'm not sure how easily could this be adapted to our current XSLT 1 base. Are there other (better?) solutions? If you will not use extensions, it should be possible to run DocBook XSLT stylesheets in XSLT 2.0 processor, hence use XSpec. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook] To Namespace or Not To Namespace
On 3.10.2014 18:21, Steve Cuzner wrote: I'm investigating porting our 4.x docbook to 5.x. For our custom elements, I'm considering adding them to our own namespace so that it is more obvious which elements are docbook and which are custom to our extension. While technically not necessary given that any customizations makes it not DocBook, what are the pros and cons of namespacing our own extension elements? Putting custom elements into a separate namespace will make authoring much more less convenient. I usually prefer easier authoring over possible future class of newly introduced standard DocBook element. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Bad DOCTYPE on toc.ncx in epub2 stylesheets snapshot
On 2.10.2014 2:22, Richard Hamilton wrote: !DOCTYPE ncx PUBLIC -//W3C//DTD XHTML 1.1//EN http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd; There is a valid xmlns attribute on the root element, and if you remove the DOCTYPE lines completely, the file is fine. In 1.78.1 this does not happen. I poked around the stylesheets, but couldn't figure out what's going on, and I didn't see anything in the revision history that seemed pertinent. Has anyone run into the same thing? I never used EPUB2 stylesheets, but trouble spot is: xsl:template name=ncx xsl:call-template name=write.chunk ... xsl:with-param name=doctype-public select=''/ !-- intentionally blank -- xsl:with-param name=doctype-system select=''/ !-- intentionally blank -- Specifying empty doctype usually doesn't override doctype specified on xsl:output. You might try disabling doctype everywhere, it shouldn't matter even for XHTML content inside EPUB package. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook] audio epubs
[Replying to docbook-apps where this belongs...]
On 18.9.2014 15:38, Peter Fleck wrote:
Is it possible to do a lot of the work to make audio epubs using
stylesheets?
Everything is possible, it depends on effort you can put into it :-)
First, how to auto generate ids for each para? I'm sure that is
straightforward. (Or if more granularity is needed then id's at the
sentence or word level as needed).
Putting following into your customization layer should do the trick:
xsl:param name=generate.id.attributes select=1/
xsl:param name=generate.consistent.ids select=1/
xsl:template name=id.attribute
xsl:param name=node select=./
xsl:param name=conditional select=0/
xsl:choose
xsl:when test=$generate.id.attributes = 0
!-- No id attributes when this param is zero --
/xsl:when
xsl:when test=$conditional = 0 or $node/@id or $node/@xml:id
xsl:attribute name=id
xsl:call-template name=object.id
xsl:with-param name=object select=$node/
/xsl:call-template
/xsl:attribute
/xsl:when
/xsl:choose
/xsl:template
However if you change your DocBook source autogenerated IDs will change.
Second, populate the smil file with the ids
smil xmlns=http://www.w3.org/ns/SMIL;
xmlns:epub=http://www.idpf.org/2007/ops; version=3.0
body
seq id=id1 epub:textref=index.xhtml epub:type=bodymatter
chapter
par id=paragraph1
text src=index.xhtml#para-id1/
audio src=audio/file.mp3 clipBegin=0:00:02.000
clipEnd=0:00:15.000/
/par
par id=paragraph2
text src=index.xhtml#para-id2/
audio src=audio/file.mp3 clipBegin=0:00:15.000
clipEnd=0:00:25.000/
/par
/seq
/body
/smil
The smil file would need manually editing for the clipBegin and clipEnd
for each but that's fine. The audio src could be passed as a parameter.
Then add something like .-epub-media-overlay-active {background-color:
#abc;} to the css.
Have you considered generating this SMIL file automatically? I can
imagine putting custom attributes into DocBook document, something like:
chapter my:audio=file.mp3
titleFoo/title
para my:begin=0:00:02.000 my:end=0:00:15.000.../para
para my:begin=0:00:15.000 my:end=0:00:25.000.../para
...
From such markup you can quite easily generate SMIL file automatically.
Finally modify the package.opf to add
meta property=media:duration
refines=#chapter1_overlay0:04:30.000/meta
meta property=media:duration
refines=#chapter2_overlay0:03:30.000/meta
meta property=media:duration0:08:00.000/meta
meta property=media:narratorNarrator Name/meta
meta property=media:active-class-epub-media-overlay-active/meta
/metadata
manifest
item id=ncx href=toc.ncx media-type=application/x-dtbncx+xml/
item id=htmltoc properties=nav
media-type=application/xhtml+xml href=ar01-toc.xhtml/
item media-type=text/css id=docbook-css href=docbook-epub.css/
item id=id-idm21776 href=index.xhtml
media-type=application/xhtml+xml media-overlay=chapter1_overlay/
item id=chapter1_overlay href=chapter1_overlay.smil
media-type=application/smil+xml/
Is something like this doable?
Yes, generation of OPF file is split into set of relative small
templates which you can easily override. Look into
epub3/epu3-element-mods.xsl file. For example metadata part is generated
by the following template:
xsl:template name=package.metadata
xsl:element name=metadata namespace={$opf.namespace}
xsl:call-template name=metadata.identifier/
xsl:call-template name=metadata.title/
xsl:call-template name=metadata.language/
xsl:call-template name=metadata.modified/
xsl:call-template name=metadata.cover/
xsl:call-template name=metadata.other.info/
/xsl:element
/xsl:template
You can generate this template manually, or put your custom elements
inside info elements and handle them in special opf.metadata mode.
info
...
media:narratorNarrator Name/media:narrator
/info
xsl:template match=media:* mode=opf.metadata
meta property=media:{local-name(.)}xsl:value-of select=.//meta
/xsl:template
HTH,
Jirka
--
--
Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz
--
Professional XML consulting and training services
DocBook customization, custom XSLT/XSL-FO document processing
--
OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
--
Bringing you XML Prague conferencehttp://xmlprague.cz
--
signature.asc
Description: OpenPGP digital signature
[docbook-apps] Re: [docbook] audio epubs
[Replying to docbook-apps where this belongs...]
On 18.9.2014 15:38, Peter Fleck wrote:
Is it possible to do a lot of the work to make audio epubs using
stylesheets?
Everything is possible, it depends on effort you can put into it :-)
First, how to auto generate ids for each para? I'm sure that is
straightforward. (Or if more granularity is needed then id's at the
sentence or word level as needed).
Putting following into your customization layer should do the trick:
xsl:param name=generate.id.attributes select=1/
xsl:param name=generate.consistent.ids select=1/
xsl:template name=id.attribute
xsl:param name=node select=./
xsl:param name=conditional select=0/
xsl:choose
xsl:when test=$generate.id.attributes = 0
!-- No id attributes when this param is zero --
/xsl:when
xsl:when test=$conditional = 0 or $node/@id or $node/@xml:id
xsl:attribute name=id
xsl:call-template name=object.id
xsl:with-param name=object select=$node/
/xsl:call-template
/xsl:attribute
/xsl:when
/xsl:choose
/xsl:template
However if you change your DocBook source autogenerated IDs will change.
Second, populate the smil file with the ids
smil xmlns=http://www.w3.org/ns/SMIL;
xmlns:epub=http://www.idpf.org/2007/ops; version=3.0
body
seq id=id1 epub:textref=index.xhtml epub:type=bodymatter
chapter
par id=paragraph1
text src=index.xhtml#para-id1/
audio src=audio/file.mp3 clipBegin=0:00:02.000
clipEnd=0:00:15.000/
/par
par id=paragraph2
text src=index.xhtml#para-id2/
audio src=audio/file.mp3 clipBegin=0:00:15.000
clipEnd=0:00:25.000/
/par
/seq
/body
/smil
The smil file would need manually editing for the clipBegin and clipEnd
for each but that's fine. The audio src could be passed as a parameter.
Then add something like .-epub-media-overlay-active {background-color:
#abc;} to the css.
Have you considered generating this SMIL file automatically? I can
imagine putting custom attributes into DocBook document, something like:
chapter my:audio=file.mp3
titleFoo/title
para my:begin=0:00:02.000 my:end=0:00:15.000.../para
para my:begin=0:00:15.000 my:end=0:00:25.000.../para
...
From such markup you can quite easily generate SMIL file automatically.
Finally modify the package.opf to add
meta property=media:duration
refines=#chapter1_overlay0:04:30.000/meta
meta property=media:duration
refines=#chapter2_overlay0:03:30.000/meta
meta property=media:duration0:08:00.000/meta
meta property=media:narratorNarrator Name/meta
meta property=media:active-class-epub-media-overlay-active/meta
/metadata
manifest
item id=ncx href=toc.ncx media-type=application/x-dtbncx+xml/
item id=htmltoc properties=nav
media-type=application/xhtml+xml href=ar01-toc.xhtml/
item media-type=text/css id=docbook-css href=docbook-epub.css/
item id=id-idm21776 href=index.xhtml
media-type=application/xhtml+xml media-overlay=chapter1_overlay/
item id=chapter1_overlay href=chapter1_overlay.smil
media-type=application/smil+xml/
Is something like this doable?
Yes, generation of OPF file is split into set of relative small
templates which you can easily override. Look into
epub3/epu3-element-mods.xsl file. For example metadata part is generated
by the following template:
xsl:template name=package.metadata
xsl:element name=metadata namespace={$opf.namespace}
xsl:call-template name=metadata.identifier/
xsl:call-template name=metadata.title/
xsl:call-template name=metadata.language/
xsl:call-template name=metadata.modified/
xsl:call-template name=metadata.cover/
xsl:call-template name=metadata.other.info/
/xsl:element
/xsl:template
You can generate this template manually, or put your custom elements
inside info elements and handle them in special opf.metadata mode.
info
...
media:narratorNarrator Name/media:narrator
/info
xsl:template match=media:* mode=opf.metadata
meta property=media:{local-name(.)}xsl:value-of select=.//meta
/xsl:template
HTH,
Jirka
--
--
Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz
--
Professional XML consulting and training services
DocBook customization, custom XSLT/XSL-FO document processing
--
OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
--
Bringing you XML Prague conferencehttp://xmlprague.cz
--
signature.asc
Description: OpenPGP digital signature
Re: [docbook-apps] DocBook XSL 1.78.1 copyright status
On 22.9.2014 16:59, Andy Hatton wrote: The distribution includes the COPYING file, which includes various copyright statements. These copyright statements are not much useful, what's important is very liberal licence statement below them. The copyrights run up to 2012, but 1.78.1 was released in 2013 (I think). The same statements are included in the current snapshot distribution. Is this just an oversight, or has the copyright situation changed after 2012? Nothing changes, simply no one dared to update dates. Next release will fix this and will state: Copyright (C) 2005-2014 The DocBook Project (with very high chance that in 2015 we forgot to update again :-) Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] support for xpointer
On 14.9.2014 3:22, Stefan Seefeld wrote: Can anyone confirm the state of xpointer support in xsltproc, or any other Free XSLT processor for that matter ? (For example, what about saxon ?) Are there any (free) test suites that I could use to get a sense of what is supported and what not ? AFAIK only thing which is reliable and works across different implementations is referencing node by its ID. Very sad. There is XInclude test suite, which has some XPointer tests as well: http://dev.w3.org/cvsweb/2001/XInclude-Test-Suite/ Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook] Alternate text for table and image accessibility - textobject, alt, summary?
On 12.9.2014 18:37, Bob Stayton wrote: This situation clearly needs some improvement. Before proceeding, I'd like to hear what others have to say regarding alt and accessibility for various elements, so that best practices can be followed if possible. For example, what should be done with any alt children of a para? I think that except for images and tables which require special HTML output the right solution is to concat all direct alt children into one string and put it inside title attribute. This can be easily implemented by extending common.html.attributes named template. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook] Alternate text for table and image accessibility - textobject, alt, summary?
On 11.9.2014 14:36, Janice Manwiller wrote: The current source files have textobject for images and nothing for tables. Is the alt element better than textobject? alt element can contain only inline elements. So if you need to use longer text descriptions, ie. several paragraphs, then you must use textobject. For tables, should I use alt or summary? This depends on table model used. In DocBook you can use HTML markup or so called CALS markup for tables. In HTML table you must use summary attribute, in CALS you can use alt/textobject. Probably sounds more complex then it should be, but there is long evolution behind this :-) Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Fwd: Thanks!
On 9.9.2014 14:20, Varga, Károly wrote:
There's a side issue with the webhelp-fast.xls: the sidebar ToC does not
expand to the currently viewed chapter if you use the navigation bar or
direct URLs to move between sections. It just shows a static, fully
collapsed ToC.
Hi folks,
could you try to run your webhelp generation on large document with
attached file copied over its original. I implemented caching of ToC on
XSLT level, so there are no changes on JS side needed.
Jirka
--
--
Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz
--
Professional XML consulting and training services
DocBook customization, custom XSLT/XSL-FO document processing
--
OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
--
Bringing you XML Prague conferencehttp://xmlprague.cz
--
xsl:stylesheet
xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
xmlns:exsl=http://exslt.org/common;
xmlns:ng=http://docbook.org/docbook-ng;
xmlns:db=http://docbook.org/ns/docbook;
version=1.0 xmlns=http://www.w3.org/1999/xhtml;
xmlns:html=http://www.w3.org/1999/xhtml;
exclude-result-prefixes=exsl ng db html
!--
$Id$
This file is part customization layer on top of the XSL DocBook
Stylesheet distribution that generates webhelp output.
--
xsl:param name=chunker.output.method
xsl:choose
xsl:when test=contains(system-property('xsl:vendor'), 'SAXON 6')saxon:xhtml/xsl:when
xsl:otherwisehtml/xsl:otherwise
/xsl:choose
/xsl:param
xsl:param name=doc.title
xsl:call-template name=get.doc.title/
/xsl:param
!-- Set some reasonable defaults for webhelp output --
xsl:param name=webhelp.common.dircommon//xsl:param
xsl:param name=chunker.output.indentyes/xsl:param
xsl:param name=navig.showtitles0/xsl:param
xsl:param name=manifest.in.base.dir select=0/
xsl:param name=base.dir select=concat($webhelp.base.dir,'/')/
xsl:param name=suppress.navigation0/xsl:param
!-- Generate the end-of-the-book index --
xsl:param name=generate.index select=1/
xsl:param name=inherit.keywords select='0'/
xsl:param name=para.propagates.style select=1/
xsl:param name=phrase.propagates.style select=1/
xsl:param name=chunk.first.sections select=1/
xsl:param name=chunk.section.depth select=3/
xsl:param name=use.id.as.filename select=1/
xsl:param name=brandingnot set/xsl:param
xsl:param name=brandname /xsl:param
xsl:param name=section.autolabel select=0/
xsl:param name=chapter.autolabel select=0/
xsl:param name=appendix.autolabel select=0/
xsl:param name=qandadiv.autolabel select=0/
xsl:param name=reference.autolabel select=0/
xsl:param name=part.autolabel select=0/
xsl:param name=section.label.includes.component.label select=1/
xsl:param name=generate.section.toc.level select=5/
xsl:param name=component.label.includes.part.label select=1/
xsl:param name=suppress.footer.navigation0/xsl:param
xsl:param name=callout.graphics.pathxsl:value-of select=$webhelp.common.dir/images/callouts//xsl:param
xsl:param name=callouts.extension1/xsl:param
xsl:param name=admon.graphics.pathxsl:value-of select=$webhelp.common.dir/images/admon//xsl:param
xsl:param name=admon.graphics select=0/
!--xsl:param name=generate.tocbook toc/xsl:param--
xsl:param name=generate.toc
appendix toc,title
article/appendix nop
article toc,title
book 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
/xsl:param
!-- Localizations of webhelp specific words. Your contributions for other languages are appreciated.
Currently, only around 10 translations needed. --
!-- Moved to files under 'gentext/locale/', search for WebHelp --
xsl:template name=user.head.title
xsl:param name=node select=./
xsl:param name=title
xsl:apply-templates select=$node mode=object.title.markup.textonly/
/xsl:param
xsl:param name=document-title
xsl:apply-templates select=/* mode=object.title.markup.textonly/
/xsl:param
title
xsl:copy-of select=$title/ - xsl:if test=parent::* - xsl:copy-of select=$document-title//xsl:if
[docbook] Updated transclusion proposal
On 20.8.2014 10:13, Jirka Kosek wrote: d. Jirka to update DocBook Transclusions document to reflect the new XInclude 1.1 features. Continued, will be ready for September meeting. Hi folks, please find first very rough attempt to update transclusions as a layer on top of XInclude 1.1. Some features are missing compared to previous draft, but once XInclude 1.1 is implemented solution will be more standards-based. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- Title: DocBook Transclusion DocBook TransclusionNaNSeptember2014This version:http://docbook.org/docs/transclusion/2014-09-XX/ (HTML, XML, PDF)Latest version:http://docbook.org/docs/transclusion/ (HTML, XML, PDF)Previous versions:http://docbook.org/docs/transclusion/2011-04-20/ (HTML, XML, PDF)http://docbook.org/docs/transclusion/2010-12-09/ (HTML, XML, PDF)Author:Jirka Kosek, ji...@kosek.czTable of ContentsTransclusion processingSpecial ID/IDREF processingA. Sample transclusion processor written in XSLT 2.0Bibliography This document describes syntax, semantics and processing model of DocBook transclusion mechanism. Please be aware that this is early stage draft everything described below might change or disappear completely. This proposal tries to resolve Requirements for transclusion in DocBook. DocBook TC welcomes any feedback on this draft, especially from users and developers of DocBook authoring and processing tools. Plese direct your comments to DocBook mailing list by sending email to docbook@lists.oasis-open.org. Actually, for now the document is written more like tutorial. If DocBook TC decides to incorporate this into DocBook, more formal and precise specification will follow. Note Previous version of this draft proposed new elements ref and def for implementing transclusions. Meanwhile DocBook TC decided that transclusions should rely as much as possible on standard technologies. XInclude 1.1 added new features that allow to implement some transclusion features on top of the XInclude. As a result transclusions were completely redesigned to be layered on top of XInclude 1.1. This resulted in a loss of some features, notably: It's no longer possible to locally redefine text replacement (see example).anything else? The following namespace bindings are assumed if namespace prefix is used in the text of this document: dbDocBook namespace (http://docbook.org/ns/docbook) xiXInclude namespace (http://www.w3.org/2001/XInclude) Transclusion processing XInclude 1.1 [XI11] in section 4.3 Attribute Copying when processing XML defines new feature which can be used for passing around attributes that control transclusion processing. Processing model of XInclude 1.1 based transclusion is simple. First XInclude processing is done. Then before normal DocBook processing additional DocBook transclusion step is applied which can modify some attributes. DocBook transclusion processor must support the following attributes: db:id Specifies ID for transcluded content. If there is xml:id attribute present it's value must be replaced by the value of db:id attribute. If db:id is present, but empty, then xml:id must be removed from the element. Should we define what to do with db:id after transclusion? Like remove/keep/don't care. db:idfixup This attribute controls how IDs are going to be adjusted during transclusion. noneNo ID adjustment is done. This is default behavior if attribute is not specified. This must be default in order to keep compatibility with XInclude.stripAll IDs on element descendants are stripped.prefixAll IDs on element descendants are prefixed with a value specified in db:prefix attribute.autoAll IDs on element descendants are prefixed with a value which is unique for each element[1] db:prefix Prefix to use when db:idfixup="prefix". db:linkscope This attribute defines how refences has to be corrected. userNo IDREF adjustment is donelocalAll IDREFs in element are prefixed by user specified prefix (when db:idfixup="prefix") or auto-generated prefix (when db:idfixup="auto"). Using this value with other db:idfixup values is an error.Maybe raising error is too strict approach.nearAll IDREFs in element are adjusted to point to the closest element which has a matching ID. A matching ID doesn't mean string equality between ID and IDREF values it is s
Re: [docbook-apps] Fwd: Thanks!
On 5.9.2014 10:58, Wegmann, Frank wrote: Personally, I’d favor to deploy the DocBook stylesheets, since I know my ways around them, but leveraging the stylesheets from the module to a set level without using the set mechanism looks to me to be way beyond trivial. Or has this been done already? Could anybody please point me to a good solution in this situation? I'm not sure I understand what you want to do with Webhelp. You want to generate one Webhelp (ie. shared ToC, Index, Search) from several DocBook documents? Or do you want to be able to make just links working between several separate Webhelps? Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Fwd: Thanks!
On 5.9.2014 11:18, Wegmann, Frank wrote: Yes, we want to generate one WebHelp from several DocBook books. And have you tried to process books as a one set solely for purpose of Webhelp geneation? -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
[docbook] Re: [docbook-tc] DocBook Technical Committee Meeting Agenda: 20 August 2014
On 18.8.2014 22:04, Bob Stayton wrote: The DocBook Technical Committee will meet on Wednesday, 20 August 2014 at 1:00pm ET for 90 minutes. My regrets. d. Jirka to update DocBook Transclusions document to reflect the new XInclude 1.1 features. Continued, will be ready for September meeting. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Release of DocBook 5.1 + XSL?
On 13.8.2014 15:04, gra...@heliocentrik.net wrote: I know this is a cheeky request. Anyway, my organisation is using the DocBook 5.1 betas in production, and we are keen to know if there is any information regarding when the final release of the spec, and in particular the XSL distribution which fully supports it, are likely to be available. Is there a known release timeframe? If there are no issues found in 5.1RC3 then plan is to make it OASIS Committee Specification and then OASIS Standard soon. There are some review periods required by OASIS process, but if everything goes well 5.1 could be Committee Specification during autumn. OASIS Standard is just rubber-stamping process, so no changes will be made into specification and this procedural delay shouldn't have impact on delaying implementations. XSL stylesheets are separate story. If you find some bug or missing feature in assembly support please fill it into tracker so implementation can be fixed. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Redundant end tags been removed
On 24.7.2014 1:32, Peter Desjardins wrote: This reminds me of a problem I saw in webhelp. I think it was solved by inserting a comment in the script tag. Then the end tag is preserved. If you use Saxon, more elagant solution is to specify saxon:xhtml as an output method, either in xsl:output or in $chunker.output.method. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] epub3 mathml rendering
On 30.6.2014 20:35, Tim Arnold wrote: However, the MathML is not rendered in either Readium or Calibre. When I manually remove the namespace from the math blocks, Calibre can then render the math (Readium still fails). And you haven't yet tested this in hardware readers :-( While EPUB3 supports MathML most reading devices doesn't yet support EPUB3. So for now you have to convert equations to images for classic reading devices. For more recent readers you might have success with using MathJax Javascript library for MathML rendering. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Status attribute
On 24.6.2014 11:04, Matteo Regazzo wrote:
Is it possible to have a status condition, in each element of the book,
where the condition value depends on the status attribute of the book
root element?
Yes, it's a bit of pitty that status is not allowed everywhere. I
usually extend DocBook schema to allow status attribute everywhere:
include docbook.rnc
{
# @status is allowed on all elements
db.effectivity.attributes = attribute status { draft | final }?
# Status is part of effectivity attributes now
db.status.attribute = empty
}
--
--
Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz
--
Professional XML consulting and training services
DocBook customization, custom XSLT/XSL-FO document processing
--
OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
--
Bringing you XML Prague conferencehttp://xmlprague.cz
--
signature.asc
Description: OpenPGP digital signature
Re: [docbook-apps] db5, fo output, page breaks
On 23.6.2014 15:40, davep wrote: Yes... but it wouldn't help with tiny chapters? I'm thinking I have to go to article layout, not a big job for this piece. Yes, each chapter starts a new fo:page-sequence, so you have to convert book-article and chapter-section before processing to get desired output. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] id fixup with prefix
On 17.6.2014 17:07, David Cramer wrote: xi:include href=foo.xml db:idprefix=second-/ Likewise, it should be an error to set db:idfixup to none, strip, or auto and also to set a db:idprefix. Does that make sense? That sounds reasonable. I should update spec and sample code to use XInclude 1.1. I was waiting for XInclude 1.1 implementations before doing this. I will not be able to attend tomorrow telcon, but please feel free to assign my action item to prepare new transclusion spec based on XInclude 1.1. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook] Image @ 100% width for HTML output
On 3.6.2014 9:04, Jean-Francois Weissmann wrote: I’m actually trying to modify an HTML conversion stylesheet to automatically display all imagedata contained into a mediaobject at 100% of the available width in the HTML page or the table cell… I tried to play somehow with these lines in the XSL file but I’m struggling with the syntaxe to provide a correct output… Have you tried setting the following parameter: http://docbook.sourceforge.net/release/xsl/current/doc/html/default.image.width.html -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Problem with images given as entity in xhtml output (template process.image)
On 22.5.2014 16:05, Frank Steimke wrote: I have an article with an image. The image is defined as an unparsed entity, its value is an relative filename. Something like !ENTITY img SYSTEM image.png NDATA PNG Used as imagedata entityref=img/ In my article. Is there any reason why you are not using fileref attribute with relative path to image? That's more manageable setup. -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Problem with images given as entity in xhtml output (template process.image)
On 22.5.2014 16:42, Fletcher, Brett wrote: I am (I think) trying to accomplish the same thing as Frank. I have multiple docs which use the same copy, but require different figures. I was hoping to define those figures in entity files so they would be easier to maintain. The references do not appear to be making it into the docs. This all sounds like what I am trying to do, but not being very familiar, I was hoping someone might offer a high-level explanation of how this is all working? Then perhaps I can understand the presented solutions. First advice -- try to eliminate usage of entities in your documents. In XML entities will give you more troubles then advantages (situation was different in SGML where entities were more flexible). In your case, you can put each set of images into different directory, but using same filenames. Then use following parameter to switch directory from which images will be loaded: http://docbook.sourceforge.net/release/xsl/current/doc/html/img.src.path.html Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Restricting values in RNG for db.audience.attribute
On 15.5.2014 9:06, Bergfrid Skaara wrote: At this point I get validation errors like group of string or data element. How do I tweak the docbookxi.rng (in my customization layer rng file) to allow this construction with semicolons, which is clearly allowed by the shema without enforcing enumeration values? List types in RELAX NG are only space separated. You can either use space instead of semicolons to separate profiling values (there is parameter profile.separator in stylesheet to support such change). If you want to stick with semicolon, you can use regular expression in schema to validate your profiling values: define name=my.audience data type=string param name=pattern(gui|admin|...)*/param /data /define Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Problem with images given as entity in xhtml output (template process.image)
On 22.5.2014 17:12, Fletcher, Brett wrote: First, Thank you for replying! I will gladly take your advice of eliminating Entities. Please, next time reply to all, so answer is sent back to the whole mailing list. As far as the solution you provided, could you provide an example of how it would look in an xml doc? Also, I am guessing I need to modify an .xsl file? I have never done that before and am not sure how to do that. I inherited my setup and am having to learn XML on the fly while trying not to fall to far behind in the actual work! Do you have any suggested reading? You should definitively read the following book if you mean it seriously with using DocBook XSL stylesheets: http://sagehill.net/docbookxsl/index.html Back to your question. In your document you will use just filenames without any path: imagedata fileref=picture.png/ Then in subdirectories like version1 and version2 you will store two different versions of this image, both times in a file called picture.png Then during the processing you will set img.src.path parameter either to version1/ or version2/ value. You can set parameter from command line when invoking XSLT processor or you can store it into your own XSL customization layer. More details are in the book mentioned above. Jirka Thanks again! Brett -Original Message- From: Jirka Kosek [mailto:ji...@kosek.cz] Sent: Thursday, May 22, 2014 10:01 AM To: Fletcher, Brett Cc: Frank Steimke; docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] Problem with images given as entity in xhtml output (template process.image) On 22.5.2014 16:42, Fletcher, Brett wrote: I am (I think) trying to accomplish the same thing as Frank. I have multiple docs which use the same copy, but require different figures. I was hoping to define those figures in entity files so they would be easier to maintain. The references do not appear to be making it into the docs. This all sounds like what I am trying to do, but not being very familiar, I was hoping someone might offer a high-level explanation of how this is all working? Then perhaps I can understand the presented solutions. First advice -- try to eliminate usage of entities in your documents. In XML entities will give you more troubles then advantages (situation was different in SGML where entities were more flexible). In your case, you can put each set of images into different directory, but using same filenames. Then use following parameter to switch directory from which images will be loaded: http://docbook.sourceforge.net/release/xsl/current/doc/html/img.src.path.html Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: AW: [docbook-apps] Problem with images given as entity in xhtml output (template process.image)
On 22.5.2014 17:22, Frank Steimke wrote: OK, but as far as I understand, the same problem would come up if I would use a @fileref with an absolute filename like file:/C:/temp/image.png. You shouldn't use absolute filenames because that way your documents are not portable. Question is, whether this is a correct URL for an absolute filename. It depends on your definition of correctness. At least for Windows paths there are several common ways how to construct URL, e.g. file:///c/..., file:/c:/..., file:///c|/... If it is not, then there is a problem with the unparsed-entity-uri() function, since it should never return an invalid URL. This would result in a bug report for saxon 6.5 on windows 7. If it is, then there is a problem with the process.image template, since it should be able to process URLs with absolute filenames. Absolute file URLs are mess, very different on each operating system. But if there is a bug, please feel free to submit bugreport. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] EPUB: dbtimestamp PI in pubdate or date
On 18.5.2014 20:10, Thomas Schraitle wrote: Yes, I thought about profiling too, but didn't add it to the list. In my opinion, it's a bit too much: Using profiling just to avoid a conceptual issue in the stylesheet(s) is not the cure, but adds additional burden. :) You will just import different base stylesheet. This issue is exactly the same than selecting the right image format in the mediaobject/imageobject elements by using a role attribute. No profiling is involved and the stylesheets just select the respective image format correctly. You wouldn't recommend to use profiling for just selecting the right image, would you? ;) If you use different images for HTML and EPUB I probably would. There are dozen of similar cases and there is no direct support for them as well. What cases do you have in mind? If there are more use cases, maybe this is an indication that we really need a best practise. In EPUB you have different ISBN then in printed version of your book, some other parts of content has to be adjusted -- for example colophon. I think that for EPUB we can just document the following best practice: date condition=noepub?dbtimestamp?/date date condition=epub?dbtimestamp format=Y-m-d?/date Well, maybe, maybe not. Whatever we prefer, I think we have to distinguish two cases in EPUB: 1. The date, probably somehow/somewhere definied by the user, which appears on a titlepage. 2. The date inside any meta information, usually hidden for the user. This is required by the EPUB specification. For (1) the user can choose whatever he likes. There is no restriction. However, for (2) the EPUB demands a YEAR-MONTH-DAY format. Either the user defines it manually or he lets the stylesheet(s) do the correct output. Well, then easiest solution is to provide template for populating EPUB field. By default it can put current date into an EPUB file and user can override it to use different date or populate date dynamically from source and format it into xs:date format. What about the following solution? date ?dbtimestamp format=Y, m? ?dbtimestamp format=Y-m-d output=epub? ?dbtimestamp format=m (Y) output=fo? /date That's messy and hard to process as PI's pseudo-attributes are not easily accessible in XPath. No, I don't use profiling when I create my EPUBs. ;) Nor for other formats. Building EPUBs and other formats doesn't involve necessarily a profiling step. By no means it should be required. Then your life and requirements are easy :-) We should keep it simple and do the magic in our stylesheets, without any profiling involved or required for this issue. Profiling is also magic hidden in the stylesheets. -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] EPUB: dbtimestamp PI in pubdate or date
On 18.5.2014 14:42, Thomas Schraitle wrote: 3. Detect an additional pubdate or date with role=epub This could solve the issue as both formats can live happily together. We used this approach also for imagedata which belongs to certain output formats. However, we need to define what to do when no 2nd pubdate or date is available. You can achieve this today with profiling, I'm not sure whether there is any need to standardize this behaviour. There are dozen of similar cases and there is no direct support for them as well. I think that for EPUB we can just document the following best practice: date condition=noepub?dbtimestamp?/date date condition=epub?dbtimestamp format=Y-m-d?/date Anyway, if you are producing EPUB and other targets it is very likely that you are already using profiling. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] informalfigures and @label
On 17.5.2014 8:37, Brad Scott wrote: but that doesn't autogenerate Figure 1 with the image. Does informalfigure need some special handling in the XSL to support this? You can use figure and provide empty title -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Profiling with Webhelp
On 10.4.2014 9:54, Fritsch, Michael wrote: So, can anyone tell me please which style sheets I have to import and how the import statement has to look?? It might be possible copy content of webhelp.xsl into your stylesheets and change imports here to use profiling. But it might be necessary to adopt additional templates. I think the easiest is to use two pass profiling -- ie. do first separate profiling step and then use normal webhelp. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] Re: webhelp local anchors in table of contents not working
On 25.3.2014 8:14, Kasun Gajasinghe wrote: The above code is kind of a hack to workaround an issue. The reason is explained in the source itself that you have pointed. We need to think what would be the proper approach to fix rather than having a workaround. The current alternative we have has some drawbacks. I guess I provided you the link to it previously. I think that main problem is that JS code in main.js is not working with DOM generated by stylesheets. I have commited change September 2013 for this issue. I would suggest to OP trying the latest version of main.js from SVN repo. http://sourceforge.net/p/docbook/code/9798/tree//trunk/xsl/webhelp/template/common/main.js?diff=9592 Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] NPE when building RTF from .fo
On 25.2.2014 22:23, Mark Craig wrote: With DocBook XSL 1.78.1 and Apache FOP 1.1, I'm running into an NPE when building RTF. Has anyone else run into this? AFAIK RTF backend in FOP was never complete and it is no longer developed. If you need to produce output suitable for further editing in office applications, you can try the following FO engine: http://www.xmlmind.com/foconverter/ -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
Re: [docbook] Customization of attribute set
On 30.1.2014 21:47, julia.jacob...@arcor.de wrote: Toolchain: xsltproc -o output.html my_style.xls my_doc.xml I would expect the title of the section to be centered, but this is not the case. Could you please point me towards additional diagnostics to run in order to pin down the problem? You are generating HTML, but changing attribute set that affects FO (print) output. If you need to customize HTML output, then easiest is to use CSS, see: http://www.sagehill.net/docbookxsl/UsingCSS.html -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep. -- Bringing you XML Prague conferencehttp://xmlprague.cz -- signature.asc Description: OpenPGP digital signature
