gmane.text.docbook.misc

DocBook Technical Committee Meeting Agenda: 22 May 2013

Bob Stayton — 2013-05-20T16:13:48

DocBook Technical Committee Meeting Agenda: 22 May 2013
=============================================================

The DocBook Technical Committee will meet on Wednesday, 22 May 2013 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: 15 May 2013
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 follow up on OASIS mirroring the schema directory.

  c.  Larry to try mapping slides to assembly.

  d.  Norm to clarify bridgehead entry in TDG

Implied author

Brad Scott — 2013-05-16T13:09:08

Hi again

A print edition has an implied author for some of the bibliography (ie 
under the heading "Books by Brecht). I'd like to have the author in the 
bibliographic reference so I can generate an OpenURL query when it is 
online, but I'd also want to be able to suppress it for any display. Is 
this an occasion when I'd use < at >condition on the author?

<bibliomixed 
xml:id="bibl8"><author><personname><firstname>Berthold</firstname> 
<surname>Brecht</surname></personname></author><title><emphasis 
role="italic">Poems and Songs from the Plays</emphasis></title>, edited 
and mainly translated by <editor><personname><firstname>John</firstname> 
<surname>Willett</surname></personname></editor> 
(<address><city>London</city></address>: 
<publishername>Methuen</publishername>, 
<pubdate>1990</pubdate>)</bibliomixed>

Similarly, where there are multiple items in a bibliography by an 
author, I want to keep the long dash, but inherit (and not display) the 
implied author from the preceding item. So, this would give

Punctuation after in ?

Brad Scott — 2013-05-14T14:05:04

We are using bibliomixed as the standard container for all reference 
items within a collection of humanities and social science texts.

The intent was to (effectively) take the text string as it appears in 
the print source and then apply the markup, leaving all the punctuation 
in situ as it appeared in print. So, starting with this:

Adamson, Sylvia, ‘The Literary Language’, in Suzanne Romaine (ed.), The 
Cambridge History of the English Language: Volume 4, 1776–1997 
(Cambridge, 1999), pp. 589–692

We apply markup:

<bibliomixed><bibliomset relation="article"><author><personname>Adamson, 
Sylvia</personname></author>, ‘<title>The Literary 
Language</title>’</bibliomset>, in <bibliomset 
relation="book"><editor><personname>Suzanne 
Romaine</personname></editor> (ed.), <title><emphasis role="italic">The 
Cambridge History of the English Language: Volume 4, 
1776–1997</emphasis></title> (<address><city>Cambridge</city></address>, 
<pubdate>1999</pubdate>)</bibliomset>, pp. 
<pagenums>589–692

how to have a structure in the HTML output

2013-05-14T13:33:49

Hi,

I tried to find some information about the structure cleanup in the output files, but I didn't found the right one on the web.
Today I got my output in one flat folder, so the output structure looks like this:

Root
|-- [img]
 |     |-- img1.png
|     |-- img2.png
|     '-- img3.png
|
|-- Sample.html
|-- Sample_frame.html
|-- Sample_main.html
|-- styles.css
'-- popup.js

My goal is to have the output like this:

Root
|-- [etc]
 |     |-- styles.css
|     '-- popup.js
|
|-- [html]
 |     |-- Sample_frame.html
|     '-- Sample_main.html
|
|-- [img]
 |     |-- img1.png
|     |-- img2.png
|     '-- img3.png
|
'-- Sample.html

So maybe, somebody can give me an idea how to customize docbook.
Thanks and
Best regards

Markus Sticker

Academic publishing use of DocBook

Brad Scott — 2013-04-29T13:31:25

Hi

I'm new to the list, if not to DocBook. I've been doing digital 
publishing stuff since the 90s, which often now includes helping 
publishers with data workflows, specs and documentation.

I was wondering if there are any folks out there who have experience of 
using DocBook for academic humanities and social science books. I'm keen 
to compare notes especially on any "standards" you may have adopted for 
some features, especially references and notes, and for more complex 
edition handling (distinguishing between authorial/editorial text, 
marginal notes, etc).

I've also got cases where I have endnotes, which also have surrounding 
editorial text, so one needs to be able to preserve the original context 
of the notes, as well as maintain the pointers to them in the text body.

I'm sure this isn't the first such use of DocBook, so I'm keen not to 
reinvent the wheel. I am, however, keen to develop some good examples.

Thanks

Brad Scott

e: brad.scott< at >brambletye-publishing.co.uk
LinkedIn: http://www.lin

Customizing Xrefs to Appendices

Morgan Hayward — 2013-04-25T20:46:17

In our DocBook customization, we've removed all section numbering in our appendices, but we still have xref's in some of our manuals that reference those sections.  They end up displaying as "Section E.3, 'Section Title'".  We would like them to display as "Appendix E, 'Section Title'".

I understand how to create an l:template for a specific element, but I'm lost when it comes to defining the context.  Does anyone know how to tell DocBook to use a different xref format for a section in appendix compared to a section in a chapter?

Thanks in advance for your help.

Regards,
Morgan


Morgan Hayward
Technical Writer, Documentation

RuggedCom, A Siemens Company
Office: (905) 482-4599 | Toll Free: 1 (888) 264-0006
300 Applewood Cres. Concord, Ontario L4K 5C7

[cid:image001.png< at >01CE41D3.BA7D6CD0]<http://www.ruggedcom.com/rss.xml> [cid:image002.png< at >01CE41D3.BA7D6CD0] <https://twitter.com/#!/RuggedCom>  [cid:image003.png< at >01CE41D3.BA7D6CD0] <http://www.linkedin.com/company/77282?goback=.fcs_GLHD_RuggedCom_false_*2_*

DocBook Technical Committee Meeting Minutes: 17 April 2013

Bob Stayton — 2013-04-19T15:50:41

DocBook Technical Committee Meeting Minutes: 17 April 2013
=============================================================

The DocBook Technical Committee met on Wednesday, 17 April 2013 at
1:00pm ET.

1. Roll call

Present: Dick Hamilton, Nancy Harrison,
Scott Hudson, Jirka Kosek, Larry Rowland, Bob Stayton

Regrets: Norm Walsh

Absent: Loren Cahlander

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

3. Next meeting: 15 May 2013

Scott gave regrets.

4. Review of the agenda.

Add item 7a, Moving Publishers Draft to OASIS standard.

5. Review of open action items

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

  b.  Norm to follow up on OASIS mirroring the schema directory.
      CONTINUE

  c.  Larry to try mapping slides to assembly.
      CONTINUE

  d.  Norm to clarify bridgehead entry in TDG to indicate
      that bridgeheads are not numbered like sections.
      CONTINUE

  e.  Norm to update The Definitive Guide that the
      behavior of nested links is undefined by th

Attribute Set for

Stefan Knorr — 2013-04-18T13:47:00

Hi all,

I created some custom fo:simple-page-masters for the DocBook/4, v.1.78.1
and while adding support for draft mode to them, I wondered why the
original authors bothered with putting

  <xsl:if test="$draft.watermark.image != ''">
    <xsl:attribute name="background-image">
      <xsl:call-template name="fo-external-image">
        <xsl:with-param name="filename" select="$draft.watermark.image"/>
      </xsl:call-template>
    </xsl:attribute>
    <xsl:attribute name="background-attachment">fixed</xsl:attribute>
    <xsl:attribute name="background-repeat">no-repeat</xsl:attribute>
    <xsl:attribute name="background-position-horizontal">center</xsl:attribute>
    <xsl:attribute name="background-position-vertical">center</xsl:attribute>
  </xsl:if>

everywhere, instead of just adding an attribute set to param.xsl. Any
reasons?

Stefan

TDG 5: DocBook sources?

Michael Valent — 2013-04-18T07:12:03

Hello!

I dimly remember that years ago (4.4?) I could download the original DocBook sources of The Definitive Guide somewhere. This is the ideal showcase (where else can you find _all_ elements, properly used, in one place?).

Now I've tried to find the DocBook sources of TDG5, but had no success so far.

Can anybody help?

Thanks in advance
Michael Valent

DocBook Technical Committee Meeting Agenda: 17 April 2013

Bob Stayton — 2013-04-15T18:04:53

DocBook Technical Committee Meeting Agenda: 17 April 2013
=============================================================

The DocBook Technical Committee will meet on Wednesday, 17 April 2013 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: 15 May 2013
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 follow up on OASIS mirroring the schema directory.

  c.  Larry to try mapping slides to assembly.

  d.  Norm to clarify bridgehead entry in

DocBook 5 Assemblies and XML Fragments

Thomas Schraitle — 2013-04-15T07:13:12

Hi,

DocBook 5 contains the new element "assembly" as definied in the TDG:

  http://docbook.org/tdg51/en/html/ch06.html

According to the TDG5, the resource contains a href attribute which is
definied as an anyURI datatype.

Does that mean, an ID fragment is allowed too? Something like:

  <resource href="foo.xml#intro"/>

Would that be supported? How it is supposed to work with other "XML
fragments"? Let's say, a user wants to refer to the first section
inside a file, but this section doesn't contain an xml:id attribute?
Should that be an XPointer expression? Or something else?

It seems, the current level of modularization with assemblies just
covers files and only files. However, sometimes the current situation
dictates a specific structure. As such using a more granular approach
would be very helpful.

This question originated from the docbook-apps mailinglist[1].


Thanks.


-----
[1]
https://lists.oasis-open.org/archives/docbook-apps/201304/msg00135.html

Status attribute

Togan Muftuoglu — 2013-04-14T11:03:52

Hi,

I have a document where I use status for "draft" or "final" phase of the
document.

However status attribute is not one of the common attributes, hence I
cannot use this attribute in variablelist or term elements (just to name
a few, as I am sure there are other cases as well).

Would it be possible to include status attribute in common attributes ?

Thanks

Togan

DB4 to DB5 conversion stylesheet

Alexey Neyman — 2013-04-12T06:16:28

Hi,

I am exploring possibility of conversion of our documents from DB4 to DB5 using the 
db4-upgrade.xsl stylesheet provided at docbook.org. I have a few questions regarding 
the stuff that the stylesheet drops from DB4 elements.

1. Is there a particular reason why that stylesheet drops < at >class attribute from 
<productname/>?

<xsl:template match="productname[< at >class]" priority="200">
  <xsl:call-template name="emit-message">
    <xsl:with-param name="message">
      <xsl:text>Dropping class attribute from productname</xsl:text>
    </xsl:with-param>
  </xsl:call-template>
  <xsl:copy>
    <xsl:call-template name="copy.attributes">
      <xsl:with-param name="suppress" select="'class'"/>
    </xsl:call-template>
    <xsl:apply-templates/>
  </xsl:copy>
</xsl:template>

As far as I can see from TDG5.1, it is perfectly legal in DocBook 5.0: 
http://www.docbook.org/tdg51/en/html/productname.html

At first I thought this removal is because of some element models changing before 
the final release of DocBook 5.0

Toolchain for beginner?

Bob Plantz — 2013-04-09T19:01:21

I hope this is the proper list for my questions.

I am almost there but cannot seem to get a good toolchain for writing a programming book with docbook. I have written, and self-published (lulu.com), a 568-page programming book using LaTeX, so I'm comfortable with markup languages, etc.

My requirements (desires) are to produce three versions: online (html), ereader (epub), and paperback (pdf). I learned from my current book that LaTeX does not have a reasonable path to html (and thus, not to epub).

Another important point is that I want to be able to include external files (that contain code) when processing the text. I like being able to test each program that I include in my book. Copy and paste leads to errors, and I dislike books that have programs that don't work.

I prefer doing this on my Ubuntu 12.10 but am willing to do it on my Windows 8 installation. This book will be free or very low cost, so I do not want to buy commercial software to write it. (I own a copy of MS Word, but previous experience

test post, please ignore

Aaron DaMommio — 2013-04-09T15:39:08

Testing my ability to post. Thanks.
--Aaron DaMommio

Some text after a section

2013-04-09T12:00:53

Hi,

I tried to have some text (maybe as para)after a section (parent chapter).
But the schema mentioned that the sequence will have no para after a section.
So I tried to place a new simplesect without a title or something else.
The results are not this, what I like to have.

Sample (expacted):
-------------------------8<----------------------------------
14. _ppdirect Schalter
Diese Dokumentation ist für die Variante

#if (_ASIS_SWITCH_OD_CANCEL_BUTTON == 1)
14.1. "_ASIS_SWITCH_OD_CANCEL_BUTTON"
Dieses Kapitel beschreibt die Funktionalität, die mit dem Schalter "_ASIS_SWITCH_OK_CANCEL_BUTTON" gekapselt ist.
#endif

------------------------->8----------------------------------

Sample (result):
-------------------------8<----------------------------------
14. _ppdirect Schalter
Diese Dokumentation ist für die Variante

#if (_ASIS_SWITCH_OD_CANCEL_BUTTON == 1)
14.1. "_ASIS_SWITCH_OD_CANCEL_BUTTON"
Dieses Kapitel beschreibt die Funktionalität, die mit dem Schalter "_ASIS_SWITCH_OK_CANCEL_BUTTON" gekapselt

[ANN] Translators Needed for XMLmind XML Editor

Olivier Ishacian — 2013-04-08T08:34:33

Translate XMLmind XML Editor messages to your mother tongue and win up 
to 5 “lifetime” Professional Edition licenses:

See: http://www.xmlmind.com/xmleditor/translators_needed.html

FW: [ docbook-Feature Requests-3610290 ] Add support for Microsoft Help Viewer 1.0

Olsen, Morten Engelhardt — 2013-04-08T07:46:52

To whomever who wants to look at this;

I have added a Feature Request for the Microsoft HelpViewer 1.0 format and attached the needed transforms/examples to implement this in docbook.

Hope this makes it into trunk :P

Morten Engelhardt Olsen
Software Engineer / Tools Group / Atmel Corporation
Tel: (+47) 930 94 593 
Morten_engelhardt.Olsen< at >atmel.com / http://www.atmel.com/

The information contained in this email message may be privileged, confidential and/or protected from unauthorized disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited. Please immediately notify the sender by reply if you received this email in error. Thank you for your cooperation.


-----Original Message-----
From: SourceForge.net [mailto:noreply< at >sourceforge.net] 
Sent: 8. april 2013 09:44
To: SourceForge.net
Subject: [ docbook-Feature Requests-3610290 ] Add support for Microsoft Help Viewer 1.0

Feature Requests item #3610290, was opened at 2013-04-08

DocBook Technical Committee Meeting Minutes: 20 March 2013

Bob Stayton — 2013-03-20T20:04:15

DocBook Technical Committee Meeting Minutes: 20 March 2013
=============================================================

The DocBook Technical Committee met on Wednesday, 20 March 2013 at
1:00pm ET for 40 minutes.

1. Roll call

Present: Loren Cahlander, Dick Hamilton, Nancy Harrison,
Scott Hudson, Jirka Kosek, Larry Rowland, Bob Stayton

Regrets: Norm Walsh

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

3. Next meeting: 17 April 2013

4. Review of the agenda.

No new items.

5. Review of open action items

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

  b.  Norm to follow up on OASIS mirroring the schema directory.
      CONTINUE

  c.  Larry to try mapping slides to assembly.
      CONTINUE

  d.  Norm to clarify bridgehead entry in TDG to indicate
      that bridgeheads are not numbered like sections.
      CONTINUE

  e.  Norm to update The Definitive Guide that the
      behavior of nested links is undefined by the standard.
      CONTINUE

  f.  Norm to prevent link

suppress header.rule or footer.rule for titlepage in rtf

2013-03-19T15:40:00

Hi,

 

I'm looking for a solution for suppressing the ruler line at the title page.

Does somebody have a quick implementation for that.

Currently I have extended the fop for generating rtf not only on one 
simplepagemaster, but conditional pagemaster are not in focus.

 

If I set the lines on titlepage.xsl:

<xsl:param name="header.rule" select="0"/>

<xsl:param name="footer.rule" select="0"/>

It will effect on every page.

 

Thanks and 
Kind regards

Markus Sticker
Technik ZF-Konzern/Operations and Technology ZF Group
Infrastruktur/Infrastructure (OTEP4)

ZF Friedrichshafen AG
88038 Friedrichshafen, Deutschland/Germany
Telefon/Phone  +49 7541 77-7644, Telefax/Fax  +49 7541 77-907644
Markus.Sticker.epos< at >zf.com


Vorsitzender des Aufsichtsrats/Chairman of the Supervisory Board: Prof. Dr. Giorgio Behr 
Vorstand/Board of Management: Dr. Stefan Sommer (Vorsitzender/CEO), Dr. Konstantin Sauer, Dr. Peter Ottenbruch, Jürgen Holeksa, Dr. Gerhard Wagner, Reinhard Buhl, Rolf Lutz, Wilhelm Rehm

Sitz/Headquarter

DocBook Technical Committee Meeting Agenda: 20 March 2013

Bob Stayton — 2013-03-19T04:57:51

DocBook Technical Committee Meeting Agenda: 20 March 2013
=============================================================

The DocBook Technical Committee will meet on Wednesday, 20 March 2013 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 April 2013
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 follow up on OASIS mirroring the schema directory.

  c.  Larry to try mapping slides to assembly.

  d.  Norm to clarify bridgehead entry