gmane.text.docbook.misc

RE: [docbook-tc] DocBook Technical Committee Meeting Agenda: 19 June 2013

Rowland, Larry — 2013-06-18T16:13:05

I must give my regrets for this meeting.  A mandatory meeting has just been dropped on my calendar opposite this meeting.

I will need to continue my report on mapping slides to assembly since I will not be at the meeting.

Regards,
Larry Rowland

-----Original Message-----
From: docbook-tc< at >lists.oasis-open.org [mailto:docbook-tc< at >lists.oasis-open.org] On Behalf Of Bob Stayton
Sent: Monday, June 17, 2013 2:21 PM
To: DocBook Technical Committee
Cc: docbook< at >lists.oasis-open.org
Subject: [docbook-tc] DocBook Technical Committee Meeting Agenda: 19 June 2013

DocBook Technical Committee Meeting Agenda: 19 June 2013
=============================================================

The DocBook Technical Committee will meet on Wednesday, 19 June 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

DocBook Technical Committee Meeting Agenda: 19 June 2013

Bob Stayton — 2013-06-17T20:21:13

DocBook Technical Committee Meeting Agenda: 19 June 2013
=============================================================

The DocBook Technical Committee will meet on Wednesday, 19 June 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 July 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

Re: Recommendation for XSLT book?

David Cramer — 2013-06-16T14:02:45

This page lists some resources for learning DocBook and XSLT:

http://wiki.docbook.org/LearningDocBook

I'd suggest archiving a copy of this page since we're in the midst of
some maintenance and the wiki may not always be available until we get
around to finishing it.

Regards,
David

Recommendation for XSLT book?

ольга крыжановская — 2013-06-16T12:36:04

Can any one recommend a programmers book for learning XSLT?

Olga

Re: Docbook -> EPUB 3

Jirka Kosek — 2013-06-14T07:26:31


eq operator comes in XPath 2.0, so stylesheet you are using is written
in XSLT 2.0 and you have to use XSLT 2.0 processor to run it, for
example Saxon 9. xsltproc doesn't support XSLT 2.0.

Jirka

Re: Docbook -> EPUB 3

Borden Rhodes — 2013-06-14T07:16:33

This is following up on the issue I was having back on 18 March when
fiddling with the ePub spec provided at
http://code.google.com/p/epub-revision/

On studying the source, I found that it provides
svn/trunk/util/docbook/olink.xsl which, I presume, automagically
builds the OLink database. In order to understand what's going on and
have some control over the output, I'm working through the Ant
svn/trunk/build.xml file and trying to run the commands in non-Java
equivalents.

Naturally, I've gotten stuck at the first step with this error message
in xsltproc:

XPath error : Invalid predicate
< at >*[namespace-uri() eq 'http://www.idpf.org/2011/epub']

(and, later in the output)

XPath error : Invalid expression
local-name($curelem) eq 'bridgehead'

With a caret under the eq in both messages.

Output of xsltproc --version:
Using libxml 20800, libxslt 10126 and libexslt 815
xsltproc was compiled against libxml 20800, libxslt 10126 and libexslt 815
libxslt 10126 was compiled against libxml 20800
libexslt 815 was compil

Book series data

Brad Scott — 2013-06-11T10:13:41

Hi

I'm working on documentation to standardise DocBook usage for an 
academic publisher for (mostly) humanities and social science titles, 
and am using DocBook Publisher as my starting point. Most of the time 
I'm simply enforcing < at >role values in our local customisation layer.

The plan is to use this for backlist conversion as well as an XML first 
workflow in the near future.

I'd be interested to know how people have marked up some prelims 
content, especially book series data (ie metadata about the <book> not 
any bibliographic references therein).

Initially, I was thinking of something like this:

<bibliomisc role="series">
<phrase role="seriesVolNo">10</phrase>
<phrase role="seriesISSN">1234-5678</phrase>
<phrase role="seriesName">The Library of Aramaic Studies</phrase>
</bibliomisc>

but am also aware that sometimes the half title verso (or even the half 
title itself) includes more comprehensive series data, or lists of 
related titles. How have other people resolved this? I've seen this kind 
of

AW: Changing the presentation of numbered lists and sections

Dominik Psenner — 2013-06-07T14:45:11

I believe that you will need to customize the HTML XSL. Something near:

https://lists.oasis-open.org/archives/docbook-apps/201210/msg00054.html

HTML);

Changing the presentation of numbered lists and sections

Kevin Bird — 2013-06-07T11:19:22

Hello,

In an <orderedlist numeration="arabic">, <listitems> are rendered (in HTML);

1. lisitem one
2. listiem two
...

Are there any attributes that I can add to the orderedlist (and/or section elements) that will change the presentation (in HTML) to

