Test User | 26 Feb 18:07 2015

Status of bug #281: allow xi:include in set

Hello All,

It was reported that xi:include was not allowed in <set>. At
http://sourceforge.net/p/docbook/rfes/281/ it says that the bug is
"fixed for 5.1".

When jing validates my document against the DocBook 5.1CR3 RELAX NG
schema (docbookxi.rng), it reports:
docs.xml:8:34: error: element "xi:include" not allowed here; expected
the element end-tag or element "setindex"

   | <?xml version="1.0"?>
   | <set xmlns="http://docbook.org/ns/docbook"
   |      xmlns:xi="http://www.w3.org/2001/XInclude"
   |      xml:lang="en"
   |      version="5.0">
   |   <info>
   |     <title>Set title</title>
   |   </info>
   |   <xi:include href="book1.xml"/>
   |   <xi:include href="book2.xml"/> <!-- line 8 -->
   | </set>
The document will validate if there is only one xi:include in the <set>
so the sample document above is illegal.

Is there in fact a version of the DocBook schema that will accept the
document above?

Test User.
Bob Stayton | 18 Feb 19:13 2015

DocBook Technical Committee Meeting Non-Minutes: 18 February 2015

No meeting in February as we failed to reach quorum.

Norm earlier reported that he submitted the appropriate tickets to OASIS 
to begin the Docbook 5.1 standards process.  We will discuss its 
progress next month.


Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Chet Ensign | 17 Feb 21:30 2015

Your request for CSD and 30 day public review for DocBook v5.1 has been received

Members of the DocBook TC, 

Your requests to publish the Committee Specification Draft for DocBook v5.1 and release it for public review have been received. You can find the TC Admin JIRA tickets tracking this at https://issues.oasis-open.org/browse/TCADMIN-2077 and https://issues.oasis-open.org/browse/TCADMIN-2078

I will let you know when we start work on these tickets. Should be in a day or two. Meanwhile, let me know if you have any questions on the tickets or the next steps. 


/chet   [§] 
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open
Markos | 17 Feb 20:01 2015

Re: Translate words in html files.

On 17-02-2015 13:46, Michael.Urban <at> jpl.nasa.gov wrote:
> Your message dated: Tue, 17 Feb 2015 12:45:42 -0200
>> Hi,
>> Which document I need to edit to change the words that are generated in
>> html format?
>> I don't know the details of the Docbook structure. I'm just a user.
>> For example, I would like to produce html documents in Esperanto, then I
>> would like to change:
>> *Table of Contents ->  Indekso
> I looked into doing this some years ago but could not get a consensus
> from Esperantists on best translations.  Anyway, I think you want to add
> a file, eo.xml, to the stylesheet's 'common/' directory, and add a
> suitable line to l10n.xml
> (Is 'indekso' the right word for 'Table of Contents'?  Isn't 'Enhavoj'
> better?  'Next' could better be 'sekva' or even 'sekve')
Hi Michael and Bob

I discovered that there is already an eo.xml file in the directory:

But when I put in the header of the source text (hackakvoj.xml) the 
<article lang = "eo"> the following error appears:

$ jw hackakvoj.xml
Using catalogs: /etc/sgml/catalog
Using stylesheet: /usr/share/docbook-utils/docbook-utils.dsl#html
Working on:
L10N ERROR: gentext-intra-label-sep

Should I change in the header of  source file the line?

Any tip?


Source file (hackakvoj.xml):

<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"

<article lang="eo">

<title>Water - AKVO - Integrada Rigardo</title>
<pubdate>Januaro 2015</pubdate>

<title>Sugestoj estas bonvena!</title>
<imagedata fileref="bildoj/email_graf.png"/>

<title>Akvo - kio estas?</title>

Markos | 17 Feb 15:45 2015

Translate words in html files.


document I need to edit to change the words that are generated in html format?

I don't know the details of the Docbook structure. I'm just a user.

For example, I would like to produce html documents in Esperanto, then I would like to change:

Table of Contents -> Indekso
Revision History -> Revizioj
Prev -> Antaŭa
Home -> Hejmo
Next -> Proksima
Bibliography -> Bibliografio
Books -> Libroj

And so on.

Any help?


Bob Stayton | 16 Feb 22:36 2015

DocBook Technical Committee Meeting Agenda: 18 February 2015

DocBook Technical Committee Meeting Agenda: 18 February 2015

The DocBook Technical Committee will meet on Wednesday, 18 February 2015
at 1:00pm ET 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.


