[docbook-apps] positioning toc

[Frank Arensmeier]

Hello all.

I am rather new to docbook and in the middle of taking one step at a  
time to the final result. Basically, I am working on a system for  
producing and maintaining operating instructions in several different  
languages.


Right now I'm stuck though. My idea is to produce a single pdf file  
(docbook xsl -> fo -> pdf) that can contain up to 12 translations. I  
am rather close to what I want, but the thing that gives me headaches  
is the toc. On page 2, I have a basic toc with a list of languages  
including page numbers only (no problem here). I was able to  
accomplish that by adding the following snippet to my customization  
layer:



  
  


But I also want a toc generated at the beginning of each article that  
is part of the xml document. And I have no clue how to do that. Google  
was not my friend this time, I am afraid. If there is anybody willing  
to share some ideas, I would be delighted.


Here is the basic outline of my source XML document:


Product XY


Operating instructions
Bedienungsanleitung
...



Some title
Some subtitle




...



Some title
Some subtitle




...




Thank you.
/frank


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: AW: [docbook-apps] positioning toc

[Frank Arensmeier]

Hello.

Thank you. Tweaking the parameter "generate.toc" did it!

/frank
9 feb 2010 kl. 22.11 skrev Alexander Rabenstein:


Hi,

perhaps that link can help you:

http://docbook.sourceforge.net/release/xsl/current/doc/html/generate.toc.htm
l
see also

http://docbook.sourceforge.net/release/xsl/current/doc/html/generate.section
.toc.level.html

Kind Regards

Alexander Rabenstein

-Ursprüngliche Nachricht-
Von: Frank Arensmeier [mailto:fr...@nikemedia.se]
Gesendet: Dienstag, 9. Februar 2010 16:00
An: docbook-apps@lists.oasis-open.org
Betreff: [docbook-apps] positioning toc

Hello all.

I am rather new to docbook and in the middle of taking one step at a
time to the final result. Basically, I am working on a system for
producing and maintaining operating instructions in several different
languages.

Right now I'm stuck though. My idea is to produce a single pdf file
(docbook xsl -> fo -> pdf) that can contain up to 12 translations. I
am rather close to what I want, but the thing that gives me headaches
is the toc. On page 2, I have a basic toc with a list of languages
including page numbers only (no problem here). I was able to
accomplish that by adding the following snippet to my customization
layer:


  
  


But I also want a toc generated at the beginning of each article that
is part of the xml document. And I have no clue how to do that. Google
was not my friend this time, I am afraid. If there is anybody willing
to share some ideas, I would be delighted.

Here is the basic outline of my source XML document:


Product XY


Operating
instructions
Bedienungsanleitung
...



Some title
Some subtitle




...



Some title
Some subtitle




...




Thank you.
/frank


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis- 
open.org







-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

[docbook-apps] Styling subtitle

[Frank Arensmeier]

Hello.

I'd like to apply some special font style on section subtitles in my  
pdf but I am not able to find any applicable properties to tweak. I  
have tried to set section.title.level2.properties (and level3...level6  
too for that matter). But it seems that those properties have no  
effect what so ever. I am really not an xsl expert... looking at the  
file "sections.xsl" in the docbook 'fo' directory, it seems to me that  
section subtitles should be considered as level2 section titles, or  
not? The fo output file contains this part:


[snip]
  
family="sans-serif,Symbol,ZapfDingbats" margin-left="0pc">

  
weight="normal" keep-with-next.within-column="always" space- 
before.minimum="0.8em" space-before.optimum="1.0em" space- 
before.maximum="1.2em" text-align="start" start-indent="0pc" font- 
style="normal" font-size="30pt" color="magenta">
  name="section.head.marker">Section title
  font-weight="normal" font-style="normal" color="#0072BA">Section  
title


  

family="sans-serif,Symbol,ZapfDingbats">Section subtitle

  

[/snip]

Basic outline of my XML is:


Section title
Section subtitle
Paragraph goes here



The subtitle is always rendered with Helvetica as font family, even  
though I've set the body font family to something else. What am I  
doing wrong? Any ideas?


/frank

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

[Frank Arensmeier]

Hello Bob.

Thank you very much. Perfect! And it works too!
/frank

15 feb 2010 kl. 19.08 skrev Bob Stayton:


Hi Frank,
In the DocBook XSL stylesheets, only title has its own attribute  
set.  Beyond title, an info element can contain lots of other  
elements, and those are handled by the titlepage spec mechanism.   
That is described in my book:


http://www.sagehill.net/docbookxsl/HTMLTitlePage.html

In your specific case, you can accomplish what you want with the  
following addition to a titlepage spec file before you compile it:




  
  
   ...

(I added color="blue" just to demonstrate that it works, but you  
probably don't want that).


Bob Stayton
Sagehill Enterprises
b...@sagehill.net


- Original Message ----- From: "Frank Arensmeier" >

To: 
Sent: Saturday, February 13, 2010 4:28 AM
Subject: [docbook-apps] Styling subtitle



Hello.

I'd like to apply some special font style on section subtitles in  
my  pdf but I am not able to find any applicable properties to  
tweak. I  have tried to set section.title.level2.properties (and  
level3...level6  too for that matter). But it seems that those  
properties have no  effect what so ever. I am really not an xsl  
expert... looking at the  file "sections.xsl" in the docbook 'fo'  
directory, it seems to me that  section subtitles should be  
considered as level2 section titles, or  not? The fo output file  
contains this part:


[snip]
 
   family="sans-serif,Symbol,ZapfDingbats" margin-left="0pc">

 
   weight="normal" keep-with-next.within-column="always" space-  
before.minimum="0.8em" space-before.optimum="1.0em" space-  
before.maximum="1.2em" text-align="start" start-indent="0pc" font-  
style="normal" font-size="30pt" color="magenta">
 name="section.head.marker">Section title
 color="#0072BA">Section  title

   
 
   
   family="sans-serif,Symbol,ZapfDingbats">Section subtitle

 
   
[/snip]

Basic outline of my XML is:


Section title
Section subtitle
Paragraph goes here



The subtitle is always rendered with Helvetica as font family,  
even  though I've set the body font family to something else. What  
am I  doing wrong? Any ideas?


/frank

-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org








-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

[docbook-apps] Help with xsl template for image on the titlepage

[Frank Arensmeier]

Hello list members.

After hours and hours of trail-and-error, I finally ran out of ideas.  
I am looking for a way to control presentation of one particular image  
that is supposed to be used on a titlepage (without editing the input  
XML). What I have achieved  so far is:


1) I customised the titlepage.templates.xml file found in the fo  
directory.

2) my titlepage now contains the article title, subtitle and one image
3) The input XML contains the imageobject (the one that is supposed to  
find its way to the titlepage) as the first child of the articleinfo  
node.


What I want to do is, in my customisation layer, to set a fixed size  
for that particular image and the corresponding image container.


One of my ideas was to tweak the graphics.xsl template, hard code the  
values for size of the image and the image container and include that  
customized template in my customization layer. I actually did succeed  
tweaking the template to my needs. One side effect was that the  
customized template was applied to all mediaobjects, not just the one  
on the titlepage. My impression was that by adding 'mode="titlepage"  
to the template, it would only apply to the titlepage. But that turned  
out to be wrong.


So my question how can I hardcode attributes (scaling, size etc.) for  
a particular image in my customization layer.


Am I making sense?

Thank you for your input.
/frank




-
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] Help with xsl template for image on the titlepage

[Frank Arensmeier]

Actually, I solved the puzzle by myself.

Just for the record, here is what I did.

1) In my titlepage template I added:

t:wrapper="fo:block" />


2) In my customization layer I added:

  

  
	

  

  

/frank

22 mar 2010 kl. 13.11 skrev Frank Arensmeier:


Hello list members.

After hours and hours of trail-and-error, I finally ran out of  
ideas. I am looking for a way to control presentation of one  
particular image that is supposed to be used on a titlepage (without  
editing the input XML). What I have achieved  so far is:


1) I customised the titlepage.templates.xml file found in the fo  
directory.

2) my titlepage now contains the article title, subtitle and one image
3) The input XML contains the imageobject (the one that is supposed  
to find its way to the titlepage) as the first child of the  
articleinfo node.


What I want to do is, in my customisation layer, to set a fixed size  
for that particular image and the corresponding image container.


One of my ideas was to tweak the graphics.xsl template, hard code  
the values for size of the image and the image container and include  
that customized template in my customization layer. I actually did  
succeed tweaking the template to my needs. One side effect was that  
the customized template was applied to all mediaobjects, not just  
the one on the titlepage. My impression was that by adding  
'mode="titlepage" to the template, it would only apply to the  
titlepage. But that turned out to be wrong.


So my question how can I hardcode attributes (scaling, size etc.)  
for a particular image in my customization layer.


Am I making sense?

Thank you for your input.
/frank




-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis- 
open.org






-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

[docbook-apps] Titleabbrev in outer margin

[Frank Arensmeier]

Hello list.

I am not a XSL programmer, so I kindly ask you to bear with me. I have  
a docbook compilant XML file (an operating instruction) that contains  
several different languages. Basic outline of the XML file is:



  

English
[...]
  
  

Deutsch
[...]
  


What I like to accomplish is putting the language names into the outer  
margin of my pdf. I found an example in the mailing list archives (http://www.mail-archive.com/docbook-apps@lists.oasis-open.org/msg12243.html 
) which describes a way to extend the pagesetup.xsl template with a  
static content region.


After some tweaks, I actually managed to incorporate the example into  
my customization layer. However, I need to find a way to calculate an  
offset value for the top position of the fo-block that contains the  
language name. Whenever the language name changes, the offset should  
increase (and the fo block moves down). Right now, those fo-block  
containers always have the same position.


My idea was to get the position of the parent element in the xml tree  
(the article element) and calculate the offset based on that. But I  
must be doing something wrong. Here is what I have come up with so far.


1) Changed the pagesetup.xsl template:

  
  

  
  

  


  
  

  

  
  

  



  





  
[...]


2) Template for the sidebar



  
  

  

  
size="1em" color="white" font-weight="bold">

  

  


3) Template for calculating the position of the article element


  
  
  Position is: xsl:message>



But, the position is always 1. Is the basic idea of calculating the  
offset value for the top position with help of the parent element  
position feasible or is there an easier way?


Kind regards,
/frank


-
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] Titleabbrev in outer margin

[Frank Arensmeier]

Sorry to bother you all. Any ideas regarding this issue?
Thank you.

/frank

23 mar 2010 kl. 13.02 skrev Frank Arensmeier:


Hello list.

