Joydeep Chakrabarty | 25 Jan 11:17 2015
Picon

Note Box

Hello all,

I have been trying to write a docbook file. I am using <note> element. 
But I cannot see the note box (or borders). What am I missing here? Here 
is my code.

<?xml version='1.0'?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
                   "http://www.oasis-open.org/docbook/xml/4.5/
docbookx.dtd">
<book lang="en">
<bookinfo><title>My first DocBook document</title></bookinfo>

  <chapter>
    <title>TEST DOCBOOK</title>
    <note>
        <title>This is Note</title>
        <para>This is test.</para>
      </note>
  </chapter>
</book>

Thanks.
Mary Connor | 23 Jan 22:49 2015

Easiest way to define ProductName variable?

I'm brand new to docbooks, having inherited it through this job I started. Now that I have my build scripts working, I'm in good shape, except that I've not yet figured out how best to achieve this simple goal: create a variable (such as ProductName) that can resolve to one of several values based on whether it's a corporate or an OEM build target.

I must not be searching on the correct words to find out how this is typically done!
Gratefully,
Mary
Richard Hamilton | 22 Jan 01:44 2015
Picon

Google Summer of Code 2015

At today's DocBook TC meeting, we discussed the possibility of applying to be a mentoring organization for
this year's Google Summer of Code.

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:
https://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2015/help_page

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

P.S. Sorry for the cross posting, but I wanted to make sure this gets out to the widest audience.
-------
XML Press
XML for Technical Communicators
http://xmlpress.net
hamilton <at> xmlpress.net
Bob Stayton | 22 Jan 01:08 2015
Picon

DocBook Technical Committee Meeting Minutes: 21 January 2015

DocBook Technical Committee Meeting Minutes: 21 January 2015
=============================================================

The DocBook Technical Committee met on Wednesday, 21 January
2015 at 1:00pm ET.

1. Roll call

Present: Dick Hamilton, 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: 18 February 2015

4. Review of the agenda.

Add Google Summer of Code.

5. Review of open action items

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

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

   c.  Bob to integrate publishers XSL into DocBook XSL.
       CONTINUED

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

   e.  Dick to complete copy edit of Jirka's Transclusion
       document.
       COMPLETED

6.  Publisher's and eLearning subcommittee reports

Nothing to report.

7.  XInclude 1.1 status.

Norm gave this status:

W3C Last Call Working Draft 16 December 2014

8.  Jirka's "DocBook Transclusions" document

Dick completed the copy edits which Jirka added into the
document. Jirka is working with Norm to get the new version
posted.

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

9.  DocBook 5.1 release

Norm was not present but had reported that he had
submitted the papers to Chet Ensign at OASIS.
Bob consulted with Chet, and then told Norm he needs to submit two
tickets to OASIS to submit the drafts.

ACTION: Bob to follow up with
   Norm to submit OASIS tickets for 5.1.

Scott made a request of the Oxygen developers to add a feature for 
managing DocBook Assemblies, similar to the one for DITA maps.
They will consider it.  Jirka said they are a sponsor of XML Prague 
taking place Feb 13-15, so he will talk to them there.

9b.  Google Summer of Code

Dick said we had a 50-50 chance of getting a project approved,
and this is the good alternate year for it.  He said we need project
ideas and mentors.

ACTION: Dick will post a request for GSOC ideas and mentors to
the DocBook mailing lists.

10.  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/201412/msg00012.html

--

-- 
Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Bob Stayton | 20 Jan 18:18 2015
Picon

DocBook Technical Committee Meeting Agenda: 21 January 2015

DocBook Technical Committee Meeting Agenda: 21 January 2015
=============================================================

The DocBook Technical Committee will meet on Wednesday, 21 January 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.

Agenda

1. Roll call
2. Accepting the minutes [1] of the previous meeting.
3. Next meeting: 18 February 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
       standard.

   c.  Bob to integrate publishers XSL into DocBook XSL.

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

   e.  Dick to complete copy edit of Jirka's Transclusion
       document.

6.  Publisher's and eLearning subcommittee reports

7.  XInclude 1.1 status.

8.  Jirka's "DocBook Transclusions" document

9.  DocBook 5.1 release

10.  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/201412/msg00012.html

--

-- 
Bob Stayton
Sagehill Enterprises
bobs <at> sagehill.net
Roland Mainz | 16 Jan 16:54 2015

Only resolve xincludes in a XML file ?

Hi!

----

Does anyone know a way to resolve all xincludes in a XML file only ?
The problem we have is that we have DocBook/XML manpages which share
some common content with other non-manpage documents but we like to
deliver the DocBook/XML manpage files as "standalone" versions to a
DocBook/XML-aware /usr/bin/man ...

----

Bye,
Roland

--

-- 
  __ .  . __
 (o.\ \/ /.o) roland.mainz <at> nrubsig.org
  \__\/\/__/  MPEG specialist, C&&JAVA&&Sun&&Unix programmer
  /O /==\ O\  TEL +49 641 3992797
 (;O/ \/ \O;)
Dan Shelton | 15 Jan 16:12 2015
Picon

