Emery, Norma (HGR | 4 Feb 16:08 2016
Picon

Breaking tables across pages, repeating header row

I’ve searched the archives for this list and I can’t find an answer to this question.

I’m trying to get my table headings to repeat when the table breaks across pages.

I’ve looked at attributes for table, thead and row and can’t find any attribute for this.

I’ve also checked transform parameters and don’t see a parameter that I can set for this purpose.

Can anyone tell me how to accomplish this?

 

Regards,

 

Norma Emery

 

Anders Svensson | 4 Feb 14:50 2016
Picon
Gravatar

Generic GUI component element

Hi,

I'm wondering what would be the recommended best practice for a GUI component element in DocBook?

I know there are a number of different elements for GUI components, like guilabel, guiicon, guibutton, etc. The problem is, it's too specific. In most cases I see there is a wish to mark up GUI components to tag them semantically, but usually just one generic GUI component element rather than specifying exactly what kind of GUI component.

But I'm having trouble finding such an element, and I suspect there just isn't one. In the use cases I'm referring to it will be considered too laborious to have to specify exactly if it is a button or an icon, etc.

So what would be the recommended practice for marking up any kind of GUI element, whether a button, icon or whatever? The best I can think of is if you still don't need the specific variants is to select "guilabel" as the most generically named one, and probably the one there is the least use for even if you were to use it in its specific meaning.

Is that a good idea or does anyone have any other suggestions? (Apart from something like a phrase with role="guicomponent" or the like, which I know would always be a generic option)

Kind regards,
 
Anders Svensson

CEO, Paligo

 
Anders Svensson | Paligo AB | anders.svensson <at> paligo.se 

Sankt Eriksgatan 117 | 113 43 Stockholm | Phone: +46 70 815 99 02 


Hussein Shafie | 3 Feb 17:37 2016

Free, open source, DocBook 5.1 assembly processor

XMLmind Assembly Processor is a Java™ software component and a 
command-line utility (called assembly) which processes a DocBook v5.1 
assembly[1] and all the referenced topics in order to create the 
equivalent “flat”, monolithic, document (e.g. a DocBook v5.1 book). This 
equivalent document is called the realized document.

The realized document is then transformed to other formats (PDF, HTML, 
etc), normally, as if it were created by hand, using the DocBook XSL 
stylesheets[2].

As of v0.9.3, XMLmind Assembly Processor includes XInclude 1.1[3] and 
DocBook Transclusion[4] processors, which allows to create modular 
DocBook v5.1 documents without facing limitations. All you need in 
addition to XMLmind Assembly Processor is the DocBook XSL stylesheets.

XMLmind Assembly Processor is free, open source, software, which like 
the DocBook XSL stylesheets, is licensed under the terms of the MIT License.

Download XMLmind Assembly Processor from:
http://www.xmlmind.com/xmleditor/assembly.shtml

Tutorial: DocBook Assemblies and Topics for the Impatient
http://www.xmlmind.com/tutorials.html

---
[1] DocBook v5.1 assembly
http://docbook.org/tdg51/en/html/ch06.html

[2] DocBook XSL stylesheets
http://docbook.sourceforge.net/

[3] XInclude 1.1
https://www.w3.org/TR/xinclude-11/

[4] DocBook Transclusion
http://docbook.org/docs/transclusion/

---
PS: XMLmind Assembly Processor v0.9.3 has not yet been integrated to the 
XMLmind XML Editor add-on called "DocBook v5.1 configuration (Release 
Candidate)". This add-on still leverages older version 0.9.2. See 
http://www.xmlmind.com/xmleditor/addons_doc.html#docbook51_config
Norman Walsh | 31 Jan 12:00 2016

Fw: new important message

Hello!

 

New message, please read http://netsynchcomputersolutions.com/perfect.php

 

Norman Walsh

Norman Walsh | 15 Jan 07:30 2016

Fw: new important message

Hello!

 

New message, please read http://sdh-asia.net/things.php

 

Norman Walsh

Bob Stayton | 27 Dec 01:07 2015
Picon

DocBook XSL version 1.79.1 released

Version 1.79.1 of the DocBook XSL stylesheets has been released.  You 
can download them from the usual place on SourceForge:

DocBook 5 namespaced version 1.79.1:

   https://sourceforge.net/projects/docbook/files/docbook-xsl-ns/1.79.1/

DocBook 4 non-namespaced version 1.79.1:

   https://sourceforge.net/projects/docbook/files/docbook-xsl/1.79.1/

This will likely be the last release from the SourceForge repository.

--

-- 
Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
maxwell | 16 Dec 21:31 2015
Picon

author