I am not a XSL programmer, so I kindly ask you to bear with me. I  
have a docbook compilant XML file (an operating instruction) that  
contains several different languages. Basic outline of the XML file  
is:



 
   
   English
   [...]
 
 
   
   Deutsch
   [...]
 


What I like to accomplish is putting the language names into the  
outer margin of my pdf. I found an example in the mailing list  
archives (http://www.mail-archive.com/docbook-apps@lists.oasis-open.org/msg12243.html 
) which describes a way to extend the pagesetup.xsl template with a  
static content region.


After some tweaks, I actually managed to incorporate the example  
into my customization layer. However, I need to find a way to  
calculate an offset value for the top position of the fo-block that  
contains the language name. Whenever the language name changes, the  
offset should increase (and the fo block moves down). Right now,  
those fo-block containers always have the same position.


My idea was to get the position of the parent element in the xml  
tree (the article element) and calculate the offset based on that.  
But I must be doing something wrong. Here is what I have come up  
with so far.


1) Changed the pagesetup.xsl template:

 
 

 
 
   
 
   

 
 
   
 
   
 
 
   
 
   
   
   
 
   

   
   

 
[...]


2) Template for the sidebar



 
 
   
 

 
   size="1em" color="white" font-weight="bold">

 
   
 


3) Template for calculating the position of the article element


 
 
 Position is: xsl:message>



But, the position is always 1. Is the basic idea of calculating the  
offset value for the top position with help of the parent element  
position feasible or is there an easier way?


Kind regards,
/frank


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis- 
open.org






-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook-apps] Titleabbrev in outer margin

[Frank Arensmeier]

Just for the record. I found the solution by myself. The following  
xpath expression gives me the position of the article element in the  
xml tree:



  



Based on that, I managed to calculate the offset value for the  
fo:block that contains the titleabbrev.


/frank

24 mar 2010 kl. 18.46 skrev Frank Arensmeier:


Sorry to bother you all. Any ideas regarding this issue?
Thank you.

/frank

23 mar 2010 kl. 13.02 skrev Frank Arensmeier:


Hello list.

I am not a XSL programmer, so I kindly ask you to bear with me. I  
have a docbook compilant XML file (an operating instruction) that  
contains several different languages. Basic outline of the XML file  
is:




  
  English
  [...]


  
  Deutsch
  [...]



What I like to accomplish is putting the language names into the  
outer margin of my pdf. I found an example in the mailing list  
archives (http://www.mail-archive.com/docbook-apps@lists.oasis-open.org/msg12243.html 
) which describes a way to extend the pagesetup.xsl template with a  
static content region.


After some tweaks, I actually managed to incorporate the example  
into my customization layer. However, I need to find a way to  
calculate an offset value for the top position of the fo-block that  
contains the language name. Whenever the language name changes, the  
offset should increase (and the fo block moves down). Right now,  
those fo-block containers always have the same position.


My idea was to get the position of the parent element in the xml  
tree (the article element) and calculate the offset based on that.  
But I must be doing something wrong. Here is what I have come up  
with so far.


1) Changed the pagesetup.xsl template:






  

  



  

  


  

  
  
  

  

  
  


[...]


2) Template for the sidebar





  



  size="1em" color="white" font-weight="bold">


  



3) Template for calculating the position of the article element




Position is: xsl:message>



But, the position is always 1. Is the basic idea of calculating the  
offset value for the top position with help of the parent element  
position feasible or is there an easier way?


Kind regards,
/frank


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org





-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis- 
open.org






-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

[docbook-apps] General question about creating docbook documents (maybe OT)

[Frank Arensmeier]

Hi there.

I would like to ask the list members: how do you create docbook- 
compilant XML documents? What does your workflow looks like so to say?  
Do you write XML files in a XML editor? A web interface? My apologies  
if this is slightly off topic.


I am asking this purely because I am interested (of course...). My  
employer is a manufacturer of industrial goods and tools. Until now,  
all our technical documentation (mainly operating instructions and  
spare parts lists) have been made with Indesign. And over time, we  
faced some very big problems:


1) Because technical documentation must be translated into many  
different languages, providing translators with documents that they  
can edit has been a hassle. In the best case, some translators had  
access to Indesign and were able to edit the original document. Re- 
using existing translations though wasn't easy / possible with this  
approach.


2) Updating existing documentation depends on remembering. E.g if one  
needed to change a product name or some technical data, you must know  
the documents where that data appears (sometimes, several different  
documents are effected by a change and those documents had several  
different translations). A simple change could easily take several  
hours to do.


3) Keeping track of what was changed, when and by whom had been a real  
mystery and still is.


A year ago or so, I was able to convince by employer to utilize a  
docbook-based workflow for creating technical documentation. At that  
time, I was looking for applications, tools and so on that would make  
this workflow feasible. Because some of the guys working with  
technical documentation are not very tech savvy, I was looking for a  
more or less intuitive, easy-to-use (web-based) solution - without  
much success.


However, because I couldn't find anything affordable (some systems  
cost about 100.000 EUR), I sat down and developed a system by myself.  
The web-based system I came up with makes building a docbook XML file  
(and converting to PDF)  a matter of drag-and-drop (with validation of  
course), it keeps track of all changes and it is comparably easy to  
use for a none-programmer. Besides that, having documentation in many  
different languages is now a no-brainer. But every now and then, I was  
wondering if there had been a more simple solution.


Regards,
/frank

ps. if someone would like to have a look at the system, you are  
welcome to contact me off-list ds.


-
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] General question about creating docbook documents (maybe OT)

[Frank Arensmeier]

14 apr 2010 kl. 11.38 skrev Mathieu Malaterre:

On Wed, Apr 14, 2010 at 10:02 AM, Frank Arensmeier  
 wrote:

Hi there.

I would like to ask the list members: how do you create docbook- 
compilant
XML documents? What does your workflow looks like so to say? Do you  
write
XML files in a XML editor? A web interface? My apologies if this is  
slightly

off topic.


I started working with docbook a couple of months back, so my
experience is very limited. Since we do software, we are internally
using cmake+ctest+cdash for managing our regression technique.
All I had to do is write a custom cmake script so that instead of
compilation errors, I know reports error of xmllint --valid. I also
catch error (on stdout) when running fop, and xstlproc.

I personnally use vim + serna to edit docbook (both are debian
packages), some coworkers uses emacs and I think one is using XXE at
times.

Cheers
--
Mathieu



Hello Mathieu.

So it seems that you have to deal with more or less highly skilled  
programmers then, not "average endusers", right? One big problem for  
my part was that most of the more common workflow outlines I found on  
the net were incorporating e.g. Oxygen or similar editors. Because we  
needed a tool that even users with only limited IT knowledge could use  
without too much trouble, those workflows where just too complicated.


Docbook in combination with XSL-FO is a great thing. But it seems to  
me that there is a gap to fill for user friendly authoring systems.


Regards,
/frank

-
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] Status on Simplified docbook?

[Frank Arensmeier]

Hello!

Just a quick question. Currently, the Docbook subset Simplified Docbook is 
based on Docbook V4.3 (according to the documentation at OASIS) . Any plans to 
update to Docbook 5 in the near future? Besides that, I was not able to find 
any Relax-NG schema for Simplified Docbook, only DTD. I read somewhere that 
Relax NG schema for Docbook should be considered as normative. Are there any 
Relax NG schema files for Simplified Docbook for download somewhere?

Thank you.
/frank


-
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] Ugly stack trace with admon.graphics and FO

[Frank Arensmeier]

Hello Steve!

The error you get is most likely caused by some erroneous PNG image file or 
some other image file with alpha transparency. Ask Google for more information 
about this issue. You need to find out which image file is causing the error. 
The most common solution is to simply run that image file through ImageMagick. 
See e.g.

http://comments.gmane.org/gmane.text.xml.fop.user/31508

Regards,
/frank

26 apr 2011 kl. 00.45 skrev Steve Johnson:

> In my customization file for FO processing, I have this:
> 
> 
> Graphics/
> 
> If I change the first line to:
> 
> 
> 
> I get a horrendously long and ugly stack trace and I don't know why. Help? 
> (xsltproc handles it fine)
> 
> Apr 25, 2011 5:44:02 PM org.apache.fop.fo.FOTreeBuilder fatalError
> SEVERE: javax.xml.transform.TransformerException: 
> java.lang.NullPointerException: Parameter alpha must not be null
> Apr 25, 2011 5:44:02 PM org.apache.fop.cli.Main startFOP
> SEVERE: Exception
> javax.xml.transform.TransformerException: java.lang.NullPointerException: 
> Parameter alpha must not be null
>at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:217)
>at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:125)
>at org.apache.fop.cli.Main.startFOP(Main.java:166)
>at org.apache.fop.cli.Main.main(Main.java:197)
> Caused by: javax.xml.transform.TransformerException: 
> java.lang.NullPointerException: Parameter alpha must not be null
>at 
> org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2416)
>at 
> org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:1374)
>at 
> org.apache.xalan.templates.ElemApplyTemplates.transformSelectedNodes(ElemApplyTemplates.java:393)
>at 
> org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.java:176)
>at 
> org.apache.xalan.templates.ElemApplyTemplates.transformSelectedNodes(ElemApplyTemplates.java:393)
>at 
> org.apache.xalan.templates.ElemApplyTemplates.execute(ElemApplyTemplates.java:176)
>at 
> org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2411)
>at org.apache.xalan.templates.ElemIf.execute(ElemIf.java:160)
>at 
> org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2411)
>at org.apache.xalan.templates.ElemChoose.execute(ElemChoose.java:139)
>at 
> org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2411)
>at org.apache.xalan.templates.ElemChoose.execute(ElemChoose.java:139)
>at 
> org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2411)
>at org.apache.xalan.templates.ElemChoose.execute(ElemChoose.java:139)
>at 
> org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2411)
>at 
> org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(TransformerImpl.java:2281)
>at 
> org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1367)
>at 
> org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:709)
>at 
> org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1284)
>at 
> org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1262)
>at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:214)
>... 3 more
> Caused by: java.lang.NullPointerException: Parameter alpha must not be null
>at org.apache.fop.pdf.AlphaRasterImage.(AlphaRasterImage.java:54)
>at org.apache.fop.pdf.AlphaRasterImage.(AlphaRasterImage.java:68)
>at 
> org.apache.fop.render.pdf.ImageRenderedAdapter.setup(ImageRenderedAdapter.java:101)
>at org.apache.fop.pdf.PDFDocument.addImage(PDFDocument.java:823)
>at 
> org.apache.fop.render.pdf.PDFImageHandlerRenderedImage.generateImage(PDFImageHandlerRenderedImage.java:58)
>at 
> org.apache.fop.render.pdf.PDFRenderer.putImage(PDFRenderer.java:1745)
>at 
> org.apache.fop.render.pdf.PDFRenderer.renderImage(PDFRenderer.java:1679)
>at 
> org.apache.fop.render.AbstractRenderer.renderViewport(AbstractRenderer.java:743)
>at 
> org.apache.fop.render.AbstractPathOrientedRenderer.renderViewport(AbstractPathOrientedRenderer.java:621)
>at 
> org.apache.fop.render.AbstractRenderer.renderInlineArea(AbstractRenderer.java:626)
>at 
> org.apache.fop.render.pdf.PDFRenderer.renderInlineArea(PDFRenderer.java:1345)
>at 
> org.apache.fop.render.AbstractRenderer.renderLineArea(AbstractRenderer.java:601)
>at 
> org.apache.fop.render.pdf.PDFRenderer.renderLineArea(PDFRenderer.java:1336)
>at 
> org.apache.fop.render.AbstractRenderer.renderBlocks(AbstractRenderer.java:536)
>at 
> org.apache.fop.render.AbstractRenderer.renderBlock(Abstrac

[docbook-apps] Customising blank page after part title page

[Frank Arensmeier]

Hello all.

Is there a (more or less simple) way to customise the blank page that is 
inserted after the titlepage when generating FO output? In my customisation 
layer I have tried with different template names: page.titlepage.before.blank, 
lot.titlepage.before.recto etc. But nothing makes it into the final FO file. Is 
the only option to customise page masters?

Thank you.
/frank



-
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] Customising blank page after part title page

