[docbook-apps] DocBook Website / the navigational ToC / internal vs. external links

2010-07-22 Thread Jochen Hayek
There is no obvious or enforced difference there
regarding internal vs. external links.

I would like to see some kind of accepted or common use of how to mark up 
in whatever way *external* links.

It does make a difference,
whether to stay within that navigation system
or to leave it through an external link.

Any best practices?

J.
--
As nice as you guys here are, pls usually *only* reply to my post right on this 
mailing list.
I honestly do follow this list.
Of course, if you want to tell me, how silly I am, then let's keep that private 
;-)
but usually it's only my Bad Simple English, not my ideas.

-
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 with xhtml-1_1 produce invalid xhtml11?

2010-07-22 Thread Giuseppe Bonelli
Jirka, thanks for your reply.
You are right, but:

On Wed, Jul 21, 2010 at 11:24 PM, Jirka Kosek ji...@kosek.cz wrote:
 DocBook has much more complex structures which can be nested and can't
 be directly mapped to valid XHTML. Handling this on stylesheet level
 would be to complex, so running HTML Tidy on output of DocBook
 stylesheets makes sense in this situations.

I need to have footnotes in table titles (that's why I
usecaptionpara) and figures in table cells (that's why I use
tdpara) and there should be a mean to have them both valid in
docbook and xhtml11 output (I need xhtml11 because I am targeting IDPF
epub content).

Anyone has some suggestions (apart from postprocessing the html files)?

TIA,

__peppo

-
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 with xhtml-1_1 produce invalid xhtml11?

2010-07-22 Thread Jirka Kosek
Giuseppe Bonelli wrote:

 I need to have footnotes in table titles (that's why I
 usecaptionpara) 

Well then you have to customize stylesheets to not emit excessive p in
HTML output.

 and figures in table cells (that's why I use
 tdpara) 

In table cell you can directly use inlinemediaobject without any
surrounding elements.

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 member
--



signature.asc
Description: OpenPGP digital signature


Re: [docbook-apps] chunking or splitting for non-html files

2010-07-22 Thread Jirka Kosek
gpev...@aol.com wrote:

 Thanks for the tip. 
 I read something in an XML forum that this was not possible with the current 
 XSL, except in certain parsers like Saxon, Xerxes, 
 using the xsl:document or even the redirect:. But I had no luck getting 
 either to do what I wanted. 
 I would think that this is not that difficult after all it is essentially 
 what we are doing with chunk xsl.

Code which I have provided is writtent in XSLT 2.0. You need XSLT 2.0
processor like Saxon9 from http://saxon.sf.net
There is also nice GUI for Saxon invocation if you don't like dealing
with command-line: http://kernowforsaxon.sourceforge.net/

-- 
--
  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 member
--



signature.asc
Description: OpenPGP digital signature


[docbook-apps] footnotes in tables (docbook 4.5 and 1.75.2 stylesheets)

2010-07-22 Thread Giuseppe Bonelli
Hi again,

in the stock docbook xslt (1.75.2) I see under xhtml/footnote.xsl (and
in xhtml-1_1/footnote.xsl as well) that the test to discriminate body
text footnotes and table footnotes is done on ancestor::tgroup nodes,
which imply support only for CALS tables.

Does exists a patch or does this simply means that html table model is
not fully supported (I am usinc docbook 4.5) and is better to stick to
CALS?

Thanks,

__peppo

-
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 or splitting for non-html files

2010-07-22 Thread gpevaco

Jirka: 

Thank  you for your very helpful response. I am copying to the mail list as 
well, I was trying to be considerate and not spam the list. 
I made couple minor changes to the code, so that I can get the declaration in 
the output files, and got it to work well enough. 

xsl:stylesheet xmlns:xsl=http://www.w3.org/1999/XSL/Transform; version=2.0
!-- 
A style sheet to split out main doc into several smaller docs
 --
!--  --
xsl:output method=xml doctype-public=-//OASIS//DTD DocBook XML V4.1.2//EN 
doctype-system=http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd; 
indent=yes omit-xml-declaration=no/

xsl:template match=node()|@*
  xsl:copy
xsl:apply-templates select=node()|@*/
  /xsl:copy
/xsl:template
xsl:template match=article
  xsl:variable name=filename
xsl:number count=article/
  /xsl:variable
  xi:include href={$filename}.xml
