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

[ben.guillon]

Hi,

On Thu, 10 Aug 2017 06:14:04 +0200, Peter Desjardins  
 wrote:



Question #2 is: Has anyone had trouble using Saxon9HE with the DocBook
XSLT v1.0 stylesheets? The way the arguments for the later version of
Saxon are structured work much better with Gradle.
(-o:myoutputfile.xml.)


Just my feedback for question 2: As far as I can tell, I've seen no  
problem with Saxon9HE and Docbook XSLT 1.0 stylesheets.


Regards,
BG

-
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] [ANN] XSL Coverage scripts

[ben.guillon]

Hi,

I've updated in github to support saxon9HE, but it's not in a tagged  
release yet. to use it:


xslcoverage report run saxon9he [saxon options and args]

Note that I've noticed some regressions in tracing since release 6.5.5.  
The side effect is that some covered instructions appear as not covered.  
I've reported to saxon:


https://saxonica.plan.io/issues/3027
https://saxonica.plan.io/issues/3028
https://saxonica.plan.io/issues/3029

Regards,
BG

On Sat, 12 Nov 2016 19:20:00 +0100, maxwell  wrote:


Sorry, I meant Saxon-HE (same link)

On 11/12/2016 1:13 PM, maxwell wrote:

Looks great, I want to try it!  But does it work with the open source
version of Saxon?  Saxon-CE, described here:
   http://www.saxonica.com/download/opensource.xml
The version # there is quite different from what you give below (6.5.5):
theirs is 9.7.

   Mike Maxwell



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

[docbook-apps] [ANN] XSL Coverage scripts

[ben.guillon]

Hi,

For your information, I've packaged a few python scripts and a java plugin  
for Saxon to compute and visualize the coverage of XSL stylesheets when  
processed on documents with saxon (currently tested with saxon 6.5.5).


It's available here:

https://github.com/marsgui/xslcoverage/tree/master

You can look at the result with an example at the end of the readme.

Regards,
BG

-
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] SGML to XML conversion: workaround for SYSTEM entities

[ben.guillon]

Hi,

I would suggest to use XInclude with XPointer that can point to a specific  
, , or any other elements written somewhere else:



  Description

  xpointer="xpointer(id('pi-texmath-user'))"

  xmlns:xi="http://www.w3.org/2001/XInclude; />



You can aways put identifiers in the blocks often used and refer to them,  
or use xpointer in a more versatile way. Example taken from  
https://www.w3.org/TR/WD-xptr:


xpointer(id('list37')/item[1]/range-to(following-sibling::item[2]))

Regards,
BG

On Mon, 03 Oct 2016 18:33:47 +0200, Bob McIlvride  
 wrote:




Dear friends,


We've been working on converting our multiple-book, multiple-set  
documentation system from Docbook SGML >4.1 to Docbook XML 5.0.  So far,  
with some help from this list (Bob Stayton in particular), things have  
been >going well.  Now a question has come up for which we again ask  
your advice.



We begin our conversion process (SGML 4.1 to XML 4.5) in our current  
document processing system in Linux, >using osx, and then complete it  
(XML 4.5 to XML 5.0) in oXygen in Windows, our new system for  
maintaining >the source documents in XML, and producing output.



In SGML, we made extensive use of text entities to create replaceable  
text strings, as well as SYSTEM entities >to organize and replicate  
larger sections of text such as chapters and sections of books.  Taking  
advantage of >SGML's flexibility, we were able to insert identical  
blocks of text into different places in a single book, or in >different  
books of a set.  


For example, with this markup for an appendix in, say, Book 1:




 




and this entity declaration:





we were able to include the text of the GNU General Public License in a  
"GPL" appendix.  The entity  >points to a file in a common  
directory that contains all of the text of the appendix except for the  
appendix> markup.  When the entity gets resolved, the  
correct, marked up content of the appendix would be >included in the  
ouput.



Using the ID in the  tag, we were able to create links within  
Book 1 to the "GPL" appendix.  For >Book 2, we would use an ID of  
"book2-ax-gpl" for that tag, and so on for each book.  In this way we  
could >create a  of books in which the links of each book would go  
to its own copy of the "GPL" appendix.



As I understand it, this was considered acceptable practise in SGML.   
However, my reading of Bob Stayton's >book and the oXygen documentation  
has led me to the conclusion that in Docbook XML this is not possible,  
at >least not using xinclude.  With xinclude each section of text in a  
given document must have a unique ID, and >each section of text must be  
completely valid in itself.  We need to replicate identical chunks of  
text in books >within a bookset, yet give each a unique ID.  Because our  
books were designed from the beginning with this >capability in mind, we  
use it quite a bit, and would like to continue using this approach with  
Docbook XML >5.0.  

