Docbook discussion

Néstor Amigo Cairo | 4 Oct 2010 12:49

Custom numbering scheme for a DocBook document (legal style stylesheet)

Hello,

I'm using dblatex v. 0.2.12-4 (GNU/Linux Ubuntu Lucid 10.04 64bit).

===

I'm trying to number DocBook document in the 'legal' (lawyer) style, to
say:

1 Chapter one
 Article 1. Article one
 Article 2. Article two
2 Chapter two
 Article 3. Article three (*not* 'one' again)
 Article 4. Article four (*not* 'two' again)

===

To achieve that, I have modified a stylesheet, which can be found in:

/usr/share/xml/docbook/stylesheet/dblatex/xsl/sections.xsl

to be able to include it in a stylesheet (renamed as 'style.xsl'), that
I call style.css:

===
<?xml version="1.0"?>

  <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
version="1.0">

(Continue reading)

headers

Justus-bulk | 9 Oct 2010 12:42

Re: Announce: DocBook V5.1b2

Hi -

What would it take to move docbook-slides forward to DocBook 5,
including the namespace-stripping stylesheets (and one day hopefully
DB5-native XSLT2 stylesheets)?

The SVN appears to contain a 4-year-old initial step in this direction.
How functional is it?  I think I can maintain docbook-slides if nobody
else is more eager, but since I've never looked closely at DB5 so far
(for lack of slides support), I'd prefer to take over from an
operational starting point.  Norm?

Thanks,
Justus

headers

Tim Arnold | 12 Oct 2010 21:33

invalid doc, but why?

Hi,

I have the following V5.0 docbook document and any validator tells me that the inner <optional> element is invalid. But where does that info come from? All I can see from the xsd file is that a <phrase> is legal inside an <optional> and an <optional> is legal inside a <phrase>.

Not questioning the validity, just trying to figure out where the rule is located.

thanks,

--Tim Arnold

<chapter xmlns="http://docbook.org/ns/docbook"

xml:id="test" version="5.0">

<info><title>my title</title></info>

<info><title>my section</title></info>

<para>

<optional><phrase><optional>maybe</optional></phrase>

</optional>

</para>

</section>

</chapter>

headers

Barton Wright | 13 Oct 2010 05:50

RE: invalid doc, but why?

Remember that the XSD version of the DocBook 5 schema is not normative. It does its best, but it can’t convey all the subtleties of the RELAX NG schema, and the RNG schema is the only one that’s normative.

My hazy understanding is that <phrase> has two lives in DB 5. In its day job, <phrase> is a taxpaying citizen whose full name is db.phrase, and it has rights and responsibilities. But there is another <phrase> who goes by db._phrase, and this is the wild one who goes out at night with a shadowy underground group that call themselves the nearly ubiquitous inlines.

When the RNG schema allows:

it is acknowledging <db.phrase> as a full citizen, and <optional> as a full citizen member of the Technical Inlines group. Everything’s on the up and up.

But when the RNG schema allows:

</optional>

it is only because <db._phrase> showed a fake ID at the door, and pretended to be ubiquitous. And in this context, it is ubiquitous enough.

However, when you (ahem) relax your standards and go all whatever on us, you start trying out such wildnesses as:

<optional>Our goal is world domination</optional>

</phrase>

</optional>

Well now. That’s when the RNG schema puts it badge back on and starts checking IDs and taking names. In the ensuing round-up, it discovers that <db._phrase> isn’t all that ubiquitous and isn’t always allowed in the <optional> door – especially not carrying that <optional> suitcase. Wait, is that suitcase ticking?

Don’t you wish you’d taken that blue pill now?

[Late night silliness aside, I would love to read an accurate and somewhat saner description of why some ubiquitous inlines aren’t always ubiquitous. The phrase “ubiquitous inlines” is dropped onto the page without definition or comment in the DB 5 TDG, and it is clearly a source of confusion. And yes, I did actually buy paper, PDF, and Kindle versions of the book from O’Reilly.]

From: Tim Arnold [mailto:Tim.Arnold <at> sas.com]
Sent: Tuesday, October 12, 2010 3:33 PM
To: docbook <at> lists.oasis-open.org
Subject: [docbook] invalid doc, but why?

