Activity for DocBook Authoring and Publishing Suite
-
Stefan Knorr modified a comment on discussion DAPS General Discussion
Hello, Frank, Thomas, and I who are maintaining DAPS have decided that we should try to unify the web presence of DAPS as much as possible. This forum was the last part of DAPS still hosted on Sourceforge instead of GitHub. It too shall now go and be replaced by GitHub. Unfortunately, GitHub does not have forum functionality, but given the volume of this forum, it should be just fine to replace it with the GitHub issue tracker. There is now a new "forum" label on GitHub, please use it for discussion...
-
Hello, Frank, Thomas, and I who are maintaining DAPS have decided that we should try to unify the web presence of DAPS as much as possible. This forum was the last part of DAPS still hosted on Sourceforge instead of GitHub. It too shall now go and be replaced by GitHub. Unfortunately, GitHub does not have forum functionality, but given the volume of this forum, it should be just fine to replace it with the GitHub issue tracker. There is now a new "forum" label on GitHub, please use it for discussion...
-
DocBook Authoring and Publishing Suite released /README.md
-
Frank Sundermeyer posted a comment on discussion DAPS General Discussion
DAPS supports all profiling variables that upstream DocBook supports. These are XML: arch, DC-file: PROFARCH XML: audience, DC-file: PROFAUDIENCE XML: condition, DC-file: PROFCONDITION XML: conformance, DC-file: PROFCONFORMANCE XML: lang, DC-file: PROFLANG XML: os, DC-file: PROFOS XML: outputformat, DC-file: PROFOUTPUTFORMAT XML: revision, DC-file: PROFREVISION XML: revisionflag="added|changed|deleted|off, DC-file: PROFREVISIONFLAG XML: role, DC-file: PROFROLE XML: security, DC-file: PROFSECURITY...
-
Bob Stafford posted a comment on discussion DAPS General Discussion
For my project just using the condition variable for profiling is not enough I need to use multiple profiling variables. I've been trying to add these additional profiling parameters to the processing but it's truning out to be more complicated than I'd hoped, I've had to change the rng file, the stylesheets, and even the daps script but I've still not got it working. Is there a simpler way to add new profiling variables to the ones initially provided by DAPS?
-
That fixed it. Many thanks!!
-
Thomas Schraitle modified a comment on discussion DAPS General Discussion
Hi Bob, thanks for your message! Your eec-bookinfo.xml contains two issues: You use the DOCTYPE declaration of the DTD. Your info element does not include the DocBook 5 namespace. That's why you get validation errors, because an info element in no namespace is not allowed in DocBook 5. I would propose to change your code in eec-bookinfo.xml like this: <!DOCTYPE info> <info xml:id="eec-bookinfo" xmlns="http://docbook.org/ns/docbook"> <!--<title>&EDGE; Manual</title>--> <title>EDGE Manual</title> <!--...
-
Hi Bob, thanks for your message! Your eec-bookinfo.xml contains two issues: You use the DOCTYPE declaration of the DTD. Your info element does not include the DocBook 5 namespace. That's why you get validation errors, because an info element in no namespace is not allowed in DocBook 5. I would propose to change your code in eec-bookinfo.xml like this: <!DOCTYPE info [ <!ENTITY % xinclude SYSTEM "eec-xinclude.mod"> <!ENTITY % edge-defs SYSTEM "eec-edge-defs.mod"> %xinclude; %edge-defs; ]> --> <!--...
-
Further progress of sorts, by running the bigfile mode on my source I get this, whoch shows that the include has added two attributes to the info block, if I add those attributes to the info block directly in my book I get the same strange error about info not being allowed. So it seems include is adding attributes (xmlns="" xml:base="eec-bookinfo.xml") that upset the validator. <?xml version="1.0"?> <?xml-model href="http://docbook.org/xml/5.0/rng/docbookxi.rng" schematypens="http://relaxng.org/ns/structure/1.0"?><book...
-
The problem seems to be related to including the info block, if I put the info block directly in the book block it works <?xml version="1.0" encoding="UTF-8"?> <?xml-model href="http://docbook.org/xml/5.0/rng/docbookxi.rng" schematypens="http://relaxng.org/ns/structure/1.0"?> <book xml:id="book.edge.api" xml:lang="en" version="5.0" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xi="http://www.w3.org/2001/XInclude" xmlns="http://docbook.org/ns/docbook"> <info> <title>EDGE Manual</title> </info>...
-
I'm converting a docbook project to use daps and I'm getting messages like this one which seem to be saying that info is not allowed despite info being in the list of expected elements. Any suggestions are welcome. /home/bobstaff/pulse/doc/api/docbook/build/.profiled/noprofile/eec-bookinfo.xml:12:53: error: element "info" not allowed here; expected the element end-tag or element "acknowledgements", "appendix", "article", "bibliography", "chapter", "colophon", "dedication", "glossary", "index", "info",...
-
Hamish McIntyre-Bhatty posted a comment on discussion DAPS General Discussion
Good idea. I know docbook 5.0 works, because that's what I used to write my documentation that I process with DAPS.
-
The lack of DocBook 5(.1) is most likely also the reason why building the AsciiDoc manual fails during compilation. AsciiDoctor produces a DB 5 XML file from the AsciiDoc sources that gets validated afterwards. And that validation step fails in the example you posted above. I have created an issue for this: https://github.com/openSUSE/daps/issues/488
-
Fair enough :) Nope, still not working. A package search doesn't yield any docbook 5.1 - specific things, so I think there probably just isn't a package for the docbook 5.1 stuff. Thanks anyway :)
-
I forgot to mention, check also if you have installed the docbook-xsl-ns and docbook-xsl packages.
-
I'm running Linux Mint 19.1, based on Ubuntu 18.04. Also, how do I enable docbook 5.1 support - whatever I do it doesn't seem to enable it? I'm not very familiar with Ubunut or Linux Mint. For Ubuntu, however, I've found there is the docbook5-xml package. Try to install that the configure script will find the DocBook schema. Hope that will help. :-)
-
Thanks for quick reply. I have asciidoctor installed, but not asciidoc. It works now I've removed it - thanks :) Yeah, when I run the configure script, I get this: DocBook 5.1 support | no | install DocBook 5.1, the | | DocBook 5 XSL stylesheets, | | and jing jing is installed, so I'm assuming one of the others isn't, or it's not being detected that they are. I don't know how to install them though. It's always said this, so not new, but I have a different issue that I think might be related to this,...
-
Thanks for quick reply. I have asciidoctor insteadd, but not asciidoc. It works now Ive removed it - thanks :) Yeah, when I run the configure script, I get this: DocBook 5.1 support | no | install DocBook 5.1, the | | DocBook 5 XSL stylesheets, | | and jing jing is installed, so I'm assuming one of the others isn't, or it's not being detected that they are. I don't know how to install them though. It's always said this, so not new, but I have a different issue that I think might be related to this,...
-
Do you have asciidoctor or asciidoc as a build requirement? Looks like it builds the asciidoc documentation and fails to generate valid XML. I assume that this is caused by asciidoc. Can you try asciidoctor instead and see if it works? If not, try to remove asciidoc/asciidoctor from the build dependencies. In that case the asciidoc document will not be built and the error should go away (the resulting DAPS will, nevertheless support ASCIIDoc). Looks like I should work on https://github.com/openSUSE/daps/issues/486...
-
This looks great, but unfortunately I can't compile this. When I try, this is the output I get: make[1]: Entering directory '.../daps-3.0.0' touch build/.firstbuild make[2]: Entering directory '.../daps-3.0.0' make[2]: Leaving directory '.../daps-3.0.0' make[2]: Entering directory '.../daps-3.0.0' .../daps-3.0.0/doc/build/.profiled/noprofile/daps-asciidoc.xml:213:144: error: element "emphasis" not allowed here; expected the element end-tag, text or element "alt", "anchor", "annotation", "biblioref",...
-
Hi, almost 1 ½ years after DAPS 2.4 it is time for a new major release: DAPS 3.0. With this release we are proud to announce a significant addition to the DAPS feature set: AsciiDoc support. In addition to creating your documens from DocBook, you can now also create them from AsciiDoc sources. And it does not stop here: you will be able to use your existing DocBook stylesheets with your AsciiDoc sources! Want to know more details? See the AsciiDoc Quickstart (which, of course, was generated from...
-
Thanks for the report. Yes, seems FOP is incompatible with OpenJDK 1.8. Hmn, maybe the FOP package should require OpenJDK 10.
-
Thanks for the report. Yes, seems FOP is incompatible with OpenJDK 1.8. Hmn, maybe the FOP package should require this version.
-
Feathers and Down posted a comment on discussion DAPS General Discussion
Solved installing openjdk-10
-
Hi, I can't create pdf files. My system is openSUSE Leap 15.0 and using daps from default repos. When I do patricio@patriciodesktop:~/DocbookStock> daps -d DC-Especificacion-de-requerimientos -vv pdf Using MAIN file /home/patricio/DocbookStock/xml/MAIN-Especificacion-de-requerimientos.xml --------------- DAPS VERSION: 2.4.0 DOC_DIR: /home/patricio/DocbookStock BUILD_DIR: /home/patricio/DocbookStock/build DAPSROOT: /usr/share/daps DOCCONF: /home/patricio/DocbookStock/DC-Especificacion-de-requerimientos...
-
Martin Köditz posted a comment on discussion DAPS General Discussion
I will try your suggestion. I think that will take a while. Regards Martin
-
If that doesn't work, here are some further explanations: The templates in the autotoc.xsl file operates in these two modes: toc-abstract is used to create a summary for set and part elements. It uses the abstract elements to give you an additional hint about your books or parts. (This mode is created by us). toc is the "normal" mode which is also used from the upstream DocBook XSL stylesheets. This mode collects all the titles from the document. Additionally, we've customized the folloing templates:...
-
Hi Martin, I agree with Stefan, the autotoc.xsl file is a good start. To help you find your way, here are some additional tips. I want to create a table of contents for sets only including the book titles. Just to understand you correct, you want to change only the set TOC, but not the usual book TOC, right? In that case, I would try to customize the set.toc template. Replace the call for make.toc with your own code, for example: <xsl:template name="set.toc"> <xsl:param name="toc-context" select="."/>...
-
Uh, that is a good question. I think you are using a modified version of our SUSE stylesheets. I must admit, I think we (that is, mostly I) broke some parts of autotoc a bit. In particular, there is a ToC depth parameter, something akin to $toc.max.depth that might be helpful but is probably a bit broken in the HTML version (I don't think we ever changed much about the set ToC in the PDF version -- that use case was never quite as important to us). Nevertheless, I guess it is a good idea to at least...
-
Uh, that is a good question. I think you are using a modified version of our SUSE stylesheets. I must admit, I think we (that is, mostly I) broke some parts of autotoc a bit. In particular, there is a ToC depth parameter, something akin to $toc.max.depth that might be helpful but is probably a bit broken in the HTML version (I don't think we ever changed much about the set ToC in the PDF version -- that use case was never quite as important to us). Nevertheless, I guess it is a good idea to at least...
-
Hi, I want to create a table of contents for sets only including the book titles. Can you give me a hint where to start? Is it possible to extend the autotoc.xsl? Or is it better to create an own template? Currently I have a toc at the beginning of the set showing each entry of each book. But here I just need the books listed. The detailed toc should be shown in the book itself. Regards, Martin
-
Well, found it in fo/params.xsl at section 17. Miscellaneous. Regards, Martin
-
Hi, I have a question regarding PDF output. How can I put the descriptive text for pictures and tables under the objects instead of over them? I can't find the correct section in the style sheets. Regards, Martin
-
Hi, just some additional information: The absolute minimum on input DAPS needs is a MAIN file. Therefore it is sufficient to rum daps -m <MAIN>. In case you need to specify additional parameters such as a rootid or a stylesheet directory, you can use the respective command line parameters to set them. These additional parameters are usually the same for every build. That's why you can specify a DC-file that defines these parameters, so you do not have to specify them on every run of DAPS. A DC-file...
-
Anonymous posted a comment on discussion DAPS General Discussion
Well, I can use -m to define my xml file. But I have to set relative path. No more questions at this point.
-
I don't think so... There is daps -m MAIN.myblub.xml ... which can be used instead of daps -d DC-myblub .... Conceptually, the MAIN parameter and ROOTID are the centerpieces of a DC file -- the reason to introduce DC files was originally mostly to cache those two values [1]. However, I guess nothing stops you from using e.g. the daps -m ... syntax in a Makefile or so..? Not sure what your exact use case is here, though. hth Stefan [1] This is history told by someone who was not there at the inception...
-
I don't think so... There is -m MAIN.myblub.xml which can be used instead of -d DC-myblub. Conceptually, the MAIN parameter and ROOTID are the centerpieces of a DC file -- the reason to introduce DC files was originally mostly to cache those two values [1]. However, I guess nothing stops you from using e.g. the daps -m ... syntax in a Makefile or so..? Not sure what your exact use case is here, though. hth Stefan [1] This is history told by someone who was not there at the inception of DAPS, of ...
-
Anonymous posted a comment on discussion DAPS General Discussion
Hi, is there a command line switch to specify / override the MAIN value of DC file? Regards, Martin
-
Hi, Same person - I've just created an account now. Thank you, that's really helpful :) I'm actually running DAPS 2.2.0 that I compiled on Linux Mint, so I'd better recompile! Thanks again, Hamish
-
Hi, https://github.com/openSUSE/daps/commit/5c09e57 fixes the issue that requires to use different paths for admonition and callout graphics in PDF and HTML builds. It will be integrated into the next release. In case you ant to use it with DAPS 2.4.0, you have the following options: if you are directly using a git checkout,, switch to the develop branch and pull. If you prefer to stay on the stable master branch, create a branch from master and cherry-pick commit 5c09e57. It will update make/pdf.mk....
-
Hi, in general, you can pass any XSLT parameters or string parameters to DAPS similar to xsltproc: daps --stringparam="KEY=VALUE" --param="KEY=VALUE" However, with callouts, admonitions, and navigation graphics you also need to consider the path to the images. The respective parameters are named: admon.graphics.path callout.graphics.path navig.graphics.path In the upstream DocBook stylesheets--/usr/sharexml/docbook/stylesheets/(nwalsh|nwalsh5)/current on SUSE-- they are set to "mages/ and images/callouts/....
-
Anonymous posted a comment on discussion DAPS General Discussion
Hi there, This is probably a bit of a silly question, but I can't figure out how to enable the admonition icons. I've seen that with other parsers there's an options for this: with xsltproc, I've heard that you can do: xsltproc --stringparam admon.graphics 1 docbook.xsl myfile.xml But I haven't had any success doing similar things with DAPS. I'm very new, so if there's some resource that tells you how to do things like this I would be very grateful if someone could point me at it :) Hamish
-
Use the suse-xsl isse tracker: https://github.com/openSUSE/suse-xsl Thanks!
-
Patricio Mercado posted a comment on discussion DAPS General Discussion
Hi, where to publish this issue in github? in daps or opensuse susexls?
-
Install the package xml-commons-resolver12 to get rid of the Java/resolver issues. However, I am not sure about why you see the "can't determine DocBook version" error: If this is DocBook 5, make sure the namespace xmlns:d="http://docbook.org/ns/docbook". Replace :d with something appropriate, which can also be nothing depending on how your normal tags look -- i.e. whether they are explicitly namespaced (like <d:book/>) or whether they are implicitly namespaced (like <book/>). If this is DocBook...
-
Anonymous posted a comment on discussion DAPS General Discussion
Stefan, Thank you for your answer. Unfortunately nothing has changed. command is: daps --debug --xsltprocessor=saxon -d DC-file pdf The error is the same: "ERROR: Fatal: Could not determine the DocBook version......." I added in file ../bin/daps echo $DOCBOOK_VERSION in case of xsltproc echo returns 5 in case of saxon6 echo returns a lot of text like: Java virtual machine used: ..../bin/java classpath used: ..../java/xml-commons-apis.jar:.../java/jaxp_parser_impl.jar:../java/xml-commons-resolver12.jar:.../saxon65.jar::.../java/xml-commons-resolver.jar:/etc/java/resolver...
-
I can't promise that we will get to implementing every feature request on GitHub. But, I can pretty much promise that if there is no one who opens an issue for it, it will be forgotten at some point. :)
-
Iirc, profiling is broken with saxon6 ... what you could try maybe is this: Profile with xsltproc: daps -d ... profile Build with saxon: daps -d ... pdf --xsltproc=saxon There is no way to use saxon just for one of the steps otherwise, I think. Sorry.
-
iirc, profiling is broken with saxon6 ... what you could try maybe is this: Profile with xsltproc: daps -d ... profile Build with saxon: daps -d ... pdf --xsltproc=saxon
-
Anonymous posted a comment on discussion DAPS General Discussion
Hi! Could you help me please: I try to use saxon6 as XSLT PROCESSOR. The result is the following error: "Fatal: Could not determine the DocBook version from .............. Looks like ........ is not a DocBook 4/5 document." Why? If i use xsltproc, everything is OK. Daps version 2.4.0. Thanks in advance.
-
Uhm, understand... thanks, currently is not a must for me now, but hope some day that feature work, Is a thing that I found great to use.
-
Did you open an issue for this at https://github.com/openSUSE/suse-xsl ? I think this could reasonably be done without support from the formatter at least for HTML.
-
Did you open an issue for this at? https://github.com/openSUSE/suse-xsl I think this could reasonably be done without support from the formatter at least for HTML.
-
Not really. It's difficult... We always use xsltproc as an XSLT processor. Although daps can use Saxon6, it isn't really well tested. As Saxon6 is quite picky about some things expect problems. I've tried it in our doc-sleha project to see how far I will come. However, I got the following error message: Profiling /local/repos/GH/SUSE/doc-sleha/xml/art_sle_ha_install_quick.xml Validating... /local/repos/GH/SUSE/doc-sleha/build/.profiled/x86_amd64_em64t_sles/art_sle_ha_install_quick.xml:38:20: fatal:...
-
Not really. As Stefan already said, it's difficult... We always use xsltproc as an XSLT processor. Although daps can use Saxon6, it isn't really well tested. As Saxon6 is quite picky about some things expect problems. I've tried it in our doc-sleha project to see how far I will come. However, I got the following error message: Profiling /local/repos/GH/SUSE/doc-sleha/xml/art_sle_ha_install_quick.xml Validating... /local/repos/GH/SUSE/doc-sleha/build/.profiled/x86_amd64_em64t_sles/art_sle_ha_install_quick.xml:38:20:...
-
Hi, any news to this issue ?
-
Anonymous posted a comment on discussion DAPS General Discussion
Hi, thanks for your support. Changed file name and that work. This is a related issue: https://github.com/openSUSE/daps/issues/397 Thank you very much!.
-
After I've got the archive I could solve this. It has to do with an Unicode/UTF-8 character inside the filename. I haven'd found the tool to blame, but for the time being, it is probably a good idea to stick to ASCII-only filenames. Thanks Patricio for this bug report. Filed it as https://github.com/openSUSE/daps/issues/416
-
Anonymous posted a comment on discussion DAPS General Discussion
Hi, book have corresponding title tag too. Data sent. Thanks for your support :)
-
Hi Patricio, thanks for your answer. are inside same xml folder: MyDocs/xml/Glosario-Gestos.xml and MyDocs/xml/Main.....xml Ok, that's good. Inside book as direct child: <book> <xinclude:....../></book> Hmn, just a guess: it seems to me, you are missing a title element. This is mandatory. If your main file is not valid, the whole xinclude and postvalidation process will fail. Try the following structure in your main file: <book xml:id="mybook" xml:lang="es" version="5.1" xmlns:xlink="http://www.w3.org/1999/xlink"...
-
Hi Patricio, thanks for your answer. are inside same xml folder: MyDocs/xml/Glosario-Gestos.xml and MyDocs/xml/Main.....xml Ok, that's good. Inside book as direct child: <book> <xinclude:....../></book> Hmn, just a guess: it seems to me, you are missing a title element. This is mandatory. If your main file is not valid, the whole xinclude and postvalidation process will fail. Try the following structure in your main file: <book xml:id="mybook" xml:lang="es" version="5.1" xmlns:xlink="http://www.w3.org/1999/xlink"...
-
Anonymous posted a comment on discussion DAPS General Discussion
Hi, it's me again, Patricio. Thanks for your reply, I have to say about it that: Ok, will avoid entitites. I've added in this way: <glossary xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude" version="5.1" xml:lang="es"> but still error. To your questions: are inside same xml folder: MyDocs/xml/Glosario-Gestos.xml and MyDocs/xml/Main.....xml Inside book as direct child: <book> <xinclude:....../></book> No, will wait to openSUSE Leap 42.3 to reinstall my system (two weeks),...
-
Hi Patricio, thanks for your detailed report! Much appreciated. Some comments though: I would try to avoid example 1 (external entities) and always use XIncludes (example 2). In example 2, file Glosario-Gestos.xml is missing the DocBook5 namespace and a version attribute ( for example, version="5.1") I have also some questions: Are all XML files stored in the directory xml/? Where does the xi:include element in example 2 appear? I mean, does it appear directly as a child element under book or is...
-
Anonymous posted a comment on discussion DAPS General Discussion
Hello, I'm trying to include some external files in my Docbooks files, but have issues with daps or docbook. I've been following some tutorials/guides and everything I try it fails. Following are some try/errors based on some Docbook/Daps guides. Still can't find the way to include external files. Please help me with light to my knowledge darkness. Some words are in polish, don't know why. I added in my opensuse leap 42.2 polish input keyboard but I don't expect that outputs are in polish too. Example...
-
Anonymous posted a comment on discussion DAPS General Discussion
Thank you!
-
Hi, Could you tell me if I can use daps to transforming documents that are created using DocBook Assemblies Unfortunately not yet. However, we've tracked that already in DAPS issue#163. Currently, the Assembly schema and its documentation contains some discrepancies. I've filed a bug report which I hope will be fixed soon. Tom
-
Anonymous posted a comment on discussion DAPS General Discussion
Hi! Could you tell me if I can use daps to transforming documents that are created using DocBook Assemblies, for example: <assembly version="5.1" xmlns="http://docbook.org/ns/docbook" <info=""> title </info> <resources> <resource href="plan-strp-adf-12.2.1.2.0-art.xml" xml:id="plan-strp-adf-12.2.1.2.0-art"/> </resources> <structure renderas="book"> <module renderas="chapter" resourceref="plan-strp-adf-12.2.1.2.0-art"/> </structure> </assembly> Thank you!
-
-
-
-
Hi, it has been a long time since we released a new DAPS version, but we were pretty pleased with 2.3.0 and therefore reduced the pace a little bit. DAPS 2.4.0 is mainly a bugfix release and additionally comes with significant improvements on documentation. Download DAPS 2.4.0 For download alternatives and installation instructions refer to the installation instructions. Here is the complete list of changes: New Features added a dependency checker for DAPS (/usr/bin/daps-check-deps) that makes it...
-
Hi, it has been a long time since we released a new DAPS version, but we were pretty pleased with 2.3.0 and therefore reduced the pace a little bit. DAPS 2.4.0 is mainly a bugfix release and additionally comes with significant improvements on documentation. https://github.com/openSUSE/daps/releases/tag/2.4.0 For download alternatives and installation instructions refer to the https://github.com/openSUSE/daps/blob/master/INSTALL.adoc. Here is the complete list of changes: New Features added a dependency...
-
This makes me wonder about the scope of the daps project and not for the first time. Hm, so first: please differentiate between DAPS and the SUSE stylesheets. Those are separate projects, if somewhat interwoven. Most of the issues you name here seem to squarely fall into stylesheet territory. Anyway, both DAPS and stylesheet development is currently very much driven by internal needs. I realize that this does make it harder for you to work with them. On the other hand, it is all open-source and open...
-
This makes me wonder about the scope of the daps project and not for the first time. Hm, so first: please differentiate between DAPS and the SUSE stylesheets. Those are separate projects, if somewhat interwoven. Most of the issues you name here seem to squarely fall into stylesheet territory. Anyway, both DAPS and stylesheet development is currently very much driven by internal needs. I realize that this does make it harder for you to work with them. On the other hand, it is all open-source and open...
-
Thanks for this extraordinary quick resolution! You're welcome! :) See my other message about the fixed issues. The feature/footnotes branch has been merged into develop now. If you want to test our full fix, use the develop branch. But then there seems to be no test case for it. Yes. Testing is a difficult matter. Currently we don't have a really good solution for that... Other DocBook elements are not supported at all by daps. It's a matter of the stylesheets not DAPS. It would be very helpful...
-
Stefan Quandt posted a comment on discussion DAPS General Discussion
If you like, you can test it with the following commands. I can confirm that the PDF footnote scaling issue is resolved on branch feature/footnotes. Thanks for this extraordinary quick resolution! Currently, the SUSE documentation doesn't use footnotes at all. As such, we haven't customize it. This makes me wonder about the scope of the daps project and not for the first time. Obviously the Docbook <footnote> element has been well supported by the suse and daps stylesheets for ages. But then there...
-
Stefan, your issue has been fixed now. \o/ :-) You can see the result here: https://github.com/openSUSE/suse-xsl/issues/314#issuecomment-305790204 Let us know if it works for you.
-
This should be fixed with the latest commit in the above pull request. The other Stefan is currently reviewing it. ;-)
-
On the other hand, when generating HTML everything is fine with the footnote. Yeah, HTML is totally different code than FO/PDF. Interestingly, upgrading to suse-xsl-2.7.0.2 requires upgrading of package liberation-fonts to liberation2-fonts. Could this cause some font selection incompability? It should not. We mostly did this because the old liberation-fonts package was being dropped and we were one of the last packages still depending on it. I think on older (supported SLE/openSUSE) distributions...
-
Thanks Stefan for your report! Currently, the SUSE documentation doesn't use footnotes at all. As such, we haven't customize it. This is why you see these strange result. Nevertheless, I've found the cause of this font size problem and opened a pull request on Github, see https://github.com/openSUSE/suse-xsl/pull/313 (can add you as reviewer, if you are available on Github) :) If you like, you can test it with the following commands. First you need to clone the stylesheet repo: $ cd /tmp/$USER $...
-
if I install the older version 2.0.6.3 of the suse-xsl stylesheets package from openSUSE LEAP then everything is fine. Interestingly, upgrading to suse-xsl-2.7.0.2 requires upgrading of package liberation-fonts to liberation2-fonts. Could this cause some font selection incompability? Anyhow, I'd assume that this problem will be reproducible on any openSUSE box with suse-xsl-2.7.0.2 by generating PDF from a simple DocBook5 document with a <footnote> element.
-
I just noticed that the footnotes are not only too big, they are also lacking the number on the left (while the in-text foonote reference number is present). On the other hand, when generating HTML everything is fine with the footnote.
-
I use the suse-xsl stylesheets from git with several minor customizations to e.g. to parameters body.font, body.font.family, booktitlepage.url, company.address and changes in colors.ent regarding FO (and several parameters in the XHTML stylesheets and style.css). If I revert all these customizations (and build and install the stylesheets) or if I install the suse-xsl stylesheets package from openSUSE LEAP (currently 2.7.0.2) footnotes in generated PDF are still too big. Running DAPS with "-vv" yields...
-
Which stylesheets are you using? (Will be visible when running DAPS with "-vv") I assume this is not a DAPS problem but caused by a change in the fo-stylesheets.
-
Hi, I just noticed that in daps PDF output built from DocBook5 sources the font size used for rendering <footnote> elements increased dramatically (its now bigger than any heading). Fortunately I had some old .fo files around in the build/.tmp directory on my production machine and found that the <fo:footnote-body> elements in FO files for unknown reason changed from <fo:footnote-body font-family="'Open Sans', OpenSans, sans-serif,'FreeSerif', serif" font-size="9pt" ... to <fo:footnote-body font-family="'Open...
-
Hi, the bird thingie... LEO was my friend. Zwei Fliegen mit einer Klappe, und so......
-
Anonymous posted a comment on discussion DAPS General Discussion
Hi Tom, the bird thingie... LEO was my friend. Zwei Fliegen mit einer Klappe, und...
-
Hi, I thought I could kill two birds with one stone. Poor birds. ;-) ;-) My DocBook...
-
Anonymous posted a comment on discussion DAPS General Discussion
Hi, I assume that it is not possible to transform DocBook(5) to WordML with DAPS?...
-
Anonymous posted a comment on discussion DAPS General Discussion
Hi Tom, thanks. Too bad... I thought I could kill two birds with one stone. My DocBook...
-
Hi, I assume that it is not possible to transform DocBook(5) to WordML with DAPS?...
-
I was struggling with the correct syntax a lot, hence here's a simple and working...
-
Hi Stefan, thanks for your response! So, the error message you have there really...
-
Hi Stefan, I can tell you that DAPS does not do any external validation of generated...
-
Hi, Apache FOP since release 2.0 has support for fo:float. Hence placing text beside...
-
Hi, a pretty wet summer made us stay indoors, so we present a new DAPS version just...
-
Hi Stefan, the areaspec element is a nasty one: to process it correctly, you need...
-
Hi, I want to annotate an image by using a <calloutlist> referencing elements of...
-
Thank you Stefan.
-
1 >