1). listiem one
2). lisitem two

Or even ...

(1) lisitem one
(2) listiem two
 
If the answer is 'you need to create a customization layer', could someone please point me in the right direction?
For information, my section elements are nested to level 6.

Many thanks.

--
Kevin

RE: Epigraph for parts

Jason Zech — 2013-06-05T17:50:11

I believe you need to wrap the epigraph in <partintro>

-----Original Message-----
From: Christopher Culver [mailto:crculver< at >christopherculver.com] 
Sent: Wednesday, June 05, 2013 11:27 AM
To: docbook< at >lists.oasis-open.org
Subject: [docbook] Epigraph for parts

The document that I am preparing in Docbook 5 has an epigraph following the part title. My XML editor is reporting that <epigraph> cannot occur immediately inside <part>, only inside <chapter>. Is this really the case?  Considering how common it is for books to have epigraphs on a new part title page, this seems like a serious deficiency.

What workaround would the community propose? Putting epigraph after the first chapter tag would not work, as that chapter already has its own epigraph.

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscribe< at >lists.oasis-open.org
For additional commands, e-mail: docbook-help< at >lists.oasis-open.org

Epigraph for parts

Christopher Culver — 2013-06-05T16:27:33

The document that I am preparing in Docbook 5 has an epigraph following
the part title. My XML editor is reporting that <epigraph> cannot occur
immediately inside <part>, only inside <chapter>. Is this really the
case?  Considering how common it is for books to have epigraphs on a new
part title page, this seems like a serious deficiency.

What workaround would the community propose? Putting epigraph after the
first chapter tag would not work, as that chapter already has its own
epigraph.

Re: xml parsing

Richard Hamilton — 2013-06-04T12:18:58

Hi Alex,

Successful validation against the DocBook schema is only possible if the instance is well-formed XML. So, if jing says a DocBook instance is valid, it also means the instance does not have any XML parsing errors.

Best Regards,
Dick Hamilton
-------
XML Press
XML for Technical Communicators
http://xmlpress.net
hamilton< at >xmlpress.net



On Jun 3, 2013, at 8:18 PM, Alex Kleider wrote:

Re: xml parsing

Robert Fekete — 2013-06-04T07:07:10

Hi,

AFAIK, jing does validate the XML, I remember seeing XML-errors (for example, 
missing tags) in jing output. If you want to use another just to check 
XML-parsing errors, I'd recommend xmllint.

Regards,

Robert Fekete

On 06/04/2013 05:18 AM, Alex Kleider wrote:

xml parsing

Alex Kleider — 2013-06-04T03:18:45

As a new comer to DocBook I've bee using the following tool chain:

jing /usr/share/xml/docbook/schema/rng/5.0/docbook.rng 
docbookDocument.xml
xmlto --skip-validation html bluebook.xml

It seems to work, but:

 From my reading:
DocBook.xml must first be checked for XML parsing errors before it is
validated against docbook.rng (RelaxNG grammer and Schematron rules.)
Jing is a RelaxNG validator (in Java.)

Does Jing also check xml parsing errors or should I be using another 
tool first?
I can't find clarification of this issue on the Jing site (or anywhere 
else, for that matter.)

I've been using vim as my editor, on a Linux (Ubuntu) platform.

Any advice/guidance appreciated.
Thanks.

alex

Re: Quote over multiple paragraphs

Bob Stayton — 2013-06-03T19:32:58

The choice of XSLT or CSS depends on the output type of the stylesheet and 
what you are trying to do.  In this case, putting a starting quote at the 
start of each para, and the ending quote only on the last para, would be 
done with XSLT for PDF output, and with either for HTML output (I think, not 
being a CSS expert).  It will get tricky of the blockquote contains children 
other than para, though.

Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net

--------------------------------------------------
From: "Klaus Schilling" <schilling.klaus< at >web.de>
Sent: Monday, June 03, 2013 10:11 AM
To: <bobs< at >sagehill.net>
Cc: <camille< at >neodoc.biz>; <docbook< at >lists.oasis-open.org>
Subject: Re: [docbook] Quote over multiple paragraphs

Re: Quote over multiple paragraphs

Klaus Schilling — 2013-06-03T17:11:49

From: "Bob Stayton" <bobs< at >sagehill.net>
Subject: Re: [docbook] Quote over multiple paragraphs
Date: Mon, 3 Jun 2013 09:44:51 -0700

XSLT, CSS, or a combination of both?

Klaus Schilling

Re: Quote over multiple paragraphs

Bob Stayton — 2013-06-03T16:44:51

And add a role attribute to blockquote so the stylesheet can handle it differently from ordinary blockquote elements.

Bob Stayton
Sagehill Enterprises
bobs< at >sagehill.net