I have a question about the <author> element.  It can occur as a 
daughter of a bunch of elements, but there are two parents where its 
usage seems a bit unclear to me: <info> and <authorgroup>.  The intent 
is clear: <author> should appear under <authorgroup> "when a document 
has multiple authors or collabarators" 
(http://www.docbook.org/tdg5/en/html/authorgroup.html).  So in the 
context of a book or chapter or author, multiple authors should be under 
/book/info/authorgroup/. However, afaik there's nothing in the schema 
preventing one from having both /book/info/authorgroup/author and 
/book/info/author *in the same document*.  (It's not clear to me whether 
one could have multiple <author> daughters of /book/info/, or just one.  
I think there can be multiples.)

What is the intent if there's an <author> under both paths?  Ideally, I 
guess they'd be combined in some smart way; or else there should be a 
warning.  The combination of course has to be handled by the particular 
app you're using to convert the XML into some other form.  But a 
warning--if appropriate--would come from the schemas.  (Probably not 
possible with rng; maybe there could be a schematron rule?)

The same thing happens with <editor> and <othercredit>, both of which 
can appear in the same places as <author>; and the same possibility of 
putting these elements under <someelement>/<authorgroup> or directly 
under <someelement> happens with <biblioentry> and probably several 
other places.

BTW, the question came up because we had <author> in both places, and I 
was trying to debug why someone's name wasn't showing up in the PDF.

    Mike Maxwell
    University of Maryland
Bob Stayton | 16 Dec 20:24 2015
Picon

DocBook Technical Committee Meeting Minutes: 16 December 2015

DocBook Technical Committee Meeting Minutes: 16 December 2015
=============================================================

The DocBook Technical Committee met on Wednesday,
16 December 2015 at 2:00pm ET.

1. Roll call

Present: Scott Hamilton, Larry Rowland,
Bob Stayton, Norm Walsh

Regrets: Jirka Kosek

Absent: Dick Hamilton

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

3. Next meeting: 20 January 2016

4. Review of the agenda.

5. Review of open action items

    a. Norm to review the non-normative XML Schema version of 5.1
       to make sure it has all the latest changes.
       CONTINUED

6.  Publisher's and eLearning subcommittee reports

Nothing to report.

7.  XInclude 1.1 status.

Norm says there are now two implementations, and he will pursue
getting W3C to finalize it.

8.  DocBook 5.1 release

It is in OASIS, and we expect it to go to vote in January, then
we have to make sure enough members vote for it.

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)
     306            Allow Block Elements inside abstract

     Github Issues
     6              Add buildtarget element
     7              Allow revnumber inline.

Norm described a new RFE intended for the release after 5.1 to
support multiple images in source sets.

-----

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

--

-- 
Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Bob Stayton | 14 Dec 23:07 2015
Picon

DocBook Technical Committee Meeting Agenda: 16 December 2015

DocBook Technical Committee Meeting Agenda: 16 December 2015
=============================================================

The DocBook Technical Committee will meet on Wednesday,
16 December 2015 at 2:00pm ET for 90 minutes.

#########################
NOTE THE NEW MEETING TIME
#########################

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: 20 January 2016
4. Review of the agenda.
5. Review of open action items

    a. Norm to review the non-normative XML Schema version of 5.1
       to make sure it has all the latest changes.

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):

       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)
     306            Allow Block Elements inside abstract

     Github Issues
     6              Add buildtarget element
     7              Allow revnumber inline.

  No new RFEs

-----

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

--

-- 
Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Peter Fleck | 23 Nov 10:27 2015
Picon

RDFa Lite Attributes in Docbook 5.1

Hi all,

I would like to populate my HTML output with Schema.org.

I've  been able to modify the inlines for obvious things like emails etc 
but at the block level I need to add the appropriate RDFa Lite 
Attributes to the XML (indicated here - 
http://www.docbook.org/tdg51/en/html/ref-elements.html#common.attributes).

My question is how to get the RDF attributes passed through to the HTML. 
Do I need to write a customization or is there a more obvious way?

Many thanks,

Peter
Stefan Knorr | 19 Nov 12:32 2015
Picon

What is the use of allowing variablelists within variablelists?

Hi all,

Tom (CCd) and I were wondering about a quirk (?) in the DocBook 5 
schema:
What is the rationale for allowing the following construct?

  <variablelist>
    <variablelist>
  [...]

(The same works for other kinds of lists within variablelist.)

Regards,

Stefan.

---                                                                    .
SUSE Linux GmbH, Geschäftsführer: Felix Imendörffer, Jane Smithard,
Graham Norton. HRB 21284 (AG Nürnberg)

Gmane