[Frank Arensmeier]

Thank's Bod!

That was really helpful.
/frank

6 okt 2011 kl. 17.24 skrev Bob Stayton:

> Hi,
> That blank page is actually the verso titlepage, but just has nothing on it. 
> There are two ways to customize the part verso titlepage.
> 
> 1.  Customize the titlepage specs and regnerate the titlepage templates.
> That process is described here:
> 
> http://www.sagehill.net/docbookxsl/TitlePagePrint.html#PrintTitlepageSpecfile
> 
> 2.  Directly write a custom template named 'part.titlepage.verso'.  Put in 
> whatever fo:blocks and properties you want to format that content, and it 
> will be presented on that page. You don't need to create a page-sequence 
> because that is already handled. But you might need to put a page break the 
> template named 'part.titlepage.before.verso', as I don't think that is 
> already done.
> 
> The templates used for each of the titlepages and their dividers can be found 
> in the file fo/titlepage.templates.xsl.  The group for each DocBook element 
> is contained in a template named 'elementname.titlepage', such as 
> 'part.titlepage'.  That file is generated from the stock titlepage spec file 
> named titlepage.templates.xml using the process described in option 1.  But 
> you can override any of those with a  direct custom template of your own.
> 
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
> 
> 
> - Original Message - From: "Frank Arensmeier" 
> To: "Docbook Apps Help list" 
> Sent: Thursday, October 06, 2011 5:34 AM
> Subject: [docbook-apps] Customising blank page after part title page
> 
> 
> Hello all.
> 
> Is there a (more or less simple) way to customise the blank page that is 
> inserted after the titlepage when generating FO output? In my customisation 
> layer I have tried with different template names: 
> page.titlepage.before.blank, lot.titlepage.before.recto etc. But nothing 
> makes it into the final FO file. Is the only option to customise page masters?
> 
> Thank you.
> /frank
> 
> 
> 
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
> 
> 
> 


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

[docbook-apps] Simplified Docbook Relax NG schema

[Frank Arensmeier]

Hello. 

For a system I am working on right now, I need the simplified docbook Relax NG 
schema file. Google yield the following page:
http://www.docbook.org/docbook-ng/simple/

Not sure if those files are official. Anyway. Everything is working great 
except the fact that elements like "warning" and "caution" are not part of 
those schema file. I am not sure if there are any other elements missing too. 
Is this intended?

Thank you.
/frank
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook-apps] Re: Simplified Docbook Relax NG schema

[Frank Arensmeier]

25 okt 2011 kl. 20.21 skrev Norman Walsh:

> Frank Arensmeier  writes:
>> Not sure if those files are official. Anyway. Everything is working
>> great except the fact that elements like "warning" and "caution" are
>> not part of those schema file. I am not sure if there are any other
>> elements missing too. Is this intended?
> 
> Yes. Simplified DocBook is designed to have only about 100 tags. It's
> more-or-less HTML-level markup in DocBook.

I have used Simplified DB before but with a DTD schema. Actually, it turned out 
that I must have altered that DTD file with the "caution" and "warning" 
elements sometime in the past. When I switched to the Relax NG file, I noticed 
that "caution" and "warning" (obviously) weren't there anymore. Therefore my 
question. 

> I hope to have a new release of the schema shortly.

That's good news. 

>Be seeing you,
>  norm
> 
> -- 
> Norman Walsh   | Society is immoral and immortal;
> http://www.oasis-open.org/docbook/ | it can afford to commit any kind
> Chair, DocBook Technical Committee | of folly, and indulge in any kind
>   | of vice; it cannot be killed, and
>   | the fragments that survive can
>   | always laugh at the dead.--Henry
>   | Adams


-
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] feedback, suggestions and criticism?

[Frank Arensmeier]

Hello all!

I'm a long time subscriber to this list but haven't been tremendously 
participating in discussions. Please forgive me if this is not the right place 
to ask.

Some years ago, I started developing an on-line publishing system based on 
Docbook with the main focus on multilingual technical documentation. Today, two 
years later, my work has resulted in something I feel really excited about. My 
plan is to release the system as a commercial (maybe open source) alternative 
within the next three or four month to come. The current version still needs 
some work on several parts. However, many parts are working quite well.

I am aware of the fact that it's rather late in the development process. But 
what I am looking for is feedback – suggestions, criticism and encouragement. 
Working as a "one-man-company" has definitely it's pros and cons. One of the 
drawbacks unfortunately (at least for my part) is that I do not know many 
people I could show the system for.

Some background information. Almost a year ago, my former employer went 
bankrupt and since then, I try to feed my family with my own one-man-business. 
I started developing a Docbook-based publishing system some years ago, which 
has led to different "reincarnations" of that system during that time. Back 
then (in my role as employee), I was looking for feasible systems that could 
help us in the production of technical documentation such as instruction 
manuals, spare parts lists and so on. Especially systems with good support for 
(printed and online) technical documentation in several different languages. 
And because the systems I looked at were either too expensive or too limited, I 
decided to write my "own" system.

The fact that I am not a programmer at the first place, has had a great 
influence on my approach when it comes to designing the system so to say. I 
tried to focus on ease-of-use and thoughtful design. And this stands in 
contrast to the systems I have seen so far.

So, to sum up, feel free to contact me off-list and I am happy to give you more 
information about the system and access to the demo installation.

Regards,
/frank arensmeier

ps. sorry for my lacking english skills. English is not my mother tongue. ds.

-
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] Error messages when building webhelp

[Frank Arensmeier]

Hello all.

I am trying to build webhelp but keep getting error messages. Not even the 
webhelp test build does it's job. Any idea what is going on here? The docbook 
stylesheets are 1.76.1 and saxon 6.5.5 is installed as it should. Running ant 
with the "noclasspath" option does not help (as pointed out here 
http://docbook.sourceforge.net/release/xsl/current/webhelp/docs/content/ch02s01.html).
 Building webhelp fails with the following output:

Buildfile: /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/build.xml

validate:

clean:
   [delete] Deleting directory 
/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/test-ouput

chunk:
[mkdir] Created dir: 
/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/test-ouput
 [xslt] Processing 
/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/docsrc/readme.xml to 
/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/test-ouput/dummy.html
 [xslt] Loading stylesheet 
/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/xsl/webhelp.xsl
 [xslt] : Warning! 
file:/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/xhtml/autoidx.xsl: line 
502: Attribute 'href' outside of element.
 [xslt] : Warning! 
file:/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/xhtml/lists.xsl: line 
728: Attribute 'type' outside of element.
[...]
 [xslt] : Error! null
 [xslt] Failed to process 
/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/docsrc/readme.xml

BUILD FAILED
/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/build.xml:34: 
javax.xml.transform.TransformerException: java.lang.NullPointerException
at 
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:716)
at 
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313)
at 
org.apache.tools.ant.taskdefs.optional.TraXLiaison.transform(TraXLiaison.java:194)
at 
org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:852)
at 
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:388)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
at 
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
at org.apache.tools.ant.Main.runBuild(Main.java:809)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Caused by: java.lang.NullPointerException
at 
com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.referenceToNodeSet(BasisLibrary.java:998)
at webhelp.l10n$dot$language()
at webhelp.topLevel()
at webhelp.transform()
at 
com.sun.org.apache.xalan.internal.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:603)
at 
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:709)
... 21 more
-
java.lang.NullPointerException
at 
com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.referenceToNodeSet(BasisLibrary.java:998)
at webhelp.l10n$dot$language()
at webhelp.topLevel()
at webhelp.transform()
at 
com.sun.org.apache.xalan.internal.xsltc.runtime.AbstractTranslet.transform(AbstractTranslet.java:603)
at 
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:709)
at 
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313)
at 
org.apache.tools.ant.taskdefs.optional.TraXLiaison.transform(TraXLiaison.java:194)
at 
org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:852)
at 
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:388)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.

Re: [docbook-apps] Error messages when building webhelp

[Frank Arensmeier]

Thank you David. I'll try with the snapshot build in stead.
/frank