xmlns:xi=http://www.w3.org/2001/XInclude/
  xsl:result-document href=Art-{$filename}.xml
xsl:next-match/
  /xsl:result-document
/xsl:template
/xsl:stylesheet


However I am running into an issue when I use this following stylesheet to 
sections and have a nested section 
it errors saying it cannot write out to same URI.

Here is the Style Sheet 


xsl:template match=node()|@*
  xsl:copy
xsl:apply-templates select=node()|@*/
  /xsl:copy
/xsl:template
xsl:template match=section
  xsl:variable name=filename
xsl:number count=section/
  /xsl:variable
  xi:include href={$filename}.xml 
xmlns:xi=http://www.w3.org/2001/XInclude/
  xsl:result-document href=Sect-{$filename}.xml
xsl:next-match/
  /xsl:result-document
/xsl:template
/xsl:stylesheet

Here is a sample of the XML data
 section
   title
 emphasis role=boldDATA indexterm significance=normal
   primaryDATA /primary
/indexterm
 /emphasis
  /title
  section
 titleSubData/title
 parablah blah blah/para
   /section
  section
 titleNEXT DATAindexterm significance=normal
   primaryNEXT DATA/primary
/indexterm
 /title
 paraNext Set of Data Blah blah blah/para
 programlisting format=linespecific
 INTEGER value 10
 INTEGER value 11
 INTEGER value 12
 /programlisting
  /section
 /section


How would you propose to modify the XSLT to handle the nested sections?

I tried to change the xsl:number to an xsl:select where it could name the 
result files as section/titles
but that was not successful. 
How would you handle that? Was I on the right track with the xsl:select?


Thank you for your help!
/G.  



-Original Message-
From: Jirka Kosek ji...@kosek.cz
To: docbook-apps@lists.oasis-open.org docbook-apps@lists.oasis-open.org
Sent: Thu, Jul 22, 2010 9:54 am
Subject: Re: [docbook-apps] chunking or splitting for non-html files


gpev...@aol.com wrote:
 Just to clarify this then is something that cant be done with XSLT 1.0?
Yes, it can be done, but you have to use proprietary extensions like
axon:output or exsl:document. That's why I have used standard XSLT 2.0.
 Thank you once again for your help with this, like I said I am a newbie with 
SLT.  
 It is greatly appreciated.
Please keep thread on mailing list by using Reply All so other users
an benefit from mailing list archive.
-- 
-
 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 member
-



RE: [docbook-apps] chunking or splitting for non-html files

2010-07-22 Thread Mauritz Jeanson
|  -Original Message-
|  From: gpev...@aol.com 
|  
|  However I am running into an issue when I use this following 
|  stylesheet to sections and have a nested section 
|  it errors saying it cannot write out to same URI.
|
|  Here is the Style Sheet 
|  
|  xsl:template match=node()|@*
|xsl:copy
|  xsl:apply-templates select=node()|@*/
|/xsl:copy
|  /xsl:template
|  xsl:template match=section
|xsl:variable name=filename
|  xsl:number count=section/
|/xsl:variable
|xi:include href={$filename}.xml 
|  xmlns:xi=http://www.w3.org/2001/XInclude/
|xsl:result-document href=Sect-{$filename}.xml
|  xsl:next-match/
|/xsl:result-document
|  /xsl:template


Try changing xsl:number count=section to 

 xsl:number count=section level=multiple/

Or perhaps you'll prefer

 xsl:number count=section level=any/

Mauritz



-
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 or splitting for non-html files

2010-07-22 Thread gpevaco

Mauritz:

Yes that works great, and yes i do prefer level=any option!
I like the way that works better!
Thank you very much!
/G. 







-Original Message-
From: Mauritz Jeanson m...@johanneberg.com
To: gpev...@aol.com; ji...@kosek.cz; docbook-apps@lists.oasis-open.org
Sent: Thu, Jul 22, 2010 12:05 pm
Subject: RE: [docbook-apps] chunking or splitting for non-html files


|  -Original Message-
  From: gpev...@aol.com 
  
  However I am running into an issue when I use this following 
  stylesheet to sections and have a nested section 
  it errors saying it cannot write out to same URI.

  Here is the Style Sheet 
  
  xsl:template match=node()|@*
xsl:copy
  xsl:apply-templates select=node()|@*/
/xsl:copy
  /xsl:template
  xsl:template match=section