Faced with this challenge, we have tried taking the same approach in XML  
as we were using in SGML, but >instead of using SYSTEM entities, we make  
them text entities.  That is, we take the contents of the file  
app->gpl.sgml and copy it into the "" string for the text entity.  

The good news is that the document validates and we get correct output.   
However, on the back end it means >that instead of neat rows of pointers  
to filenames, our entity declaration file is quite large, as it now  
contains >all of the text and markup content of all of the common  
files.  So, the question we put to you is: Is this an >acceptable  
approach (or the only approach) to the problem, or is there a  
better/recommended alternative?



Thank  you in advance for your help.


Best regards,


Bob





Bob McIlvrideCommunications Manager


Cogent Real-Time Systems Inc., a Skkynet company

T   1 905 702 7851 ext 103

cogent.ca

Re: [docbook-apps] dblatex (was Re: [docbook-apps] Show off what you've done with Docbook)

[ben.guillon]

Hi,

It seems that xelatex is not found when dblatex tries to run it. To check  
what happens, append -V to the dblatex command to print out the actual  
command runned that fails. We can investigate further but I suggest to  
switch to the dblatex mailing list for this.


Regards,
BG

On Wed, 16 Sep 2015 17:02:56 +0200, Warren Block   
wrote:



On Sun, 13 Sep 2015, maxwell wrote:


Does your system die during the dblatex phase, or the LaTeX phase?  We  
hardly ever see a failure in the dblatex phase, unless there's actually  
an error in the DocBook XML.


This example is a known-good DocBook XML file.  However, I can't say for  
sure that the XSL file is current or working, and the problem might be  
there.  "tag:" warnings trimmed:


dblatex book.parsed.print.xml -p  
/usr/devel/doc/share/xml/freebsd-dblatex.xsl -T simple -b xetex -d -o  
book.pdf

...
tag: default template used in programlisting or screen
Build book.parsed.print.pdf
/tmp/tmpUWdRvD not removed
Unexpected error occured
Error: [Errno 2] No such file or directory

Adding -D to the command gives a Python traceback, which might tell  
something useful but not to me.




-
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] Image maps in PDF output

[ben.guillon]