7 feb 2012 kl. 16.19 skrev David Cramer:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi Frank,
> It looks like ant is using xalan. Rather than debugging this, however,
> I'd suggest starting with the snapshot build. It contains many
> improvements anyway and will be part of a forthcoming release of the
> docbook xsls. If you still have error messages from it, we can start
> debugging from there.
> 
> Note: there are a few new properties in the build.properties files to
> set (i.e. jars to point to) that aren't mentioned in the doc yet, so
> do take a look at that.
> 
> David
> 
> On 02/07/2012 07:32 AM, Frank Arensmeier wrote:
>> Hello all.
>> 
>> I am trying to build webhelp but keep getting error messages. Not
>> even the webhelp test build does it's job. Any idea what is going
>> on here? The docbook stylesheets are 1.76.1 and saxon 6.5.5 is
>> installed as it should. Running ant with the "noclasspath" option
>> does not help (as pointed out here
>> http://docbook.sourceforge.net/release/xsl/current/webhelp/docs/content/ch02s01.html).
>> Building webhelp fails with the following output:
>> 
>> Buildfile:
>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/build.xml
>> 
>> validate:
>> 
>> clean: [delete] Deleting directory
>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/test-ouput
>> 
>> chunk: [mkdir] Created dir:
>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/test-ouput
>> 
>> 
> [xslt] Processing
> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/docsrc/readme.xml
> to
> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/test-ouput/dummy.html
>> [xslt] Loading stylesheet
>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/xsl/webhelp.xsl
>> 
>> 
> [xslt] : Warning!
> file:/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/xhtml/autoidx.xsl:
> line 502: Attribute 'href' outside of element.
>> [xslt] : Warning!
>> file:/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/xhtml/lists.xsl:
>> line 728: Attribute 'type' outside of element. [...] [xslt] :
>> Error! null [xslt] Failed to process
>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/docsrc/readme.xml
>> 
>> BUILD FAILED 
>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/build.xml:34:
>> javax.xml.transform.TransformerException:
>> java.lang.NullPointerException at
>> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:716)
>> 
>> 
> at
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313)
>> at
>> org.apache.tools.ant.taskdefs.optional.TraXLiaison.transform(TraXLiaison.java:194)
>> 
>> 
> at org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:852)
>> at
>> org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:388)
>> 
>> 
> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>> 
>> 
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>> at java.lang.reflect.Method.invoke(Method.java:597) at
>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>> 
>> 
> at org.apache.tools.ant.Task.perform(Task.java:348)
>> at org.apache.tools.ant.Target.execute(Target.java:390) at
>> org.apache.tools.ant.Target.performTasks(Target.java:411) at
>> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>> 
>> 
> at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
>> at
>> org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
>> 
>> 
> at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
>> at org.apache.tools.ant.Main.runBuild(Main.java:809) at
>> org.apache.tools.ant.Main.startAnt(Main.java:217) at
>> org.apache.tools.ant.launch.Launcher.run(Launcher.java:280) at
>> org.apache.tools.ant.launch.Launcher.main(Launcher.java:109) Caused
>> by: java.lang.NullPointerException at
>> com.sun.org.apache.xalan.internal.xsltc.runtime.BasisLibrary.referenceToNodeSet(BasisLibrary.java:998)
>> 
>> 
> at webhelp.l10n$dot$language()
>> at webhelp.topLevel() at webhelp.transform() at
&

Re: [docbook-apps] DocBook, visualized as a treemap

[Frank Arensmeier]

Hi Tim.

You might take a look at diffxml. http://diffxml.sourceforge.net/ I think it 
looks promising. But I am not sure if there is some kind of html visualizer 
available.

cheers,
/frank

 
9 feb 2012 kl. 16.22 skrev Tim Arnold:

> hi,
> I wonder if there is already a tool out there to visualize a DocBook
> document as a treemap.
> 
> I came across some interesting research on how one can visualize
> changes between two treemaps that would be useful to monitor changes
> in a DocBook document: create the treemap today, create a new one
> tomorrow, compare the two with a layout distance function which
> creates a new treemap that shows changes by differences in contrast.
> And there you have it, a simple graphic to give a high-level view of
> the differences between documents or versions of a document.
> 
> So, before I go inventing this wheel, I wondered if someone already
> has such a project. If not, does anyone see the benefit or perhaps
> another way to get the same basic result?
> 
> thanks,
> --Tim Arnold
> 
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
> 


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

[docbook-apps] Controlling page break after toc

[Frank Arensmeier]

Hi there.

I am generating double sided PDF files with the latest docbook xsl stylesheets. 
Everything is working just fine besides one thing. I'd like to get rid of the 
blank page that is inserted after the table of contents. How can this be 
accomplished? I can not find anything "suspicious" in the 
fo/titlepage.templates.xml file that could be tweaked.

Thank you,
/frank
-
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] valign on inlinemediaobject no effect?

[Frank Arensmeier]

Hi there.

I am trying to align some inline graphics nicely with the surrounding text. 
But, setting the attribute valign on the imagedata element has no effect. The 
image stays aligned relative to the text top whatsoever. By looking at the fo 
output from the transformation process, I can see that the attribute valign is 
reflected to the fo attribute "display-align" on the "external-graphic" 
element. If I change that to "alignment-baseline" and set the value to 
"middle", everything shows up fine. Am I missing something? Shouldn't the 
stylesheet distinguish between valign on inlinemediaobjects and mediaobjects 
and "translate" that attribute to "alignment-baseline" on inlinemediaobjects 
and "display-align" on mediaobjects?

Regards,
/frank
-
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] valign on inlinemediaobject no effect?

[Frank Arensmeier]

I've downloaded and installed the latest XSL snapshot. Everything is working 
fine now.

Thank you!
/frank


18 feb 2012 kl. 00.50 skrev Bob Stayton:

> I checked in a fix for this problem.  You can confirm the correct behavior if 
> you download the latest XSL snapshot.
> 
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
> 
> 
> - Original Message - From: "Frank Arensmeier" 
> To: "Docbook Apps Help list" 
> Sent: Monday, February 13, 2012 4:51 AM
> Subject: [docbook-apps] valign on inlinemediaobject no effect?
> 
> 
> Hi there.
> 
> I am trying to align some inline graphics nicely with the surrounding text. 
> But, setting the attribute valign on the imagedata element has no effect. The 
> image stays aligned relative to the text top whatsoever. By looking at the fo 
> output from the transformation process, I can see that the attribute valign 
> is reflected to the fo attribute "display-align" on the "external-graphic" 
> element. If I change that to "alignment-baseline" and set the value to 
> "middle", everything shows up fine. Am I missing something? Shouldn't the 
> stylesheet distinguish between valign on inlinemediaobjects and mediaobjects 
> and "translate" that attribute to "alignment-baseline" on inlinemediaobjects 
> and "display-align" on mediaobjects?
> 
> Regards,
> /frank
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
> 
> 
> 


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook-apps] Error messages when building webhelp

[Frank Arensmeier]

Finally I had the chance to test your suggestion with the latest DocBook XSL 
snapshot. But the result is the same. Building webhelp fails with a bunch of 
errors. Surprisingly, webhelp builds just fine using the 1.76.0 stylesheets 
(everything else is the same, xalan, ant, xslproc). Something has changed. But 
what?

/frank


7 feb 2012 kl. 16.43 skrev Frank Arensmeier:

