Peter Fleck | 18 Sep 15:38 2014
Picon

audio epubs

Hi all.

I might be stretching a bit far here but worth trying.

Is it possible to do a lot of the work to make audio epubs using 
stylesheets?

First, how to auto generate ids for each <para>? I'm sure that is 
straightforward. (Or if more granularity is needed then id's at the 
sentence or word level as needed).

Second, populate the smil file with the ids

<smil xmlns="http://www.w3.org/ns/SMIL" 
xmlns:epub="http://www.idpf.org/2007/ops" version="3.0">
     <body>
         <seq id="id1" epub:textref="index.xhtml" epub:type="bodymatter 
chapter">
             <par id="paragraph1">
                 <text src="index.xhtml#para-id1"/>
                 <audio src="audio/file.mp3" clipBegin="0:00:02.000" 
clipEnd="0:00:15.000"/>
             </par>
             <par id="paragraph2">
                 <text src="index.xhtml#para-id2"/>
                 <audio src="audio/file.mp3" clipBegin="0:00:15.000" 
clipEnd="0:00:25.000"/>
             </par>
             ....
         </seq>
(Continue reading)

Janice Manwiller | 11 Sep 14:36 2014

Alternate text for table and image accessibility - textobject, alt, summary?

Apologies in advance if this is the wrong list. I've had conflicting advice about what to post to docbook vs. docbook-apps.

I'm brand new to DocBook, and am reviewing the current source files for the doc set at my new job.

Is there a recommendation for providing alternate text for accessibility?

The current source files have textobject for images and nothing for tables.

Is the alt element better than textobject?

For tables, should I use alt or summary?

Thanks,

Janice
Peter Fleck | 5 Sep 12:00 2014
Picon

duplicate dcterms:date

Hi all,

I'm getting duplicate dcterms:date in the epub3 package.opf

<meta property="dcterms:date">2012</meta>
<dc:date>2012</dc:date>
<meta property="dcterms:date">2012</meta>
<dc:date>2012</dc:date>

The validator at http://validator.idpf.org/ gives me this.

ERROR OEBPS/package.opf 20 14 element "dc:date" not allowed here; expected the element end-tag or element "dc:contributor", "dc:coverage", "dc:creator", "dc:description", "dc:format", "dc:identifier", "dc:language", "dc:publisher", "dc:relation", "dc:rights", "dc:source", "dc:subject", "dc:title", "dc:type", "link" or "meta"

I'm just wondering if anyone else is getting this or if it is a bug in my stylesheet.
I'm using docbook-xsl-ns-1.78.1 stylesheets.

Thanks,

Peter
Mary Tabasko | 5 Sep 05:34 2014

Oops. Wrong list!

Drat. Sorry -- I joined both the docbook and docbook-apps list, and sent
that last message to the wrong one. Great introduction! D'oh. 

Apologies!

-- Mary Tabasko
Mary Tabasko | 5 Sep 05:33 2014

Thanks!

Hi, gang.

I just joined this list, and I wanted to start off by offering
a HUGE thanks to everyone who maintains the DocBook Stylesheets
and the related resources.

We have been using them where I work for years, and we would
not be able to do the things we've done without them! Over the
years, I've been asked to do some things that I was not sure would
be possible, but the stylesheets have provided a terrific basis for
a bunch of crazy things.

So thanks!

We are just finishing up a project to move some large documents
we produced as Microsoft Help (CHM) output to the Webhelp format.
We've been trying to replace MSHelp (the compiler is getting harder
and harder to keep running), but were having no luck finding a suitable
replacement, until we stumbled on the Webhelp transforms. 

We did run into some non-trivial issues and ended up doing a fair
amount of work to get what we wanted, but we got very close
to our wishlist, and it wouldn't have been possible without the
Webhelp transforms. So thanks again.

I didn't want to dump a long list of the issues we had and
how we dealt with them, but if anyone is interested, I'd be
happy to describe them (and send a screen shot of what we
ended up with). Some of it might be useful or informative
in relation to a few of the bug/issue reports I've seen on them,
but I don't want to offer unsolicited input.