FYI, dblatex supports callouts on images (see  
http://dblatex.sourceforge.net/example/dblatex/example.pdf, section 5.1).


The only constraint to have relevant coordinates.

Regards,
BG

On Mon, 07 May 2012 16:29:16 +0200, Tyson Marchuk  
tmarc...@cdlsystems.com wrote:



Hi Bob,

Thank you. I guess I'll have to do something else then if hotspots on  
graphics are not supported in PDFs. I did some more searching and  
apparently PDFs do support this  
(http://www.authorst.com/hot_graphics_in_pdf_file.php) so I guess it is  
a limitation of the DocBook XSL to PDF conversion (which I guess is what  
you're saying below although I don't quite understand the concept of  
extensions in this context.)


Thank you for your time,
-Tyson

On 2012/05/06 1:00 AM, Bob Stayton wrote:

Hi Tyson,
That message you referred to did not cover imagemaps.  It was referring  
to using callout icons in a programlisting.  In that case, an extension  
function is needed to preprocess the text in the programlisting to  
place the callout images in with the text, and that mix is then  
processed by DocBook XSL into PDF output.  There is no equivalent  
extension for mixing callouts or other hot spots with images, as far as  
I know.  I hope someone proves me wrong.


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


- Original Message - From: Tyson Marchuk  
tmarc...@cdlsystems.com

To: docbook-apps@lists.oasis-open.org
Sent: Friday, May 04, 2012 4:09 PM
Subject: [docbook-apps] Image maps in PDF output



Hello,

I'm new to Docbook and I'm trying to create an image map (click-able  
image where clicking different sections of the image results in going  
to different locations in the document) in a PDF document. I've run  
across this reference  
(http://www.sagehill.net/docbookxsl/Imagemaps.html) which seems to  
suggest this can't be done in PDFs with Docbook but it was published  
in 2007 and I saw a post on this mailing list from 2012  
(http://lists.oasis-open.org/archives/docbook-apps/201202/msg00010.html)  
which seems to suggest it should work in PDFs. I've used the example  
code from the first link with slight modifications (copied below) on  
one of my graphics and changed the stylesheet to only use numbers and  
while the output does have the numbers and text below the graphic  
there does not appear to be any linking going on in the document  
between the graphic and callouts.


Is this a limitation of PDFs or Docbook or am I doing something wrong?

Thank you for your time and help,
Tyson Marchuk

mediaobjectco
imageobjectco
areaspec id=map1 units=calspair
area linkends=callout1 coords=0,0 5000,1 id=area1/
area linkends=callout2 coords=5000,0 1,1 id=area2/
/areaspec
imageobject
imagedata fileref=images/myImage.png /
/imageobject
calloutlist
callout arearefs=area1 id=callout1
paraMy only callout1/para
/callout
callout arearefs=area2 id=callout2
paraMy only callout2/para
/callout
/calloutlist
/imageobjectco
/mediaobjectco




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






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








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





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

Re: [docbook-apps] dblatex and FO

[ben.guillon]

On Sun, 25 Mar 2012 21:37:14 +0200, Mike Maxwell maxw...@umiacs.umd.edu  
wrote:



On 3/25/2012 2:44 PM, Bob Stayton wrote:
I have come across a Makefile that is trying to apply dblatex to an FO  
file. The Makefile command
 specifies the .fo file (which was generated from xsltproc in another  
step) as the input, and a
.pdf file as the output. I'm not a dblatex user, but it is my  
understanding that it operates on
the original XML, not XSL-FO output, to generate a PDF. Is this  
Makefile in error?


You're correct, it does not have a command line parameter for .fo input,  
just xml or sgml.


I just checked that with the current version, 0.3.2.  Perhaps an older  
version used .fo input. There was also an older program called db2latex,  
I believe.  Might could be that used .fo files as input; I've never used  
it.


I confirm: neither db2latex nor dblatex have ever worked on FO files. Only  
on XML documents.


Regards,
BG


-
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] ragged index with recent fop snapshots

[ben.guillon]

On Mon, 18 Jul 2011 16:46:19 +0200, maxwell maxw...@umiacs.umd.edu wrote:


Markus Hoenicka wrote:

At first sight, I didn't find any information about SVG
graphics though. Are they known to work?


I don't know.  I expect if there's a problem, it would be with LaTeX (or
XeLaTeX), not with dblatex.  As of a few years ago, svg and Xe(La)TeX  
were

not compatible:
   http://tug.org/pipermail/xetex/2008-June/010185.html
Doesn't look like the situation's much better in vanilla LaTeX; the
consensus seems to be that you need to convert a SVG graphic to PDF  
before

including it in the LaTeX source.  The same work-around would work in
XeLaTeX, too.


Hi,

Thanks Mike and Robert for mentionning dblatex. Dblatex can detect the  
figure format (by checking the filename suffix),  automatically convert  
SVG to PDF, and then compile the tex file. For SVG figures, it calls  
inkscape.


Therefore, provided that inkscape(*) is installed there is no need to  
convert manually the figures.


Regards,
BG


(*) if another converter is required, it is not a big deal to add its call  
in dblatex.


-
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] PDF customization questions from newbie

[ben.guillon]

Hi,

I'm the dblatex maintainer, so I'm a bit biased, but if you know latex you  
will be free to customize the latex layout as you wish.


I think most of the elements are supported, except the HTML tables. The  
limitations are those imposed by latex: the latex table limitations, the  
footnotes limitations especially in tables (even if workarounded in  
dblatex), the legacy UTF8 support limitations when pdftex is used, the  
one-page only floats, the float positioning (often frustating for non-tex  
users), some hyphenation weirdness, and so on.


But on the other side dblatex deals with all the tex stuff: graphic  
conversions, makeindex use, the ability to use xetex as backend. It even  
supports some advanced features (full callout support on graphics and on  
listings, olinking between a set of documents) that I'm not sure fop-based  
solutions support without some extensions.


In a word, if you know and like latex you'll be in a friendly world.

Regards,
BG

On Thu, 10 Feb 2011 13:28:39 +0100, John Rossmann rossmannj...@yahoo.com  
wrote:



Thank you, Robert.

Your reply gives me more confidence that dblatex is the right choice.  
But... are
there any disadvantages compared to the xslt- and fop-processors that  
seem to be
the recommended way to convert XML to PDF? Are there any docbook  
elements that
are not supported by dblatex? Does dblatex give me more or less  
flexibility

compared to the fop-processor?

Johnny



- Original Message 
From: robert.buer...@bmw.de robert.buer...@bmw.de
To: rossmannj...@yahoo.com; docbook-apps@lists.oasis-open.org
Sent: Thu, February 10, 2011 12:08:58 PM
Subject: AW: [docbook-apps] PDF customization questions from newbie

Hi Jonny,

we are useing dblatex (http://dblatex.sourceforge.net/ ) for some  
documents and

produce with this way high quality PDFs.

A lot of your requirements you can achive with this approach. We are  
also using

the KOMA-script-styles without tweaking the Latex-file. With your
Latex-background I would suggest dblatex.

Regards

Robert

-Ursprüngliche Nachricht-
Von: John Rossmann [mailto:rossmannj...@yahoo.com]
Gesendet: Donnerstag, 10. Februar 2011 11:41
An: docbook-apps@lists.oasis-open.org
Betreff: [docbook-apps] PDF customization questions from newbie

Hi, recently I got started with my first docbook document, and I am very
satisfied with the great possibilities to publish a number of output  
formats

from a single structured document.

Coming from LaTeX, I am looking for possibilities to customize high  
quality PDF
output. For example, I'd like to modify paragraph indentation, font  
sizes, line
spacing, page numbering, page headers and footers etc. Ideally I am  
looking for
a gallery of document layouts from which I can choose one and maybe fine  
tune,

as it is possible under LaTeX by choosing from a large number of document
classes (like e.g. koma script).

Some help is given at  
http://www.sagehill.net/docbookxsl/PrintOutput.html. But
those  options are too limited to do things like putting a logo into the  
page
header, numbering frontmatter pages like i,ii,iii,iv,... and only the  
main
document 1,2,3,..., putting a light yellow background below verbatim  
(code) text



boxes, etc. (If someone points me to an explanation how to achieve these  
three
options - logo, page numbering, code background color - I might have a  
better

idea where to look for other solutions in the future.)

Should I go the DBLatex way and change the intermediate LaTeX file to  
use the
desired document class? Or can I find an idiot-proof PDF customization  
tutorial

somewhere that doesn't require me to learn the low-level PDF language?

Thank you
Johnny


-
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] Escape DTD snippet

[ben.guillon]

Use CDATA sections:

http://www.w3schools.com/xml/xml_cdata.asp

quote![CDATA[ !ELEMENT foo (bar)]]/quote


On Thu, 06 Jan 2011 10:15:43 +0100, Susanne Wunsch  
docbook-a...@uriah.heep.sax.de wrote:



Hello,

I really enjoy writing specifications with DocBook, currently using
dblatex for transformation to PDF.

I searched for a possibility to quote DTD snippets that aren't parsed
but integrated as is. I didn't find some appropriate hints.

  quote!ELEMENT foo (bar)/quote

Is there a possibility to put some escape around the DTD snippet?

  programlisting doesn't help.

  textdata doesn't fit. I don't snip from DTD files, but from a Word
  Document with DTD comments.

If there is an XSLT opportunity I will switch to the XSL toolchain.

Thanks for any suggestions in advance.

read you ...
Susi

-
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] Creating a documentation set with separate book outputs

[ben.guillon]

Hi,

dblatex does that on sets: it builds a PDF per book, with it's own TOC,  
index, in each. Cross-linking between books work too.


Regards,
BG

On Tue, 11 May 2010 16:20:39 +0200, Peter Desjardins  
peter.desjardins...@gmail.com wrote:



Hi All,

I have a large book that I would like to split up into several smaller,
interlinked books. The plan is to create separate book elements for the
separate books, but include a global TOC and index in each. I thought  
that

docbook sets were the way to do this, but it seems that sets are used to
merge separate books into a single one. I've tried googling, but to no
avail.

Is there a way to do it?

Thanks and Regards,


-
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] Cannot resolve imagedata element's fileref attribute using modular docbook and XInclude