> Thank you David. I'll try with the snapshot build in stead.
> /frank
> 
> 
> 7 feb 2012 kl. 16.19 skrev David Cramer:
> 
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>> 
>> Hi Frank,
>> It looks like ant is using xalan. Rather than debugging this, however,
>> I'd suggest starting with the snapshot build. It contains many
>> improvements anyway and will be part of a forthcoming release of the
>> docbook xsls. If you still have error messages from it, we can start
>> debugging from there.
>> 
>> Note: there are a few new properties in the build.properties files to
>> set (i.e. jars to point to) that aren't mentioned in the doc yet, so
>> do take a look at that.
>> 
>> David
>> 
>> On 02/07/2012 07:32 AM, Frank Arensmeier wrote:
>>> Hello all.
>>> 
>>> I am trying to build webhelp but keep getting error messages. Not
>>> even the webhelp test build does it's job. Any idea what is going
>>> on here? The docbook stylesheets are 1.76.1 and saxon 6.5.5 is
>>> installed as it should. Running ant with the "noclasspath" option
>>> does not help (as pointed out here
>>> http://docbook.sourceforge.net/release/xsl/current/webhelp/docs/content/ch02s01.html).
>>> Building webhelp fails with the following output:
>>> 
>>> Buildfile:
>>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/build.xml
>>> 
>>> validate:
>>> 
>>> clean: [delete] Deleting directory
>>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/test-ouput
>>> 
>>> chunk: [mkdir] Created dir:
>>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/test-ouput
>>> 
>>> 
>> [xslt] Processing
>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/docsrc/readme.xml
>> to
>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/test-ouput/dummy.html
>>> [xslt] Loading stylesheet
>>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/xsl/webhelp.xsl
>>> 
>>> 
>> [xslt] : Warning!
>> file:/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/xhtml/autoidx.xsl:
>> line 502: Attribute 'href' outside of element.
>>> [xslt] : Warning!
>>> file:/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/xhtml/lists.xsl:
>>> line 728: Attribute 'type' outside of element. [...] [xslt] :
>>> Error! null [xslt] Failed to process
>>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/docsrc/readme.xml
>>> 
>>> BUILD FAILED 
>>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/build.xml:34:
>>> javax.xml.transform.TransformerException:
>>> java.lang.NullPointerException at
>>> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:716)
>>> 
>>> 
>> at
>> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(TransformerImpl.java:313)
>>> at
>>> org.apache.tools.ant.taskdefs.optional.TraXLiaison.transform(TraXLiaison.java:194)
>>> 
>>> 
>> at org.apache.tools.ant.taskdefs.XSLTProcess.process(XSLTProcess.java:852)
>>> at
>>> org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:388)
>>> 
>>> 
>> at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>> 
>>> 
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>> at java.lang.reflect.Method.invoke(Method.java:597) at
>>> org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
>>> 
>>> 
>> at org.apache.tools.ant.Task.perform(Task.java:348)
>>> at org.apache.tools.ant.Target.execute(Target.java:390) at
>>> org.apache.tools.ant.Target.performTasks(Target.java:411) at
>>> org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
>>> 
>>> 
>> at org.apache.tools.ant.Project.executeTarget(Project.java:13

Re: [docbook-apps] Error messages when building webhelp

[Frank Arensmeier]

Thank you for this eye-opener! The path to saxon was not correct. My fault.

Sorry for the noise.
/frank

1 mar 2012 kl. 16.30 skrev David Cramer:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi Frank,
> 
> Can you confirm that you've modified build.properties so that the
> appropriate properties point to the needed jars:
> 
> # Modify the follosing so that they point to your local
> # copy of the jars indicated:
> # * Saxon 6.5 jar
> # * Xerces 2: xercesImpl.jar
> # * xml-commons: xml-apis.jar
> xslt-processor-classpath=/usr/share/java/saxon-6.5.5.jar
> xercesImpl.jar=/usr/share/java/xercesImpl.jar
> xml-apis.jar=/usr/share/java/xml-apis.jar
> 
> David
> 
> On 03/01/2012 08:37 AM, Frank Arensmeier wrote:
>> Finally I had the chance to test your suggestion with the latest
>> DocBook XSL snapshot. But the result is the same. Building webhelp
>> fails with a bunch of errors. Surprisingly, webhelp builds just
>> fine using the 1.76.0 stylesheets (everything else is the same,
>> xalan, ant, xslproc). Something has changed. But what?
>> 
>> /frank
>> 
>> 
>> 7 feb 2012 kl. 16.43 skrev Frank Arensmeier:
>> 
>>> Thank you David. I'll try with the snapshot build in stead. 
>>> /frank
>>> 
>>> 
>>> 7 feb 2012 kl. 16.19 skrev David Cramer:
>>> 
>> Hi Frank, It looks like ant is using xalan. Rather than debugging
>> this, however, I'd suggest starting with the snapshot build. It
>> contains many improvements anyway and will be part of a forthcoming
>> release of the docbook xsls. If you still have error messages from
>> it, we can start debugging from there.
>> 
>> Note: there are a few new properties in the build.properties files
>> to set (i.e. jars to point to) that aren't mentioned in the doc
>> yet, so do take a look at that.
>> 
>> David
>> 
>> On 02/07/2012 07:32 AM, Frank Arensmeier wrote:
>>>>>> Hello all.
>>>>>> 
>>>>>> I am trying to build webhelp but keep getting error
>>>>>> messages. Not even the webhelp test build does it's job.
>>>>>> Any idea what is going on here? The docbook stylesheets are
>>>>>> 1.76.1 and saxon 6.5.5 is installed as it should. Running
>>>>>> ant with the "noclasspath" option does not help (as pointed
>>>>>> out here 
>>>>>> http://docbook.sourceforge.net/release/xsl/current/webhelp/docs/content/ch02s01.html).
>>>>>> 
>>>>>> 
> Building webhelp fails with the following output:
>>>>>> 
>>>>>> Buildfile: 
>>>>>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/build.xml
>>>>>> 
>>>>>> 
>>>>>> 
> validate:
>>>>>> 
>>>>>> clean: [delete] Deleting directory 
>>>>>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/test-ouput
>>>>>> 
>>>>>> 
>>>>>> 
> chunk: [mkdir] Created dir:
>>>>>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/test-ouput
>>>>>> 
>>>>>> 
>> 
>>>>>> 
> [xslt] Processing
>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/docsrc/readme.xml
>> 
>> 
> to
>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/test-ouput/dummy.html
>>>>>> 
>> 
> [xslt] Loading stylesheet
>>>>>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/xsl/webhelp.xsl
>>>>>> 
>>>>>> 
>> 
>>>>>> 
> [xslt] : Warning!
>> file:/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/xhtml/autoidx.xsl:
>> 
>> 
> line 502: Attribute 'href' outside of element.
>>>>>> [xslt] : Warning! 
>>>>>> file:/Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/xhtml/lists.xsl:
>>>>>> 
>>>>>> 
> line 728: Attribute 'type' outside of element. [...] [xslt] :
>>>>>> Error! null [xslt] Failed to process 
>>>>>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/docsrc/readme.xml
>>>>>> 
>>>>>> 
>>>>>> 
> BUILD FAILED
>>>>>> /Users/brillo/Sites/tecdoc2/lib/docbook-xsl-1.76.1/webhelp/build.xml:34:
>>>>>> 
>>>>>> 
> javax.xml.transform.TransformerException:
>>>>

[docbook-apps] section element only allows one subtitle, why?

[Frank Arensmeier]

Hi.

Just a quick question. I am working with simplified docbook where the element 
"article" is the top level element. Mostly because the "normal" set of docbook 
elements includes a large number of elements that are totally unnecessary for 
kinds of documentation other than e.g. software documentation. So, I feel that 
simplified docbook is more than enough.

My question is why does the "section" element only allows one single subtitle 
element? Are there any particular reasons for this? Documents with a rather 
simple structure (title, subtitle, section , title, subtitle, para, subtitle, 
para) are easily being cluttered with nested sections (on places where a simple 
subtitle would be so much more handy). Or am I missing something?

Cheers
/frank


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

[docbook-apps] docbook stylesheets 1.77.0 - webhelp

[Frank Arensmeier]

Dear all.

Yesterday I tried to build webhelp from the new stylesheets 1.77.0 There seems 
to be a bug in the file "build.xml". Around line 30 it says:

[...]






[...]

Notice the relative path "../profiling/profile.xsl". This causes an error if 
the custom build file is not in the same directory as the build file from the 
source distribution. Changing that attribute to something like 
"${extensions.dir}/../profiling/profile.xsl" worked for me.

/frank
-
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] Background for programlisting

[Frank Arensmeier]

15 jun 2012 kl. 01.03 skrev Lars Vogel:

> Hello,
> 
> I wanted to add a background color to my programming listings and
> found an old post from Bob in which he suggested to add the following
> to the customizing layer:
> 
> 
>   border-color="thin black ridge"
>   background-color="silver"
> 
> 
> If I do this, I get an error:
> 
>[xslt] Unknown file:61:9: Fatal Error! Error reported by XML
> parser Cause: org.xml.sax.SAXParseException; lineNumber: 61;
> columnNumber: 9; expected '"' or "'" (found "b")
> [xslt] Failed to process null
> 
> BUILD FAILED
> /home/vogella/workspace/docu/de.vogella.publishing/buildpdf.xml:294:
> javax.xml.transform.TransformerConfigurationException: Failed to parse
> stylesheet
> 
> Anyone knows what I'm doing incorrect?
> 
> Best regards, Lars
> 
> -- 
> Lars

Hi.

Maybe it is the attribute value you have in "border-color"? "thin black ridge" 
is not a colour. Either you change the attribute to "border" or you change the 
value to a valid colour value.

/frank


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

[Frank Arensmeier]

> 7 dec 2013 kl. 21:35 skrev Jirka Kosek :
> 
>> On 6.12.2013 22:53, Norman Walsh wrote:
>> It appears that modern systems do this in the JavaScript layer on the
>> client. They also use tables to render line numbers.
>> 
>> I'm tempted to move in this direction. Comments?
> 
> I have used both approaches. Problem with Javascript one is that it
> doesn't work for print (neither of XSL-FO, HTML/CSS composition egines
> support Javascript) and sometimes introduces delay in rendering. On the
> other hand Javascript syntax highlighters are in a more active
> development then highlighting extensions for XSLT.
> 
>> As long as I'm airing dirty laundry, I'm also tempted to abandon the
>> XSL stylesheets and work instead on a purpose-built HTML+CSS rendering
>> for printing.
> 
> Do you mean completely removing existing incomplete fo code from project?
> 
> I think that we can keep code here in the case someone will have time
> and interest to improve it further.
> 
> With HTML+CSS composition there is one big problem -- there is (at least
> to my knowledge) no free renderer, I'm aware only of PrinceXML and
> AntennaHouse.

Actually, there is a renderer that is able to generate PDF from HTML with 
really good results. Wkhtmltopdf (https://code.google.com/p/wkhtmltopdf/). It's 
basically a wrapper for the WebKit engine used by safari, chrome etc. Not sure 
if the WebKit they are using right now is bleeding edge. Anyway, it produces 
quite decent PDFs. 

I would definitely vote for the HTML route. Styling printable output with CSS 
would make the whole development process much more easier and less time 
consuming than it is today with XSL.

/frank

> 
> But HTML+CSS printing got some traction recently, so it is wortwhile to
> explore this area.
> 
>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
> --
> 

-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook-apps] Re: Syntax highlighting

[Frank Arensmeier]

10 dec 2013 kl. 07:59 skrev davep :

> On 09/12/13 16:09, Norman Walsh wrote:
> 
>>> I can see you getting 80% with html and CSS...
>>> My penneth says you'll fall over on the 20% so I'm -1 on this.
>>>   Do you believe you can do it?
>>> What of re-ordering, toc etc?
>> 
>> Oh, you'd need a "for print" HTML stylesheet. There's lots of things
>> that CSS can't do. But I still think that would be easier for most
>> people than dealing with XSL FO.
> 
> 
> I have to agree with you Norm. I still think there will be
> things that (today) CSS can't do? That should change over (guess)
> the next 3-4 years?
>  What workflow would it be then?
> XSLT to obtain the selected / added /re-organised output, then CSS to style 
> it?

I'd like to chime in here for a second or two. I think it is also important to 
ask in which direction Docbook (and other XML standards too for that matter) 
need to evolve in the near future. If you look at marketshare for desktop 
computer vs mobile devices, one will realise that the number of mobile devices 
has exploded the last couple of years. And this trend will definitely continue 
over the next decade or two. On the other hand, number of desktop computers has 
decreased tremendously. 

Where does DB come into this picture? Personally, I think that HTML output will 
(and should) become more important to focus on than anything else. It is not 
XSL/FO that gets attention today, it's CSS. In my opinion, XSL/FO is a dead 
end. It has a rather steep learning curve, there are only three production 
ready formatters available and I cannot see any signs of increased effort to 
develop XSL/FO any further. I've already customers that are more and more 
reluctant to pay for XSL/FO development. Partly because these customers don't 
want to be forced into one single technology and/or one single developer.

If Docbook would switch to CSS based PDF generation, and you are able to 
achieve 80% of all the features that come with the PDF format, that's 
absolutely fine with me. I am convinced that it's only a matter of time before 
we reach those remaining 20%.

/frank

ps. sorry for my english. I'm not a native english speaker… ds.

> regards
> 
> -- 
> Dave Pawson
> XSLT XSL-FO FAQ.
> http://www.dpawson.co.uk
> 
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
> 


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook-apps] Table Center

[Frank Arensmeier]

26 mar 2014 kl. 14:09 skrev Rogério Rosa :

> Hello,
> 
> I am having a hard time to centre a table when the width is less than 100%. 
> There is any way to centre it?
> 
> Thanks in advance.
> Best Regards,

Hi!

I suppose you are talking about PDF output, right? My understanding is that 
this depends on the FO engine you are using. Both RenderX and FOP need some 
tweaks whereas AH Formatter has support for center aligned tables out of the 
box. You should read about table alignment here:

http://www.sagehill.net/docbookxsl/TableAlignment.html

Cheers,
/frank

> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
> 


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook-apps] Table Center

[Frank Arensmeier]

26 mar 2014 kl. 15:36 skrev Rogério Rosa :

> Thanks,
> 
> However I need to ask if that works with apache fop ? I am getting some 
> strange behaviour, the table is centred but
> it shrinks in comparison with the desired size. 
> 
> Any ideias ?
> 

Would it be possible for you to show us the relevant XSL:FO code for the table? 
Maybe there is some unwanted space applied on the surrounding table cell?

Cheers,
/frank