1. Roll call
2. Accepting the minutes [1] of the previous meeting.
3. Next meeting: 18 March 2015
4. Review of the agenda.
5. Review of open action items

   a.  Norm to work with OASIS to advance DocBook 5.1 to
       OASIS Standard.

   b.  Norm to convince someone to implement the new XInclude

   c.  Bob to integrate publishers XSL into DocBook XSL.

   d.  Bob to work with Norm to request Oxygen to implement
       XInclude 1.1.

   e.  Jirka to work with Norm to post the new DocBook
       Transclusions document.

   f.  Bob to follow up with Norm about OASIS tickets for
       DocBook 5.1 submittal.

   g.  Dick will post a request for GSOC ideas and mentors.

6.  Publisher's and eLearning subcommittee reports

7.  XInclude 1.1 status.

8.  DocBook 5.1 release

9.  Review of Requests for Enhancement

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


     RFEs to revisit for 6.0

     247   1907003  biblioid content model too broad

    RFEs under discussion

    Ticket  Tracker
     260   2820947  Ability to transclude text
     273   3035565  Allow sections at any level
     291   3491860  license tag  (hold for 5.2)
     306            Allow Block Elements inside abstract

    One new RFE


[1] https://lists.oasis-open.org/archives/docbook-tc/201501/msg00003.html


Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Amin Abbaspour | 15 Feb 05:27 2015

Arabic-Indic numbering in XSL FO output for orderedlist

hi everyone,

how can I use arabic-indic numbering for orderedlist items in FO output of docbook-xsl. 

I can get it working with epub/html using CSS but not much success with FO. 

for the record, setting "chapter.autolabel" parameter to '&#x661;' makes Arabic/Persian numbers working in chapters but that’s separate than orderedlist items.

many thanks for the help,

Robin Cover | 10 Feb 17:18 2015

Admin test (please ignore)

This is not the message you are looking for.
Markos | 10 Feb 13:22 2015

Document in Esperanto with Docbook


I use Docbook to write documents in Portuguese and English.

I would like to start using Esperanto with Docbook.

How to write the letters of Esperanto with diacritic marks, ĉ, ĝ, ĥ, ĵ, 
ŝ, and ŭ?

Any tip?


PS- I use Debian 6.0 (Squeeze) with the script "jw" to generate the html 
files from xml sources.
Richard Hamilton | 9 Feb 22:32 2015

Google Summer of Code 2015 -- Last call for participants

So far, I've only received one message expressing interest in having the DocBook project apply to
participate in the Google Summer of Code this year.

The applications open today (Feb 9) and close in 10 days (Feb 20), so unless I hear from a few more people, I
don't think it will make sense to apply this time around.

I've enclosed my original message for your reference. If you're interested, now's your last chance to
raise your hand.

Best regards,
Dick Hamilton
XML Press
XML for Technical Communicators
hamilton <at> xmlpress.net

As many of you know, the DocBook project (as distinct from the DocBook TC, though many people participate in
both activities) applied to the program several times and was accepted twice. The program has brought us
some useful software and, even more important, new contributors to the DocBook community.

To participate this year, we need two things:

1) Mentors: we need at least 5 or 6 people who are willing to participate as mentors.
2) Ideas: we need ideas for projects that students can work on.

I'm willing to be the organization administrator again this year, but I'm glad to hand over responsibility
if someone else wants the job this year.

For the full schedule and more information about the program, go to:

February 20 is the deadline for applications. To participate, we need to have mentors lined up by February
9, which is the opening date for filing applications.

If you're interested in participating, you can reply to this message on the list or send me email directly at
the address below.

Best regards,
Dick Hamilton
Thomas Schraitle | 9 Feb 17:36 2015

DocBook 5: Removing XLinks for Block Elements?


after playing around with some DocBook 5 customization, I'm a little
bit stuck in regards to XLink customization. 
Is there an easy way to remove XLink attributes for all block elements
only, but leave it there for inline elements? I fear I have to redefine
all(?) patterns for block elements. 

Obviously, this solution just removes *all* XLink attributes:

include "db51cr3/docbook.rnc"
   db.xlink.attributes = empty

After digging deeper, a common pattern for a DocBook element definition
uses db.common.attributes. Would it make sense to distinguish between
a block and inline elements at this level?

We could define a db.common.block.attributes and a
db.common.inline.attributes pattern to make customization easier.
Bascially it is the same, but it would allow developers to customize
just inline or block elements in one fell swoop. I guess, there are
other use cases not only for XLink attributes. :)

What do you think? Is this possible? Useful?


    Thomas Schraitle