Thanks again! You guys rock!

-- Mary Tabasko
Roland Mainz | 2 Sep 16:02 2014

Fwd: Listing dates of contributions in a DocBook manpage ?

[2nd try to get this question posted...]

---------- Forwarded message ----------
From: Roland Mainz <roland.mainz <at> nrubsig.org>
Date: Tue, Sep 2, 2014 at 3:51 PM
Subject: Listing dates of contributions in a DocBook manpage ?
To: docbook <at> lists.oasis-open.org

Hi!

----

Is there any good way to describe that an author contributed from
date1 to date 2 to a project as employee of a company and then from
date3 until now on the same project as a private person ?

Right now it looks like this:
-- snip --
<refentryinfo>
<authorgroup>

<author>
<firstname>Merida</firstname>
<surname>Archer</surname>
<email>marcher <at> bowhunting.com</email>
<affiliation><orgname>Archery Inc.</orgname></affiliation>
<contrib>Developer (2013-2014)</contrib>
</author>

<author>
<firstname>Merida</firstname>
<surname>Archer</surname>
<email>merida.archer <at> gmail.com</email>
<contrib>Developer (2014-)</contrib>
</author>

</authorgroup>
</refentryinfo>
-- snip --

The problematic parts for me are the year ranges embedded in <contrib>
where they AFAIK do not belong to...

----

Bye,
Roland

--

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz <at> nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 3992797
 (;O/ \/ \O;)
David Clunie | 26 Aug 15:55 2014

Line numbering ordinary text, not just 'verbatim environments'

Hi

I need to include line numbers for all the text in a document (so
that reviewers can comment on specific parts of the document with
precise references, without having to manually count line offsets
from the nearest section label, etc). This is for PDF rendering.

I found the "line numbering extensions" but I understand that it
only applies to 'verbatim environments', which the documentation
describes as 'address, literallayout, programlisting, screen,
synopsis'.

Before I start customizing the stylesheets, is there a mechanism
for this already?

David

PS. Or to put it another way, I am looking for something like Microsoft
Word's line numbering feature, but better, in that ideally table lines
would also be numbered (which they are not in Word).

PPS. Either restarting numbering with a page, or continuous from the
start would be fine for my use case.
Bob Stayton | 20 Aug 19:45 2014
Picon

DocBook Technical Committee Meeting Minutes: 29 August 2014

DocBook Technical Committee Meeting Minutes: 20 August 2014
=============================================================

The DocBook Technical Committee met on Wednesday, 20 August 2014
at 1:00pm ET.

1. Roll call

Present: Loren Cahlander, Dick Hamilton, Jirka Kosek, Larry Rowland,
Bob Stayton, Norm Walsh

Regrets: Scott Hudson, Jirka Kosek

Absent: Nancy Harrison

2. Accepted the minutes [1] of the previous meeting.

3. Next meeting: 17 September 2014

Neither Norm or Bob are available on the 17th.
Norm suggested moving the meeting to 3 Sept,
to be held if we need to vote on moving 5.1
forward, otherwise we will meet next 15 Oct.

4. Review of the agenda.

No change.

5. Review of open action items

   a.  Norm to publish an XSD for 5.1 when it is finished.
       COMPLETED

   b.  Norm to work with OASIS to advance DocBook 5.1 to
       OASIS Standard.
       CONTINUED

   c.  Norm to convince someone to implement the new XInclude
       standard.
       CONTINUED

   d.  Jirka to update "DocBook Transclusions" document to reflect
       the new XInclude 1.1 features.
       CONTINUED

6.  Publisher's and eLearning subcommittee reports

Scott reports via email:
No new inputs from the subcommittees, but would like to get the
Publishers stylesheet code added to the XSL distro.

7.  Transclusion in DocBook

Norm is still trying to motivate another implementation of the
new XInclude spec, and Jirka will deliver his update of
the guidelines in September.