> Thanks in advance.
> Best Regards,
> 
> On Mar 26, 2014, at 2:15 PM, deannel...@aol.com wrote:
> 
>> Here is what I use in my stylesheets.
>>  
>> Regards
>> Dean Nelson
>>  
>>  
>>  
>>  
>>   
>> 
>>  
>> 
>> 
>>
>>
>> 
>>
>>   Table width set to > select="@width"> 
>> 
>> 
>>   
>>   Table width NOT set.
>> 
>>
>> 
>> 
>>   
>> 
>>   
>> 
>>   
>> 
>>   
>> 
>>   
>> 
>>  
>>   
>>  
>> 
>>  
>> 
>>
>> 
>>
>> 
>>
>>   Table width set to > select="@width"> 
>> 
>> 
>>   
>>   Table width NOT set.
>> 
>>
>> 
>>   
>> 
>>   
>> 
>>   
>> 
>>   
>> 
>>   
>> 
>>  
>>   
>>  
>> 
>>
>> 
>>   
>> 
>> 
>>  
>>  
>>  
>> In a message dated 3/26/2014 7:05:43 A.M. Pacific Daylight Time, 
>> farensme...@gmail.com writes:
>> 26 mar 2014 kl. 14:09 skrev Rogério Rosa :
>> 
>> > Hello,
>> > 
>> > I am having a hard time to centre a table when the width is less than 
>> > 100%. There is any way to centre it?
>> > 
>> > Thanks in advance.
>> > Best Regards,
>> 
>> Hi!
>> 
>> I suppose you are talking about PDF output, right? My understanding is that 
>> this depends on the FO engine you are using. Both RenderX and FOP need some 
>> tweaks whereas AH Formatter has support for center aligned tables out of the 
>> box. You should read about table alignment here:
>> 
>> http://www.sagehill.net/docbookxsl/TableAlignment.html
>> 
>> Cheers,
>> /frank
>> 
>> > -
>> > To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
>> > For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>> > 
>> 
>> 
>> -
>> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
>> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org




-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook-apps] Producing interactive PDF forms from DocBook content with XEP

[Frank Arensmeier]

9 apr 2014 kl. 11:01 skrev Bergfrid Skaara :

> We have a large amount of PDFs generated from modular and singlesourced 
> DocBook XML, and need to expand that portfolio with ineractive PDF forms.
> 
> All trails lead back to http://www.renderx.com/reference.html#PDF%20Forms, 
> but they do not say what we need to do in our DocBook XML and XSL files to 
> achieve this.
> 
> Do I need to become an XSL-FO expert and write the .fo file by hand?
> Do I need to rewrite the XSL to pull something out of the existing XML files? 
> And do I need to add special markup in the XML for this?

Hello Bergfrid!

Since XEP is not explicitly made for Docbook, I doubt you’ll find detailed 
instructions on the RenderX site on this matter. Besides that, form field 
generation for PDF output is not part of the ”out-of-the-box” Docbook 
stylesheets. It will definitely require some customisation of your stylesheets 
in order to produce usable FO output for XEP.

When it comes to your question about special XML markup, that depends heavily 
on what you want to achieve – are we talking about just a few elements that 
should be transformed into editable form fields in the PDF? Are those elements 
always of the same type (e.g. all email elements)? Do you want the author to be 
able to determine which element to ”convert” to an editable input field? So, if 
your XSL-skills are limited, you'll probably need some help on this. You are 
welcome to drop me a line off-list.

Hälsningar,
/frank

Re: [docbook-apps] Custom colors for admonitions

[Frank Arensmeier]

Hi Brett!

Which version of the stylesheets are you using? There is a version that uses a 
namespace and one that doesn’t.

/frank

29 apr 2014 kl. 10:24 skrev Brett Davis :

> Hi Dean,
> 
> Thanks for the speedy answer. Unfortunately, that doesn't let me give
> each admonition a different color either.
> 
> The part that's not working for me is the "choose" block, where a
> warning should have red lines and a note should have blue lines.
> Whether I use test="self::d:warning" or
> test="ancestor-or-self::warning", all admonitions end up in my PDF as
> the default color, which is black.
> 
> 
> Thanks,
> Brett
> 
> On 29 April 2014 15:51,   wrote:
>> Brett,
>> The simple answer is to add
>> 1pt solid blue
>> or a variation of it.
>> 
>> However, I have found that you will need to also deal with the title box as
>> well or it will look a bit weird. So below you will see my admonition
>> section that you should be able to modify to suit your needs.
>> 
>> Regards
>> Dean Nelson
>> 
>> 
>> 
>> http://www.w3.org/1999/XSL/Transform";
>> version="1.0"
>>xmlns:fo="http://www.w3.org/1999/XSL/Format"; >
>> 
>> 
>>
>> 
>>
>>
>>
>>> select="'http://docbook.sourceforge.net/release/xsl/current/images/'"/>
>> 
>>
>>
>>
>>
>>>> #FF
>>>> #FF
>>> test="ancestor-or-self::important">#B5FFB5
>>>> #FAFA8C
>>>> #FFADAD
>>#00
>>
>>
>>> name="keep-together.within-column">always
>>5pt
>>-5pt
>>1pt solid blue
>> 
>> 
>>
>>> name="keep-together.within-column">always
>>#E0E0E0
>>left
>>5pt
>>  
>>1pt solid blue
>>1pt solid blue
>>1pt solid blue
>>> 
>> 
>> 
>> 
>> 
>> In a message dated 4/28/2014 7:24:58 P.M. Pacific Daylight Time,
>> brett...@gmail.com writes:
>> 
>> Hi,
>> 
>> I'd like to give each admonition a border of its own color. I found a
>> question where using a "choose" block was suggested when customizing
>> the attribute-set for "graphical.admonition.properties". I've tried
>> that, and while I can change the attributes in the attribute-set, my
>> tests in the "choose" block never match any admonitions. They all get
>> the value given in the "otherwise" block. Is there something I should
>> be using instead of test="self::d:warning", or have I screwed up
>> somewhere else?
>> 
>> I'm using DocBook 5.0, libxslt-1.1.26.win32, fop-1.1 on Windows Vista
>> 64 bit Ultimate.
>> 
>> 
>> Here's testbook.xml:
>> 
>> 
>> http://docbook.org/ns/docbook"; version="5.0">
>>A Small Example
>> 
>>
>>If everything goes as planned, the warning below will
>> have a red line above and below it, and the note will have blue lines.
>> If not, they'll both have black lines.
>> 
>>
>>This is a warning!
>>
>> 
>>
>>This is just a note.
>>
>> 
>>Ok, black lines it is.
>>
>> 
>> 
>> 
>> Here's testStylesheet.xsl:
>> 
>> 
>> http://www.w3.org/1999/XSL/Transform";
>> xmlns:fo="http://www.w3.org/1999/XSL/Format";
>> xmlns:d="http://docbook/org/ns/docbook"; version="1.0">
>>
>> 
>>A4
>> 
>>
>>
>>images/
>>.png
>> 
>>
>>
>>
>>red
>>blue
>>black
>>
>>
>>1pt solid
>>1pt solid
>>
>> 
>> 
>> 
>> I'm currently writing in Notepad++ and building using a .bat file:
>> 
>> D:\sdk\docbook\libxslt-1.1.26.win32\bin\xsltproc.exe --output
>> testbook.fo testStylesheet.xsl testbook.xml
>> 
>> D:\sdk\docbook\fop-1.1\fop.bat -fo testbook.fo -pdf testbook.pdf
>> 
>> 
>> I'm new to DocBook, so I'm probably making a stupid mistake somewhere.
>> Any help would be much appreciated.
>> 
>> Thanks,
>> Brett
>> 
>> -
>> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
>> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>> 
> 
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
> 


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

[docbook-apps] Problem with http://www.sagehill.net

[Frank Arensmeier]

Hi!

I’m getting a ”Permanently moved” message when trying to access 
http://www.sagehill.net

Is this site gone?

Cheers,
/frank
-
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] Problem with http://www.sagehill.net

[Frank Arensmeier]

10 jun 2014 kl. 11:48 skrev Stefan Hinz :

> Maybe a temporary failure? I can access it fine, including 
> http://www.sagehill.net/docbookxsl/index.html. I get a 404 
> forhttp://www.sagehill.net/personal/ElectricRabbit.htm, but I can live with 
> that. :-)

Hi Stefan!

Thank you for your quick test. The page is loading just fine on my remote 
dev-box. So, it seems like a DNS related issue with my DNS provider. 

Greetings from Sweden, sunshine and 30 degrees! Beat that if you can...
/frank
-
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] Simplified DocBook RelaxNG schema not valid?

[Frank Arensmeier]

Hi there!

For a project I am working on, I did a couple of tests with the Simplified 
DocBook schema. The definition I downloaded was 5.1CR3. When I open that schema 
in Oxygen I see a couple of validation errors:

System ID: /Users/brillo/Downloads/sdocbook.rng
Description: multiple definitions of start without "combine" attribute
Start location: 290:11

System ID: /Users/brillo/Downloads/sdocbook.rng
Description: multiple definitions of start without "combine" attribute
Start location: 2390:11

System ID: /Users/brillo/Downloads/sdocbook.rng
Description: multiple definitions of start without "combine" attribute
Start location: 6644:11

System ID: /Users/brillo/Downloads/sdocbook.rng
Description: multiple definitions of "db.admonition.blocks" without "combine" 
attribute
Start location: 6736:40

System ID: /Users/brillo/Downloads/sdocbook.rng
Description: multiple definitions of "db.os.inlines" without "combine" attribute
Start location: 6826:33

System ID: /Users/brillo/Downloads/sdocbook.rng
Description: multiple definitions of "db.programming.inlines" without "combine" 
attribute
Start location: 6835:42

System ID: /Users/brillo/Downloads/sdocbook.rng
Description: multiple definitions of "db.markup.inlines" without "combine" 
attribute
Start location: 6853:37

Most of these errors seem to be caused by the fact that there are some 
duplicates of element definitions. Removing those duplicates however does not 
make Oxygen happy. Instead, it says: found element matching the prohibited path 
start//empty in the simplified XML form of the schema[…].

What is going on here? Can this be fixed? Shall I file a bug report somewhere? 
Do pigs fly?
Thanks!

/frank

Frank Arensmeier
farensme...@gmail.com
-
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] Time for new DocBook Stylesheet Release?

[Frank Arensmeier]

Hi!

I'd be interested to know what to expect from these updates to come too –  
besides bug fixes I mean. Are there any plans to implement some new and 
exciting output targets? We have been building a CCMS system with Docbook as 
its backbone. So for my company it would be very important to know if Docbook 
is still alive and kicking. 

/frank
http://www.paligo.se