[ben.guillon]

Hi Bob,

Thanks for the hints that helped me in fixing easily the bug.

Regards,
BG


On Wed, 14 Oct 2009 19:41:22 +0200, Bob Stayton b...@sagehill.net wrote:

Do you know if dblatex knows how to resolve xml:base attributes?  If  
not, then that is where it is going wrong.


When XInclude pulls in content from another directory, the XInclude  
processor inserts an xml:base attribute indicating the new directory.   
That sort of stores a change-of-directory in the resolved XML content,  
so that relative paths (like yours) in the included content can be  
resolved downstream.  When the DocBook XSL stylesheets encounter a  
relative path in a fileref, they look for xml:base attributes and  
reconstruct any fileref path to resolve any xml:base attributes from all  
its ancestor elements.  If dblatex does not do that xml:base resolution,  
then the filerefs are passed through without change and lack the  
directory fixups.


The relevant templates in DocBook XSL include:

in fo/graphics.xsl:
  xsl:template match=@fileref

in common/common.xsl:
  xsl:template name=relative-uri
  xsl:template name=xml.base.dirs



-
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] issue with olinks, sitemaps, and fo stylesheets ?

[ben.guillon]

On Sat, 30 May 2009 20:48:29 +0200, Stefan Seefeld seef...@sympatico.ca  
wrote:


Any idea what may have caused this ? I'm using xsltproc --xinclude (and  
xinclude processing of the docbook sources works fine, only the target  
db files aren't read in.


Try to add the option --xincludestyle.

Regards,
BG

-
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] Tables stop flowing with text

[ben.guillon]

On Mon, 20 Oct 2008 23:21:20 +0200, Watkins, Peter  
[EMAIL PROTECTED] wrote:



I'm using dblatex and pdflatex to make PDFs from a docbook file.The
problem I'm running into is that if I put many small tables on a page,
eventually the tables will separate from the paragraphs they're in and
they'll end up on one page with the paragraph text on another.


You have two possibilities:

1) Ask latex to hardly try to let the tables where they are:

dblatex -Ptable.default.position=[H] file.xml

2) Do not use the float mechanism:

dblatex -Ptable.in.float=0 file.xml

I would recommend 1) for your specific case. 2) is mainly for tables that  
should be splitted over several pages.


Both options work for your case. For further discussions, you should  
switch to the dblatex mailing list.


Regards,
BG

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] Docbook with Math ML/Latex = PDF

[ben.guillon]

On Mon, 20 Oct 2008 14:49:51 +0200, Dave Pawson [EMAIL PROTECTED]  
wrote:


AFAIK there is no 'recommended' way to get mathml (either kind) embedded  
into docbook... yet.


DocBook already addresses MathML, through a derived DTD, at least for  
DocBook 4.X (http://www.oasis-open.org/docbook//xml/mathml/). The  
principle is to allow mml:math within equation and inlineequation.


For an example of what dblatex can give:  
http://dblatex.sourceforge.net/example/dblatex/example_mathml.pdf


You can also look at the large W3C MathML test suite excerpt rendered by  
dblatex: http://dblatex.sourceforge.net/example/mmltest2.pdf.bz2


Regards,
BG

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [docbook-apps] Re: DocBook to text (solution)

[ben.guillon]

On Wed, 11 Jun 2008 15:53:48 +0200, W. Martin Borgert [EMAIL PROTECTED]
wrote:


Hi,

I found a solution, that is acceptable for me. Criticism and
help welcome! It's mainly:


An interesting feature would be to be able to transform DocBook to reSt.

There's already docutils-native XML-docbook  
(http://membres.lycos.fr/ebellot/dn2dbk).  It should be possible to  
reverse the Docbook-native XML XSL, and then use the existing native  
XML-rst (http://www.merten-home.de/FreeSoftware/xml2rst).


Just a thought.

Regards,
BG

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: AW: [docbook-apps] default attributes

[ben.guillon]

On Tue, 21 Aug 2007 15:42:21 +0200, Hinrich Aue  
[EMAIL PROTECTED] wrote:


Contentwidth=100%, contentdepth=100% and scalefit=1 make the images  
scale to

it's intrinsic size, but reduces their size if they are to big.


It is not the behaviour defined in TDG. When the content area is  
specified, scalefit should be ignored  
(http://www.docbook.org/tdg/en/html/imagedata.html):


Specification of content area, scaling, and scaling to fit are mutually  
exclusive. If a content area (contentwidth, contentdepth, or both) is  
specified, both scaling and scaling to fit are ignored. If the content  
area is not specified and both scaling and scaling to fit are specified,  
scalefit is ignored.


Moreover, scalefit fits to a viewport area, so that without a specified  
viewport area, scalefit is irrelevant. At least, it's my understanding of  
TDG...


Regards,
BG

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[docbook-apps] Empty link in no.anchor.mode mode

[ben.guillon]

Hello,

I've been trying to use the up to date Docbook Project common stylesheets,  
in order to add olink and powerful xref features in dblatex.


I've a section title containing a link like this:

section id=section2
  titleOnly a link in it [link linkend=ch04  
endterm=ch04short/link]/title

  ...
/section

And:

xref xrefstyle=select:title linkend=section2/

The link content is empty in the produced xref markup, which is what gives  
the no.anchor.mode in common/titles.xsl:


xsl:template match=link mode=no.anchor.mode
  xsl:apply-templates/
/xsl:template

The question is: is it the expected result? Shouldn't it take into account  
the possibly existing @enterm?


Regards,
BG

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]