From: Camille Bégnis 
Sent: Monday, June 03, 2013 7:18 AM
To: docbook< at >lists.oasis-open.org 
Subject: Re: [docbook] Quote over multiple paragraphs

I would use the <blockquote> element to group the paragraphs, and then have the XSL do the job.

NeoDoc
Camille Bégnis
camille< at >neodoc.fr
Tél: +33 (0)4.42.52.24.20
5, rue de la Touloubre
13770 Venelles
France
http://www.neodoc.fr/
On 03/06/2013 16:12, Jason Zech wrote:

I've run into the same problem. Since we use curly quote marks in our work, I need to use the quote tag to get those right, and my workarounds don't seem terribly elegant in these cases:

1) You could just use the quotation characters (rather than the tags) in those instances (I made an entity for them), but this means you are treating quotes in your work in 2 different ways. Not ideal at all but it works.

2) Later, I starte

Re: How to get a proper UTF-8 HTML with umlaut

Bob Stayton — 2013-06-03T16:43:27

Hi,


Indeed, the source is not being read correctly.  It is being read not as 
ascii but as ISO-8859-1 (Latin1).  The lowercase ü character is encoded in 
UTF-8 as hex sequence C3 BC.  The C3 and BC characters do not exist in ASCII 
encoding, but they do in ISO-8859-1 as A-tilde and fraction 1/4.  If the 
source is interpreted as ISO-8859-1, then that byte sequence would be 
interpreted as those two characters, not one.  In the ISO named entities, C3 
is &Atilde; and BC is &frac14; which is what you are seeing in your output 
for ü.   (You can see these entity declarations in the DocBook 4.5 DTD 
distribution in the "ent" directory files.)

I'm not able to duplicate your output using xsltproc and any combination of 
encodings or xsltproc options.  I did not think xsltproc could even output 
named entities like &Atilde; but I could be wrong.

Something is going wrong with the parser reading your files.  I would 
examine your xsltproc setup, try xsltproc on another system that is 
independent of the first,

Re: Quote over multiple paragraphs

Camille Bégnis — 2013-06-03T14:18:49

I would use the <blockquote> element to group the paragraphs, and then
have the XSL do the job.

*NeoDoc*
*Camille Bégnis*
camille< at >neodoc.fr
Tél: +33 (0)4.42.52.24.20
5, rue de la Touloubre
13770 Venelles
France
http://www.neodoc.fr/
On 03/06/2013 16:12, Jason Zech wrote:

RE: Quote over multiple paragraphs

Jason Zech — 2013-06-03T14:12:27

I've run into the same problem. Since we use curly quote marks in our work, I need to use the quote tag to get those right, and my workarounds don't seem terribly elegant in these cases:

1) You could just use the quotation characters (rather than the tags) in those instances (I made an entity for them), but this means you are treating quotes in your work in 2 different ways. Not ideal at all but it works.

2) Later, I started marking those quotes with a role="continues" tag and closing them as normal. I customized the XSLT to only output an opening quote mark a <quote role="continutes">...</quote>. But then your content is not really tagged correctly. But it also works.

I tend to prefer the latter, but I don't know that DocBook handles this case well. I'd love to hear other solutions. 

-----Original Message-----
From: Christopher Culver [mailto:crculver< at >christopherculver.com] 
Sent: Monday, June 03, 2013 6:54 AM
To: docbook< at >lists.oasis-open.org
Subject: [docbook] Quote over multiple paragraphs

What is th

AW: AW: AW: AW: AW: AW: How to get a proper UTF-8 HTML with umlaut

2013-06-03T14:12:05

Hi Markus,

I have set this parameter before. 
(See the former mails)

So there must be some switches for 
setting the entity translation of.

As you can see all special characters are 
translated to HTML entities.

Futher I think the source is not read well.
The mutation form ü to Ã¼ is maybe cause by 
reading the source as ascii not as UTF-8.

BR
Markus





-----Ursprüngliche Nachricht-----
Von: Markus Hoenicka [mailto:markus.hoenicka< at >mhoenicka.de] 
Gesendet: Montag, 3. Juni 2013 15:52
An: docbook< at >lists.oasis-open.org
Betreff: Re: AW: AW: AW: AW: AW: [docbook] How to get a proper UTF-8 HTML with umlaut

Am 2013-06-03 15:39, schrieb markus.sticker.epos< at >zf.com:

I'm sorry, I was too quick with this test.

I've now processed the document with the following command line, using chunked output and UTF-8 as you requested:

xsltproc --output output/ --stringparam chunker.output.encoding UTF-8 /usr/share/sgml/docbook/xsl-stylesheets/html/chunk.xsl refdbtest.xml

The result i