> 30 jun 2015 kl. 19:11 skrev Bob Stayton :
> 
> Hi Thomas,
> Has it really been two years?!  I'll start the process to produce a new 
> DocBook XSL release, and then work with the other developers to carry out the 
> transition of the build to Ant, hopefully simplifying the rather arcane 
> process.
> 
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
> 
>> On 6/29/2015 11:53 PM, Thomas Schraitle wrote:
>> Hi,
>> 
>> in the last years I've observed a trend, that the DocBook stylesheets
>> don't publish new releases very often.
>> 
>> The last release of the stylesheets is from 2013 which is two years old!
>> Am I'm the only one who need and wait desperately for a new release? ;))
>> 
>> I know, you are all busy with other things. However, I fear, this makes
>> the wrong impression that this project is dead. I hope this is not.
>> 
>> After two years I would love to see a new release. Maybe with a release
>> cycle which counts in months and not years?
>> 
>> Any plans? Thoughts? :)
>> 
> 
> -
> 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] Time for new DocBook Stylesheet Release?

[Frank Arensmeier]

Hi!

Thanks for asking. A couple of things pop up in my mind. HTML5 output based on 
Bootstrap, UI kit or Foundation (or whatever modern CSS framework you prefer). 
Or why not PhoneGap-ready output. I think in the long run, HTML output targeted 
for mobile devices would be one very exciting and useful feature for Docbook 
XSLT. Just have a look on sites like https://readthedocs.org or 
https://stripe.com/docs/api. I’m not saying that those sites are the mother of 
all things. But I am convinced that output like this would make Docbook more 
future-proof than it seems to be right now.

/frank

> 1 jul 2015 kl. 11:56 skrev Peter Desjardins :
> 
> Do you have any output targets in mind? What would be interesting to you?
> 
> Peter
> 
> On Tue, Jun 30, 2015 at 4:18 PM, Frank Arensmeier  
> wrote:
>> Hi!
>> 
>> I'd be interested to know what to expect from these updates to come too –
>> besides bug fixes I mean. Are there any plans to implement some new and
>> exciting output targets? We have been building a CCMS system with Docbook as
>> its backbone. So for my company it would be very important to know if
>> Docbook is still alive and kicking.
>> 
>> /frank
>> http://www.paligo.se
>> 
>> 30 jun 2015 kl. 19:11 skrev Bob Stayton :
>> 
>> Hi Thomas,
>> Has it really been two years?!  I'll start the process to produce a new
>> DocBook XSL release, and then work with the other developers to carry out
>> the transition of the build to Ant, hopefully simplifying the rather arcane
>> process.
>> 
>> Bob Stayton
>> Sagehill Enterprises
>> b...@sagehill.net
>> 
>> On 6/29/2015 11:53 PM, Thomas Schraitle wrote:
>> 
>> Hi,
>> 
>> 
>> in the last years I've observed a trend, that the DocBook stylesheets
>> 
>> don't publish new releases very often.
>> 
>> 
>> The last release of the stylesheets is from 2013 which is two years old!
>> 
>> Am I'm the only one who need and wait desperately for a new release? ;))
>> 
>> 
>> I know, you are all busy with other things. However, I fear, this makes
>> 
>> the wrong impression that this project is dead. I hope this is not.
>> 
>> 
>> After two years I would love to see a new release. Maybe with a release
>> 
>> cycle which counts in months and not years?
>> 
>> 
>> Any plans? Thoughts? :)
>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
>> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>> 


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

Re: [docbook-apps] should become in another book

[Frank Arensmeier]

Hi there!

There is probably some XLST foo out there that does what you want. I’d like to 
suggest an other approach. Have a look at "Xpointers" for the x:include 
element. The attribute "xpointer" on that element defines an xpath expression 
(kind of) that is used to select only parts of the document you want to include.

http://www.sagehill.net/docbookxsl/ModularDoc.html#UsingXinclude 


See e.g. "Selecting part of a file". However, your tool chain must support 
xpointers (not sure if xproc has suport for the full power of xpointers).

Hope this helps!

Regards
/frank 
 
> 19 aug 2015 kl. 14:21 skrev Lars Vogel :
> 
> Hi,
> 
> I use xinclude to include certain documents in different books. In a certain 
> context I want to use it as part in another as appendix.
> 
> I tried to remove the top level node with the following to my customization 
> layer:
> 
> 
>   
>   
>   
> 
> And include it into the books like this:
> 
> 
>   Gerrit code reviews with Eclipse
>   http://www.w3.org/2001/XInclude 
> " href="820_gerrit.xml" />
> 
> 
> or 
> 
> 
>   Gerrit code reviews with Eclipse
>   http://www.w3.org/2001/XInclude 
> " href="820_gerrit.xml" />
> 
> 
> Unfortunately my customization removes not only the top level part element 
> but the whole part.
> 
> Is anyone aware of a nice trick to replace part in some books with appendix? 
> 
> Best regards, Lars
> 
> P.S. What I would like to have is the equivalent of the  node for 
> defining Android layouts, this node is only their to have a valid XML file, 
> but is removed during the include process.

Re: [docbook-apps] should become in another book

[Frank Arensmeier]

Just a quick heads-up. I just stumbled upon an old thread on this list dealing 
with more or less the same problem as you have.

http://comments.gmane.org/gmane.text.docbook.apps/29005 
<http://comments.gmane.org/gmane.text.docbook.apps/29005>

Maybe worth reading?
/frank 


> 19 aug 2015 kl. 15:20 skrev Lars Vogel :
> 
> Hi Frank,
> 
> thanks, xpointers sound very useful.
> 
> I tried it but my self-written xinclude Apache Ant task does not support 
> xpointers. Is anyone aware of an existing Ant xinclude task which has support 
> for xpointers?
> 
> Best regards, Lars
> 
> 2015-08-19 15:04 GMT+02:00 Frank Arensmeier  <mailto:farensme...@gmail.com>>:
> Hi there!
> 
> There is probably some XLST foo out there that does what you want. I’d like 
> to suggest an other approach. Have a look at "Xpointers" for the x:include 
> element. The attribute "xpointer" on that element defines an xpath expression 
> (kind of) that is used to select only parts of the document you want to 
> include.
> 
> http://www.sagehill.net/docbookxsl/ModularDoc.html#UsingXinclude 
> <http://www.sagehill.net/docbookxsl/ModularDoc.html#UsingXinclude>
> 
> See e.g. "Selecting part of a file". However, your tool chain must support 
> xpointers (not sure if xproc has suport for the full power of xpointers).
> 
> Hope this helps!
> 
> Regards
> /frank 
>  
>> 19 aug 2015 kl. 14:21 skrev Lars Vogel > <mailto:lars.vo...@gmail.com>>:
>> 
>> Hi,
>> 
>> I use xinclude to include certain documents in different books. In a certain 
>> context I want to use it as part in another as appendix.
>> 
>> I tried to remove the top level node with the following to my customization 
>> layer:
>> 
>> 
>>  
>>  
>>  
>> 
>> And include it into the books like this:
>> 
>> 
>>  Gerrit code reviews with Eclipse
>>  http://www.w3.org/2001/XInclude 
>> <http://www.w3.org/2001/XInclude>" href="820_gerrit.xml" />
>> 
>> 
>> or 
>> 
>> 
>>  Gerrit code reviews with Eclipse
>>  http://www.w3.org/2001/XInclude 
>> <http://www.w3.org/2001/XInclude>" href="820_gerrit.xml" />
>> 
>> 
>> Unfortunately my customization removes not only the top level part element 
>> but the whole part.
>> 
>> Is anyone aware of a nice trick to replace part in some books with appendix? 
>> 
>> Best regards, Lars
>> 
>> P.S. What I would like to have is the equivalent of the  node for 
>> defining Android layouts, this node is only their to have a valid XML file, 
>> but is removed during the include process.
> 
> 

[docbook-apps] Different style on even/odd page in PDF

[Frank Arensmeier]

Hi list!

I am wondering, is it possible to have different style attributes for titles 
depending on if the title appears on an even or odd page? Of course, for PDF 
output that is. Suppose I’d like to have my titles in green on even pages and 
in blue on odd pages.

Is that possible?

Thanks!
/frank
-
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] Different style on even/odd page in PDF

[Frank Arensmeier]

Hi Dick!

That was my suspicion already. I know that the header / footer use a parameter 
called "sequence" which denotes the page type (odd, even or blank). But, as you 
already pointed out, because titles (at least none-devision titles) are part of 
the content flow, you really cannot say where the titles are placed since this 
is known only at rending time. So even if it were possible to get that sequence 
parameter, it would be useless.

It’s a shame.

/frank

> 27 sep 2015 kl. 22:34 skrev XML Press :
> 
> Hi Frank, 
> 
> If you are talking about the header or footer, I think you can do that by 
> adjusting properties.
> 
> But if you're talking about regular titles, that may be harder. Only the 
> layout engine (fop or equivalent) knows whether something is on a left- or 
> right-hand page, and it only knows that when it is laying out pages, which is 
> after you have generated fo.
> 
> There may be markup you could include that would let you do something like 
> this (possibly a processor-specific directive for one of the proprietary fo 
> processors), but the last time I tried something similar, I couldn't find a 
> way to automatically do this. 
> 
> Dick Hamilton 
> 
> XML for Technical Communicators
> http://xmlpress.net
> 
>> On Sep 27, 2015, at 12:16, Frank Arensmeier  wrote:
>> 
>> Hi list!
>> 
>> I am wondering, is it possible to have different style attributes for titles 
>> depending on if the title appears on an even or odd page? Of course, for PDF 
>> output that is. Suppose I’d like to have my titles in green on even pages 
>> and in blue on odd pages.
>> 
>> Is that possible?
>> 
>> Thanks!
>> /frank
>> -----
>> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
>> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
>> 

Frank Arensmeier
farensme...@gmail.com

Jaktstigen 10
71832 Frövi
mobil 070-23 39 0 39
hem 0581-30 40 1





-
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] Chunking options for HTML output

[Frank Arensmeier]

Hi!

I am wondering. DITA has the attribute "chunk" that gives the user some control 
about how a topic/section is treated when it comes to output chunking. Setting 
that attribute to "to-content", the topic (including its children) is "… 
rendered as a single chunk of content". Is there something similar in DocBook? 
I know that I can control the chunking level – but that’s a different story. I 
need a more fine-grain control for the chunking mechanism. Could this be 
achieved in a customisation? Which "key" stylesheets in DocBook XSLT would be 
promising candidates to look at?

Thank you!
/frank
-
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] Chunking options for HTML output

[Frank Arensmeier]

Hi!

Thomas and Bob, thank you for pointing me in the right direction. I’ll give it 
a try.

/frank