xsl:variable name=filename
  xsl:number count=section/
/xsl:variable
xi:include href={$filename}.xml 
  xmlns:xi=http://www.w3.org/2001/XInclude/
xsl:result-document href=Sect-{$filename}.xml
  xsl:next-match/
/xsl:result-document
  /xsl:template

ry changing xsl:number count=section to 
 xsl:number count=section level=multiple/
Or perhaps you'll prefer
 xsl:number count=section level=any/
Mauritz

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



Re: [docbook-apps] footnotes in tables (docbook 4.5 and 1.75.2 stylesheets)

2010-07-22 Thread Bob Stayton
Indeed, your analysis appears to be correct that HTML tables do not handle footnotes 
as table footnotes.  They should still appear, but just as ordinary footnotes.  I 
would classify this as a bug that needs fixing.  Can you file a bug report on the 
DocBook SourceForge site?  Thanks.


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


- Original Message - 
From: Giuseppe Bonelli peppo.bone...@gmail.com

To: apps docbook docbook-apps@lists.oasis-open.org
Sent: Thursday, July 22, 2010 7:27 AM
Subject: [docbook-apps] footnotes in tables (docbook 4.5 and 1.75.2 stylesheets)



Hi again,

in the stock docbook xslt (1.75.2) I see under xhtml/footnote.xsl (and
in xhtml-1_1/footnote.xsl as well) that the test to discriminate body
text footnotes and table footnotes is done on ancestor::tgroup nodes,
which imply support only for CALS tables.

Does exists a patch or does this simply means that html table model is
not fully supported (I am usinc docbook 4.5) and is better to stick to
CALS?

Thanks,

__peppo

-
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] elements inside remark

2010-07-22 Thread maxwell
According to the documentation on DB 5
(http://www.docbook.org/tdg5/en/html/remark.html), it appears that a large
number of inline elements ought to be able to appear inside a remark
element.  However, the docbook.rng
(http://www.docbook.org/xml/5.0b9/rng/docbook.rng) appears to allow only a
few of these:
   inlinemediaobject, remark, superscript, subscript, 
   xref, link, olink, anchor, biblioref, alt, annotation, 
   indexterm.singular, indexterm.startofrange, indexterm.endofrange,
   phrase, replaceable
Missing from this list afaict are many of the gui inlines, markup inlines,
operating system inlines, etc. that the documentation says should be
allowed (and which I believe DocBook 4.5 allowed).

Perhaps this is intentional; there are some comments at
http://www.oasis-open.org/docbook/specs/docbook-5.0b6-spec-wd-01.html to
the effect that DB5 drastically reduced the content models of many
inlines. This description uses the command element as an example, and
this content model seems to correspond to the DB5 schema.  Again, this
differs from the documentation at
http://www.docbook.org/tdg5/en/html/command.html.  So maybe this is a case
of the documentation at http://www.docbook.org/tdg5/en/html/command.html
(etc.) not having caught up with the schema?

Or maybe http://www.docbook.org/tdg5/ is not the definitive documentation
for DB5, because it's v1.1 of the documentation, and for now 1.0 is what I
should be using?

So maybe my question boils down to this:  Where can I find both the
current and consistent schema and human-readable documentation for DB5?
 
   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



Re: [docbook-apps] linkend attr required in biblioref?

2010-07-22 Thread maxwell
On Thu, 22 Jul 2010 09:25:48 +0200, Markus Hoenicka
markus.hoeni...@mhoenicka.de wrote:
 maxwell maxw...@umiacs.umd.edu was heard to say:
 
 Perhaps this XML frag is supposed to be
citationbiblioref linkend=Chomsky1965 begin=23
end=25//citation
 
 I can't comment on the innards of the RNG schema regarding the  
 biblioref element, but as one of those who originally suggested the  
 biblioref element I'd like to confirm that the above usage is what we  
 had in mind. 

Thanks, after playing around I see that this works well--in fact, I don't
need the citation element (which I showed above wrapping the biblioref
element) at all.  Much cleaner!

I think the 'xrefstyle' attribute on biblioref is supposed to be used
for things like where the parens go, or whether things are parenthesized,
etc.  I suppose it's too much to ask that this could be standardized in
DocBook, perhaps along the lines of the LaTeX 'natbib' package--probably
there's just too much variability.  If only everyone did things like me!

   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