Re: Restrictive Docbook XML editor which enforces Docbook schema?

On 15 January 2015 at 16:04, Franklin Einspruch
<franklin.einspruch <at> gmail.com> wrote:
> Emacs will do it. Well, you can create any tag you want, but the text goes
> red to let you know that validation is failing.

No, what I need is that users are completely prevented from creating
tags which do not belong there. No red text or something like that. We
need something which really prevents the creation in the first place.
>
> f.
>
> On Thu, Jan 15, 2015 at 10:01 AM, Dan Shelton <dan.f.shelton <at> gmail.com>
> wrote:
>>
>> Is there a Docbook XML editor which enforces the Docbook schema during
>> editing?
>>
>> I am looking for an editor which loads the Docbook XML schema and then
>> only allows the creation of tags which are allowed at the current
>> position in the XML document.
>>
>> Dan
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: docbook-unsubscribe <at> lists.oasis-open.org
>> For additional commands, e-mail: docbook-help <at> lists.oasis-open.org
>>
>

Dan
Gerard Nicol | 8 Jan 23:24 2015

Docbook Consultants

All,

 

Are there companies out there who provide Docbook consultancy services?

 

We are committed to using Docbook moving forward (compared to products like RoboHelp it is a no-brainer), but finding people with real Docbook experience is not simple.

 

In particular we are looking for assistance with customization, but we could also use advice on tools as we are currently evaluating editors.

 

If there is anybody out there with information, or who is interested in this work please feel free to email me directly.

 

Gerard Nicol

GazillaByte LLC

 

Jason Curl | 7 Jan 13:02 2015
Picon

Glossary linking not working as expected

Dear all,

I've managed to set up conversion of my DocBook 4.5 documents to HTML 
via the XSL scripts 1.78.1. My XSLT parser is Saxon 6.5.5 using Java on 
Ubuntu 11.10 (1.6.0_27 with OpenJDK).

However, using a glossary database results in the error (and no cross 
reference is set up):
   Error: no ID for constraint linkend: gloss.qnx

I've followed as best I can tell, 
http://www.sagehill.net/docbookxsl/GlossDatabase.html#LinksGlossCollection

I have in my "book" the text:
  <glossterm linkend="gloss.qnx">QNX</glossterm>
and at the end I have:
   <glossary role="auto">
     <glossdiv>
       <title>Dummy Glossdiv</title>
       <glossentry>
         <glossterm>Dummy Glossary Entry</glossterm>
         <glossdef>
           <para>This text should never appear</para>
         </glossdef>
       </glossentry>
     </glossdiv>
   </glossary>

In my glossary.xml I have the entry:
<glossdif>
   <title>Q</title>
   <glossentry id="gloss.qnx">
     <glossterm>QNX</glossterm>
     <glossdef>
       <para>A Microkernel from QNX Software Systems.</para>
     </glossdef>
   </glossentry>
</glossdiff>

I'm building on Linux and have set the parameter:
  java -cp ... com.icl.saxon.StyleSheet -o out.html in.html mycfg.xsl 
glossary.collection=/home/user/glossary.xml

At the end of the build, the term is in italics, and my book contains 
the glossary entry, but there is no link. This tells me that the 
parameter is correct (else the glossary should be empty) and that the 
conversion has reverted back to using the glossterm, not the linkend to 
the id in the external glossary database.

Putting the glossary.collection term in my config XSL doesn't work either.

How can I get a glossary database working so that linking works as 
expected? And on a lesser note, when I get that working, how do I change 
the default behaviour so that the link is not italics?

Thanks & Best Regards,
Jason.
Sascha Manns | 6 Jan 11:43 2015
Picon

Moving down the title block on titlepage

Hello list,

i'm using docbook with publican and customized xsl stylesheets. My used 
stylesheets are placed in 
http://bazaar.launchpad.net/~sascha-manns-h/+junk/publican-xcom/files/head:/xsl/.
The pdf.xsl is the mainfile like docbook.xsl.
Inside "book.titlepage.recto" i have placed a <xsl:call-template 
name="company.logo"/> which places my company logo on the titlepage. The 
pdf.xsl is the original one from publican and xcom.customized.xsl are my 
customizing stylesheet.
Actually i have the problem, that the titleblock is too close to the 
company logo. So i would like to place it in the middle of the site.

Maybe anyone can help me to fix this?

--

-- 
Yours sincerly

Sascha Manns
Gerard Nicol | 6 Jan 10:59 2015

Refentry in TOC

Hi,

 

I have a number of refentry sections in a book I am producing with DocBook.

 

I would like these headings to appear in the TOC, and I have been trying to follow the instructions at http://www.sagehill.net/docbookxsl/TOCcontrol.html

 

I have other overrides in my customization file, but this one has me struggling.

 

Does anybody have any working examples they would be able to share?

 

Gerard Nicol / CEO

gerard.nicol <at> gazillabyte.com

 

GazillaByte LLC

4600 S. Syracuse Street, Level 9, Suite 905, Denver Colorado USA

Cell +1-720-382-8560 / Office +1-720-583-8880

http://tapetrack.com

Languages English

 


Gmane