Frank Arensmeier
Paligo - The truly user-friendly CMS for technical documentation
www.paligo.se

> 18 nov 2015 kl. 23:31 skrev Bob Stayton :
> 
> Hi Frank,
> I have some experience with customizing chunking in the stylesheet. Many of 
> the features of DocBook XSL were designed to be easily customized, but 
> chunking isn't one of them.  So it is possible, but there are a lot of 
> details that must be attended to. One of those details is navigation to Next 
> and Previous, which is altered when you change chunking behavior.
> 
> There is a section in my online book on customizing chunking, including a 
> section on "How chunking works", but it is not a complete guide.  It does 
> point out the files and templates that will need to be looked at.
> 
> http://www.sagehill.net/docbookxsl/ChunkingCustomization.html
> 
> Bob Stayton
> Sagehill Enterprises
> b...@sagehill.net
> 
> On 11/6/2015 7:59 AM, Frank Arensmeier wrote:
>> Hi!
>> 
>> I am wondering. DITA has the attribute "chunk" that gives the user
>> some control about how a topic/section is treated when it comes to
>> output chunking. Setting that attribute to "to-content", the topic
>> (including its children) is "… rendered as a single chunk of
>> content". Is there something similar in DocBook? I know that I can
>> control the chunking level – but that’s a different story. I need a
>> more fine-grain control for the chunking mechanism. Could this be
>> achieved in a customisation? Which "key" stylesheets in DocBook XSLT
>> would be promising candidates to look at?
>> 
>> Thank you! /frank
>> -
>> 
>> 
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
>> For additional commands, e-mail:
>> docbook-apps-h...@lists.oasis-open.org
>> 
>> 
>> 


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

[docbook-apps] Madcap Flare to Docbook conversion

[Frank Arensmeier]

Hi List!

I am wondering, does anyone have any experience with transforming Madcap Flare 
to Docbook? I mean not within Flare – rather a transformation that takes a 
Madcap flare Toc file as input. The only reference I could find to Madcap on 
this list was a short conversation from 2006 
(http://markmail.org/search/?q=madcap+flare&q=list%3Aorg.oasis-open.lists.docbook#query:madcap%20flare%20list%3Aorg.oasis-open.lists.docbook+page:1+mid:a5szwhwjtaaeoo6j+state:results
 
<http://markmail.org/search/?q=madcap+flare&q=list:org.oasis-open.lists.docbook#query:madcap
 flare 
list:org.oasis-open.lists.docbook+page:1+mid:a5szwhwjtaaeoo6j+state:results>). 
The interview referenced there seems not available anymore.

Any ideas?

Thanks!
/frank


Frank Arensmeier

Paligo - The truly user-friendly CMS for technical documentation
www.paligo.se <http://www.paligo.se/>

Re: [docbook-apps] Madcap Flare to Docbook conversion

[Frank Arensmeier]

Hi Peter!

Thank you for your reply! I was afraid that my question was little bit unclear. 
I am working on a XSLT transformation from Flare to Docbook – at least I am 
thinking about it. I’m not a tech writer, so I haven’t used Flare for content 
creation and therefor I am still a novice when it comes to Flare. I’m a system 
developer with a broad knowledge in a number of programming languages (e.g. 
XSLT). Right now, I try to understand the structure and inner concept of a 
Flare project. 

Looking at the source code for a Flare project, a good candidate for the 
initial transformation would be the Flare Toc file. I’m aware of the fact that 
there is no equivalent to a Flare Toc file (or Ditamap for that matter) in 
Docbook. However, it seems that the Toc file already contains some vital 
information for the transformation: the content structure and links to the 
actual content. The HTML content could very well be transformed with Herold, as 
you already pointed out.

I was hoping for someone who already has done something similar before and who 
could share some insights.

Frank Arensmeier

Paligo - The truly user-friendly CMS for technical documentation
www.paligo.se <http://www.paligo.se/>
> 9 dec 2015 kl. 16:51 skrev Peter Lavin :
> 
> I’m not sure if I understand exactly what you are asking but here goes.
> 
> Use herold from dbdoclet.org <http://dbdoclet.org/> to convert HTML to 
> DocBook. [sales pitch] You might find "DocBook for Writers" useful when doing 
> this kind of conversion. It's available as an EPUB from Google or as a MOBI 
> from Amazon.
> 
> Do you have access to Flare HTML output files? If so, use these files rather 
> than the "raw" Flare files. The raw files will probably contain proprietary 
> tags such as "" but the output files will have converted these 
> to standard HTML that herold can process.
> 
> There is no DocBook equivalent to a Flare TOC file. The structure of a 
> DocBook document is used to create a table of contents. How are your 
> programming skills? Assuming that your Flare TOC entries point only at files 
> (rather than other TOC files or Flare bookmarks) you could transform the 
> Flare TOC to a DocBook file with Xincludes referencing each file created by 
> herold. The root element of your main DocBook file will depend upon what 
> parameter you use with the herold option, "--docbook-root-element".
> 
> --
> Excuse brevity. Sent from a mobile device.
> 
> Hi List!
> 
> I am wondering, does anyone have any experience with transforming Madcap 
> Flare to Docbook? I mean not within Flare – rather a transformation that 
> takes a Madcap flare Toc file as input. The only reference I could find to 
> Madcap on this list was a short conversation from 2006 
> (http://markmail.org/search/?q=madcap+flare&q=list%3Aorg.oasis-open.lists.docbook#query:madcap%20flare%20list%3Aorg.oasis-open.lists.docbook+page:1+mid:a5szwhwjtaaeoo6j+state:results
>  
> <http://markmail.org/search/?q=madcap+flare&q=list:org.oasis-open.lists.docbook#query:madcap%20flare%20list:org.oasis-open.lists.docbook+page:1+mid:a5szwhwjtaaeoo6j+state:results>).
>  The interview referenced there seems not available anymore.
> 
> Any ideas?
> 
> Thanks!
> /frank
> 
> 
> Frank Arensmeier
> 
> Paligo - The truly user-friendly CMS for technical documentation
> www.paligo.se <http://www.paligo.se/>

[docbook-apps] Caption on informalfigure not recognised by PDF stylesheet?

[Frank Arensmeier]

Hi there!

I came across an issue with the PDF stylesheets, but I am not sure if it is a 
bug nor not. Assume I have the following XML:

http://docbook.org/ns/docbook"; version="5.0">
Section title
Some para

[…]

Caption comes here




The snippet validates as valid Docbook XML but the resulting PDF however shows 
the caption element in red (no matching template found). I am using 1.78.1. Can 
someone confirm that this is a bug?

Thank you!

/Frank Arensmeier

Paligo - The truly user-friendly CMS for technical documentation
www.paligo.se <http://www.paligo.se/>

[docbook-apps] Content model for caption wrong?

[Frank Arensmeier]

Hello!

I am reading the content model definition for the "caption" element - 
http://www.docbook.org/tdg/en/html/caption.html 
<http://www.docbook.org/tdg/en/html/caption.html>
The content model clearly states that captions can contain plain text. However, 
this little snippet does not pass validation in Oxygen:

http://docbook.org/ns/docbook"; 
xmlns:xlink="http://www.w3.org/1999/xlink"; version="5.0">
Section Template Title
Text






My caption here.



Is the content model wrong or the Docbook RNG Schema?

Frank Arensmeier

Paligo - The truly user-friendly CMS for technical documentation
www.paligo.se <http://www.paligo.se/>

Re: [docbook-apps] Content model for caption wrong?

[Frank Arensmeier]

Hi!

Ok, I see. Thank you Radu!

/frank

> 4 feb 2016 kl. 12:16 skrev Radu Coravu :
> 
> Hi Frank,
> 
> Your link is from the Docbook 4 Guide.
> The Docbook 5 specs for "caption" does not seem to allow mixed content inside 
> it:
> 
>> http://www.docbook.org/tdg5/en/html/caption.html
> 
> Regards,
> Radu


-
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] Match on Language

[Frank Arensmeier]

Hi Peter!

I think it would be helpful to know what you are trying to accomplish. Could 
you be little bit more specific? Are we talking PDF or HTML output? Or some 
kind of identity transformation? What is the desired output?

Frank Arensmeier

Paligo - The truly user-friendly CMS for technical documentation
paligo.net

> 7 sep 2016 kl. 18:41 skrev Peter Fleck :
> 
> Hi all,
> 
> I'm trying to set all elements tagged with a particular language to a font.
> 
> I tried a few combinations of the below but I don't know what I'm doing. Any 
> help appreciated.
> 
> 
>FontName
> 
> 
> Many thanks,
> 
> Peter
> 
> 
> -
> To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
> For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
> 


-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org

[docbook-apps] XSLT cannot find UnwrapLinks.so

[Frank Arensmeier]

Hi!

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 
). Can someone shed 
some light on this? Why would you need that plugin? Can you download that 
plugin somewhere?

We have very large HTML builds (80MB XML Docbook files). I am concerned that 
this might have a negative impact on build time.

Thanks!
Frank

[docbook-apps] [ANN] Webinar: Publish technical documentation to Zendesk with Paligo

[Frank Arensmeier]

[ANN] Webinar: Publish technical documentation to Zendesk with Paligo

Paligo - the leading cloud CCMS for technical documentation based on DocBook 
XML has released major updates to offer even more flexible output channels. 
Paligo allows you to single-source your content, manage it with version 
branching and review and translation workflows, and publish to modern output 
formats like HTML5 responsive design, PDF/print, SCORM, Word, Salesforce 
Knowledge, Zendesk, Freshdesk, and many more.
 
[Upcoming webinar]:
 
June 23, 5 PM CET (11 AM EST, 8 AM PST)
 
The feature to publish professional technical documentation directly to Zendesk 
has now become even more powerful. With the new interface Zendesk Preflight you 
get a full visual preview of how your content will be mapped to Zendesk 
articles, and with the ability to configure it as you like.
 
Register for our upcoming webinar now to hear more about these updates to the 
Zendesk publishing feature.
 
https://us02web.zoom.us/webinar/register/WN_-s4Gw6InSJer0GUbDljE9A 

 
- Selective publishing: publish entire publications or single articles
- Resolving links between articles even if published separately
- Remapping topics to different articles
- Changing status, visibility, ownership, all from within Paligo
- Removing obsolete content from Zendesk
- And much more…
 
We will also touch on the release on the following new output channel 
possibilities:
 
- Publish directly to your web server via FTP
- Integrate your publishing in your GitHub workflow
- Get Continuous Integration publishing Paligo to BitBucket
- Publish directly to Amazon S3
 
Hope to see you there!
 
/Team Paligo
https://paligo.net/