Hi,

I have the following V5.0 docbook document and any validator tells me that the inner <optional> element is invalid. But where does that info come from? All I can see from the xsd file is that a <phrase> is legal inside an <optional> and an <optional> is legal inside a <phrase>.

Not questioning the validity, just trying to figure out where the rule is located.

thanks,

--Tim Arnold

<chapter xmlns="http://docbook.org/ns/docbook"

xml:id="test" version="5.0">

<info><title>my title</title></info>

<info><title>my section</title></info>

<para>

<optional><phrase><optional>maybe</optional></phrase>

</optional>

</para>

</section>

</chapter>

headers

chris snow | 13 Oct 2010 16:16

how to throw error if imagedata not found

Is it possible for an error to be thrown during processing if a file
referred to by imagedata is not found?

    <mediaobject>
      <imageobject>
        <imagedata fileref="../../images/coding-cycle.png"/>
      </imageobject>
    </mediaobject>

Many thanks,

Chris

headers

Tim Arnold | 13 Oct 2010 16:55

RE: invalid doc, but why?

Hi Barton,

That is one great explanation and gave me a laugh or two this morning. Thanks.

I had always wondered what the deal was with those underscored elements in the documentation, figuring that it was important but not understanding how. It would be good to see more documentation on those.

In any case, I don't have many of these corner cases like optional:phrase:optional or option:phrase:inlineequation

So I'll take care of postprocessing these in a separate, somewhat messy, subroutine.

thanks for your fantastic explanation. friggin' phrase wildnesses!

--Tim Arnold

From: Barton Wright [mailto:bwright <at> streambase.com]
Sent: Tuesday, October 12, 2010 11:50 PM
To: Tim Arnold; docbook <at> lists.oasis-open.org
Subject: RE: invalid doc, but why?

Remember that the XSD version of the DocBook 5 schema is not normative. It does its best, but it can’t convey all the subtleties of the RELAX NG schema, and the RNG schema is the only one that’s normative.

My hazy understanding is that <phrase> has two lives in DB 5. In its day job, <phrase> is a taxpaying citizen whose full name is db.phrase, and it has rights and responsibilities. But there is another <phrase> who goes by db._phrase, and this is the wild one who goes out at night with a shadowy underground group that call themselves the nearly ubiquitous inlines.

When the RNG schema allows:

it is acknowledging <db.phrase> as a full citizen, and <optional> as a full citizen member of the Technical Inlines group. Everything’s on the up and up.

But when the RNG schema allows:

</optional>

it is only because <db._phrase> showed a fake ID at the door, and pretended to be ubiquitous. And in this context, it is ubiquitous enough.

However, when you (ahem) relax your standards and go all whatever on us, you start trying out such wildnesses as:

<optional>Our goal is world domination</optional>

</phrase>

</optional>

Well now. That’s when the RNG schema puts it badge back on and starts checking IDs and taking names. In the ensuing round-up, it discovers that <db._phrase> isn’t all that ubiquitous and isn’t always allowed in the <optional> door – especially not carrying that <optional> suitcase. Wait, is that suitcase ticking?

Don’t you wish you’d taken that blue pill now?

[Late night silliness aside, I would love to read an accurate and somewhat saner description of why some ubiquitous inlines aren’t always ubiquitous. The phrase “ubiquitous inlines” is dropped onto the page without definition or comment in the DB 5 TDG, and it is clearly a source of confusion. And yes, I did actually buy paper, PDF, and Kindle versions of the book from O’Reilly.]

From: Tim Arnold [mailto:Tim.Arnold <at> sas.com]
Sent: Tuesday, October 12, 2010 3:33 PM
To: docbook <at> lists.oasis-open.org
Subject: [docbook] invalid doc, but why?

Hi,

I have the following V5.0 docbook document and any validator tells me that the inner <optional> element is invalid. But where does that info come from? All I can see from the xsd file is that a <phrase> is legal inside an <optional> and an <optional> is legal inside a <phrase>.

Not questioning the validity, just trying to figure out where the rule is located.

thanks,

--Tim Arnold

<chapter xmlns="http://docbook.org/ns/docbook"