8.  DocBook 5.1 release

Norm proposed fixing two Schematron related items so they conform
to the ISO Schematron spec, and these will have no impact on
content models.  Norm proposed releasing 5.1 with those changes.
The committee vote was unanimous to proceed.

There were six issues reported on GitHub:
http://github.com/docbook/docbook/issues

a. Allow trademark everywhere #8

Norm reported that this was already in 5.1 CR2 and will be
part of the released 5.1.

b.  Allow revnumber inline.

To be considered in 5.2.

c.  Add buildtarget element.

To be considered in 5.2.

d.  Makefile and pipelines are not very Windows friendly.

e.  Convert  <at> name on s:pattern to s:title.

Norm to fix.

f.  Add a Schematron rule for  <at> startref on indexterm.

Norm to fix.

9.  Review of Requests for Enhancement

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

       https://sourceforge.net/p/docbook/rfes/300/

     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)

    No new RFEs

-----

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

--

-- 
Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Bob Stayton | 18 Aug 22:04 2014
Picon

DocBook Technical Committee Meeting Agenda: 20 August 2014

DocBook Technical Committee Meeting Agenda: 20 August 2014
=============================================================

The DocBook Technical Committee will meet on Wednesday, 20 August 2014
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.

Agenda

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

   a.  Norm to publish an XSD for 5.1 when it is finished.

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

   c.  Norm to convince someone to implement the new XInclude
       standard.

   d.  Jirka to update "DocBook Transclusions" document to reflect
       the new XInclude 1.1 features.

6.  Publisher's and eLearning subcommittee reports

7.  Transclusion in DocBook

8.  DocBook 5.1 release

9.  Review of Requests for Enhancement

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

       https://sourceforge.net/p/docbook/rfes/300/

     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)

    No new RFEs

-----

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

--

-- 
Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Norman Walsh | 24 Jul 01:52 2014

DocBook V5.1CR3 XSD

Hello world,

This afternoon (well, local afternoon anyway), I published an XML
Schema version of DocBook V5.1CR3:

  http://docbook.org/xsd/5.1CR3/

I assert that it's a valid XSD. Because Saxon EE said so.

It passed a smoke test on a few DocBook documents, but is surely
buggy. It is also considerably more liberal than the normative DocBook
schemas. I don't expect it to reject any valid DocBook documents, but
it is by no means guaranteed that passing the XSD test means your
document is valid.

Interesting open question: how many of these XSD validation
infilicities could be tested with XSD 1.1 xs:assert statements?

Share and enjoy.

                                        Be seeing you,
                                          norm

--

-- 
Norman Walsh <ndw <at> nwalsh.com>      | If you put tomfoolery into a
http://www.oasis-open.org/docbook/ | computer, nothing comes out of it
Chair, DocBook Technical Committee | but tomfoolery. But this
                                   | tomfoolery, having passed through
                                   | a very expensive machine, is
                                   | somehow enobled and no-one dares
                                   | criticize it.--Pierre Gallois
Stefan Knorr | 23 Jul 18:17 2014
Picon

Localisation bug in common/titles.xsl?


Hi all,

just a question: Is the following a localisation bug or am I
overlooking something obvious and this is fine?

DocBook 1.78.1, file: common/titles.xsl, line 485ff:

[...]
<xsl:template match="answer" mode="title.markup">
  <!-- answers don't have titles -->
  <xsl:text>Answer</xsl:text>
</xsl:template>

<xsl:template match="qandaentry" mode="title.markup">
  <!-- qandaentrys are represented by the first question in them -->
  <xsl:text>Question</xsl:text>
</xsl:template>
[...]

Regards,

Stefan.

--

-- 
SUSE LINUX Products GmbH, Maxfeldstraße 5, D-90409 Nürnberg
Geschäftsführer: Jeff Hawn, Jennifer Guild, Felix Imendörffer
HRB 16746 (Amtsgericht Nürnberg)

Gmane