xml:id="test" version="5.0">

<info><title>my title</title></info>

<info><title>my section</title></info>

<para>

<optional><phrase><optional>maybe</optional></phrase>

</optional>

</para>

</section>

</chapter>

headers

Jim Campbell | 13 Oct 2010 18:27

Re: how to throw error if imagedata not found

Hi there, Chris,

On Wed, Oct 13, 2010 at 9:16 AM, chris snow <chsnow123 <at> gmail.com> wrote:

Is it possible for an error to be thrown during processing if a file
referred to by imagedata is not found?

<mediaobject>
<imageobject>
<imagedata fileref="../../images/coding-cycle.png"/>
</imageobject>
</mediaobject>

Many thanks,

Chris

It might not be exactly what you are looking for, but one option would be to include the image via an xinclude mechanism, and then include a xinclude fallback. It might go something like this:

       <xi:include fileref="../../images/coding-cycle.png">
         <xi:fallback>Image file is unavailable.</xi:fallback>
       </xi:include>
     </imageobject>
</mediaobject>

You would need to use a DTD or schema (or at least a DTD fragment) that allows for use of xinclude.

I hope this helps,

Jim

headers

Cramer, David W (David | 13 Oct 2010 18:42

RE: how to throw error if imagedata not found

Hi Chris,

Here’s what we do:

The build runs an xslt that produces a list of images used. Ant then checks to make sure all are the images available and kills with a useful error message the build if any are missing. To avoid an annoying build/fail/fix/repeat cycle, the error message shows all missing images rather than only listing the first missing image it finds.

I think to do something like this within the xslt would require that you write an extension/call out to java.

David

From: jwcampbell <at> gmail.com [mailto:jwcampbell <at> gmail.com] On Behalf Of Jim Campbell
Sent: Wednesday, October 13, 2010 11:27 AM
To: chris snow
Cc: docbook <at> lists.oasis-open.org
Subject: Re: [docbook] how to throw error if imagedata not found

Hi there, Chris,

On Wed, Oct 13, 2010 at 9:16 AM, chris snow <chsnow123 <at> gmail.com> wrote:

Is it possible for an error to be thrown during processing if a file
referred to by imagedata is not found?

<mediaobject>
<imageobject>
<imagedata fileref="../../images/coding-cycle.png"/>
</imageobject>
</mediaobject>

Many thanks,

Chris

It might not be exactly what you are looking for, but one option would be to include the image via an xinclude mechanism, and then include a xinclude fallback. It might go something like this:

       <xi:include fileref="../../images/coding-cycle.png">
         <xi:fallback>Image file is unavailable.</xi:fallback>
       </xi:include>
     </imageobject>
</mediaobject>

You would need to use a DTD or schema (or at least a DTD fragment) that allows for use of xinclude.

I hope this helps,

Jim

headers

Bob Stayton | 19 Oct 2010 08:11

DocBook Technical Committee Meeting Agenda: 20 October 2010

DocBook Technical Committee Meeting Agenda: 20 October 2010
=============================================================

The DocBook Technical Committee will meet on Wednesday, 20 October 2010 at
01:00p EDT (10:00a PDT, 17:00GMT, 18:00BST, 19:00CEST, 02:00JST+,
022:30p India+) for 90 minutes.

Attendance at teleconferences is restricted to members
(and prospective members) of the committee.

This is the phone number for Wednesday's DocBook TC call:

Phone: +1-719-387-5556
 Code: 902213

The DocBook TC uses the #docbook IRC channel on
irc.freenode.org.  The IRC channel is used for exchanging
URIs, providing out-of-band comments, and other aspects
of the teleconference, so please join us there if at
all possible.

Agenda

1. Roll call
2. Accepting the minutes [1] of the previous meeting.
3. Next meeting: 17 November 2010
4. Review of the agenda.
5. Review of open action items

  a.  Norm to develop a proposal for maintaining the DocBook websites.

  b.  Larry and Nancy to render the current reltable example from
      Bob and Norm with the current assembly elements for
      comparison.

  c.  Nancy to send some example reltables to the tc-list.

  d.  Bob to write up a short policy statement about the use
      of the DocBook namespace.

  e.  Bob to respond to RFE 3035565.

  f.  Jirka to investigate transclusion-to-XInclude mapping.

6.  Publishing Subcommittee report.

7.  Online documentation for 5.0 *and* 5.1 (Bob).

8.  Reltables in modular DocBook.

9.  Transclusion in DocBook.

Please see Jirka's updated proposal and discussion thread. [2]

10.  Discussion of Larry's help example in assembly and  <at> type proposal. [3]

11.  Review of Requests for Enhancement

    To browse a specific RFE, enter the URL (on one line):

      http://sourceforge.net/tracker/index.php?func=detail&;
      group_id=21935&atid=384107&aid=XXXX

    RFEs to revisit for 6.0
      1907003  biblioid content model too broad  

    RFEs to be considered 
      1679665  Add better support for modular documentation  
      2820190  add a topic element  
      2820947  Ability to transclude text 
      2964576  disallow table in entry  
      3035565  Allow sections at any level  

      No new RFEs.

-----

[1] http://lists.oasis-open.org/archives/docbook-tc/201009/msg00010.html
[2] http://lists.oasis-open.org/archives/docbook-tc/201010/msg00001.html
[3] http://lists.oasis-open.org/archives/docbook-tc/201009/msg00007.html

Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net

headers

George Cristian Bina | 20 Oct 2010 06:26

Re: [docbook-apps] Re: DocBook Inquiries

Hi,

On 10/20/10 6:57 AM, Bob Stayton wrote:
> Hi Andrew,
> I'm not aware of any DocBook video tutorials. Perhaps others can chime
> in on this subject.

We have a number of video tutorials at
http://www.oxygenxml.com/videos.html
and a few of them are directly related to DocBook. They are also related 
with oXygen but you should expect similar support also in other tools:

http://www.oxygenxml.com/demo/DocBook_Editing_in_Author.html
http://www.oxygenxml.com/demo/DocBook_Profiling.html
http://www.oxygenxml.com/demo/DocBook_Customization.html

Best Regards,
George
--

-- 
George Cristian Bina
<oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
http://www.oxygenxml.com

7	May 2013
52	April 2013
22	March 2013
9	February 2013
28	January 2013
22	December 2012
11	November 2012
10	October 2012
9	September 2012
24	August 2012
24	July 2012
21	June 2012
55	May 2012
17	April 2012
46	March 2012
7	February 2012
41	January 2012
67	December 2011
17	November 2011
29	October 2011
15	September 2011
41	August 2011
23	July 2011
20	June 2011
30	May 2011
9	April 2011
36	March 2011
43	February 2011
35	January 2011
26	December 2010
16	November 2010
18	October 2010
16	September 2010
20	August 2010
54	July 2010
29	June 2010
24	May 2010
33	April 2010
37	March 2010
29	February 2010
82	January 2010
33	December 2009
37	November 2009
21	October 2009
29	September 2009
21	August 2009
56	July 2009
42	June 2009
24	May 2009
41	April 2009
26	March 2009
30	February 2009
35	January 2009
12	December 2008
36	November 2008
53	October 2008
35	September 2008
43	August 2008
62	July 2008
29	June 2008
21	May 2008
9	April 2008
38	March 2008
19	February 2008
74	January 2008
62	December 2007
88	November 2007
81	October 2007
84	September 2007
62	August 2007
48	July 2007
18	June 2007
29	May 2007
53	April 2007
83	March 2007
8	February 2007
14	December 2006
4	June 2006
6	May 2006
2	April 2006
13	February 2006
4	November 2005
32	September 2005
26	August 2005
66	July 2005
50	June 2005
53	May 2005
82	April 2005
6	March 2005
1	March 2004
187	March 2003
162	February 2003
133	January 2003
137	December 2002
136	November 2002
152	October 2002
217	September 2002
200	August 2002
188	July 2002
179	June 2002
125	May 2002
108	April 2002
145	March 2002
116	February 2002
1	January 2001

Mon	Tue	Wed	Thu	Fri	Sat	Sun

				1	2	3
4	5	6	7	8	9	10
11	12	13	14	15	16	17
18	19	20	21	22	23	24
25	26	27	28	29	30	31