Thomas Schraitle | 28 Apr 10:15 2016
Picon

Add "danger" to the list of possible admonitions?

Hi,

a DocBook writer asked me why there is no "danger" element in DocBook.

Currently, we have tip, note, important, warning, and caution as
admonition elements. The list is sorted from lowest to highest
"severity".

However, for writers who want to give a warning about deadly
consequences, caution seems to me a bit "tame". ;)

Although I'm a bit hesitant to add new elements to the DocBook schema,
maybe we should consider that. The element danger would also fit better
to the ANSI standard (I think it was Z535, right?).

What do you think?

--

-- 
Gruß/Regards,
    Thomas Schraitle
Hussein Shafie | 22 Apr 17:22 2016

Release of XMLmind XSL-FO Converter v5.4.1

Release of XMLmind XSL-FO Converter v5.4.1.

Highlights:

- XMLmind XSL Utility and XMLmind XSL Server: updated several software 
components Apache FOP 2.1, DocBook XSL stylesheets 1.79.1, XMLmind DITA 
Converter v2.6, etc.

   Latest version of XMLmind DITA Converter adds partial DITA 1.3 
support to XMLmind XSL Utility and XMLmind XSL Server. Full DITA 1.3 
support is planned for year 2016. More information in "About DITA 
support in XMLmind DITA Converter" 
(http://www.xmlmind.com/ditac/_distrib/doc/manual/dita_support.html).

- XMLmind XSL-FO Converter engine: better support of East Asian (CJK) 
fonts. See "Special support for East Asian fonts" 
(http://www.xmlmind.com/foconverter/_distrib/doc/user/implementation.html#east_asian_fonts).

Download Evaluation Edition: 
http://www.xmlmind.com/foconverter/downloadeval.shtml

---------------------------------
What is XMLmind XSL-FO Converter?
---------------------------------

XMLmind XSL-FO Converter (http://www.xmlmind.com/foconverter/) is an 
XSL-FO processor similar to Apache FOP, RenderX XEP or Antenna House XSL 
Formatter, except that it generates RTF, WML, ODT and DOCX file formats 
rather than PDF.

(Continue reading)

Bob Stayton | 18 Apr 23:34 2016
Picon

DocBook Technical Committee Meeting Agenda: 20 April 2016

DocBook Technical Committee Meeting Agenda: 20 April 2016
=============================================================

The DocBook Technical Committee will meet on Wednesday,
20 April 2016 at 2: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 May 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.
(Continue reading)

Hussein Shafie | 11 Apr 10:49 2016

[ANN] Release of XMLmind XML Editor v6.7

Release of XMLmind XML Editor v6.7

Highlights:

- Enhanced "DocBook v5.1 configuration (Release Candidate)" add-on.

- Improved XInclude 1.1 support in DocBook v5 and v5.1 configurations.

- Partial DITA 1.3 support. Full DITA 1.3 support is planned for year 2016.

- Drag&drop of document tabs and tool tabs.

More info in http://www.xmlmind.com/xmleditor/changes.html

Home page: http://www.xmlmind.com/xmleditor/
Doug Smythies | 23 Mar 19:17 2016
Picon

When compiling PDF, relative paths no longer work (Ubuntu serverguide)

Hi,

I tried asking for help on your IRC channel, and got no reply, so trying here.

Using a Ubuntu 16.04 server, I am attempting to compile the preliminary Ubuntu 16.04 Server guide, for
preliminary publication on
help.ubuntu.com.
The build is failing to find the included png image files, used to indicate an inset  "Note" or "Warning" or
whatever, and the
resulting PDF file is missing these icon indicators.
Note that these icons inclusions are not something new, and has always worked in the past. i.e. compiling
with a 14.04 server.
I can get the compile to work properly by changing from relative to absolute paths in the file that defines
this stuff, however that
is not a practical long term solution. 

I think, but am not sure, the problem is in the docbook.xsl package.

I am looking for help to identify the root issue and push for a solution or to come up with a viable workaround solution.

References:
https://bugs.launchpad.net/serverguide/+bug/1559783

Versions of docbook related stuff:
docbook        4.5-5.1ubuntu1    standard SGML representation system for technical documents
docbook-dsssl  1.79-9      modular DocBook DSSSL stylesheets, for print and HTML
docbook-utils    0.6.14-3ubuntu1    Convert DocBook files to other formats (HTML, RTF, PS, man, PDF)
docbook-xml    4.5-7.3  standard XML documentation system for software and systems
docbook-xsl      1.79.1+dfsg-1   stylesheets for processing DocBook XML to various output formats

(Continue reading)

Bob Stayton | 16 Mar 21:27 2016
Picon

DocBook Technical Committee Meeting Minutes: 16 March 2016

DocBook Technical Committee Meeting Minutes: 16 March 2016
=============================================================

The DocBook Technical Committee met on Wednesday, 16 March 2016.

1. Roll call

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

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

3. Next meeting: 20 April 2016

No regrets.

4. Review of the agenda.

No additions.

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

    b. Norm to check what "independent implementations" means in
       this context.
       COMPLETED

(Continue reading)

Bob Stayton | 14 Mar 19:50 2016
Picon

DocBook Technical Commitee Meeting Agenda: 16 March 2016

DocBook Technical Committee Meeting Agenda: 16 March 2016
=============================================================

The DocBook Technical Committee will meet on Wednesday,
16 March 2016 at 2: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: 20 April 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.
(Continue reading)

stressware | 27 Feb 23:51 2016
Picon

Licencing


There are entity (.ent) files copyrighted by OASIS under the
following licence:

  Permission to use, copy, modify and distribute this entity set
  and its accompanying documentation for any purpose and without
  fee is hereby granted in perpetuity, provided that the above
  copyright notice and this paragraph appear in all copies. The
  copyright holders make no representation about the suitability
  of the entities for any purpose. It is provided "as is" without
  expressed or implied warranty.

But the files say they are derived from files under this licence:

  Copyright (C) 1986 International Organization for Standardization
  Permission to copy in any form is granted for use with conforming
  SGML systems and applications as defined in ISO 8879, provided
  this notice is included in all copies.

Did OASIS get permission to relicence the files, or think that the
derivation was trivial enough to not matter? By just looking at
the licence information of the files, it seems they are violating
the copyright of the original files.

There is also the fact that the original licence only gives
permission to copy for use 'with conforming SGML systems and
applications', so if DocBook does not conform to SGML, it would
also be a licence violation.

An example file is attached.
(Continue reading)

Phillip E. Gardner | 26 Feb 19:12 2016

using both DocBook Publisher and technical markup

I am trying to write a document using DocBook Publisher markup which also contains some of the technical markup.

In "DocBook Publisher:  The Definitive Guide" by Norman Walsh, it says "it is very easy to add elements back
into a customization of the Publishers schema.  For example, if the elements in the programming module
were needed, it is very simple to use an include statement for the programming.rnc file from the source
DocBook distribution."

My customization is

<grammar ns="http://docbook.org/ns/docbook" xmlns="http://relaxng.org/ns/structure/1.0">
<include href="/Users/gardner/Dropbox/Library/xml/docbook/5.1CR3/rng/publishers.rng"/>
<include href="/Users/gardner/Dropbox/Library/xml/docbook/stylesheets/docbook-xsl-ns-1.78.1/slides/schema/relaxng/programming.rng"/>
</grammar>

Note that the only place I could find the schema for programming was in the slides stylesheet directory; so,
maybe that is the problem.  If so, where is the file that I need?

When I use jing to validate, I get these
errors:

/Users/gardner/Dropbox/Library/xml/docbook/stylesheets/docbook-xsl-ns-1.78.1/slides/schema/relaxng/programming.rng:913:37:
error: reference to undefined pattern
"db.rep.attribute"
/Users/gardner/Dropbox/Library/xml/docbook/stylesheets/docbook-xsl-ns-1.78.1/slides/schema/relaxng/programming.rng:523:37:
error: reference to undefined pattern
"db.package"
/Users/gardner/Dropbox/Library/xml/docbook/stylesheets/docbook-xsl-ns-1.78.1/slides/schema/relaxng/programming.rng:58:33:
error: reference to undefined pattern
"db.parameter"
/Users/gardner/Dropbox/Library/xml/docbook/stylesheets/docbook-xsl-ns-1.78.1/slides/schema/relaxng/programming.rng:327:44:
(Continue reading)

Matthias Apitz | 25 Feb 21:04 2016
Picon

dbl1mn.ent: "1058" is not a character ...


Hello,

I'm new to this list and have zero knowledge about DokBook at all. I
subscribed because I'm a maintainer of a port in FreeBSD which compiles
some piece of software using DokBook for the manuals. See:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207299
for more background.

The make process spills out a lot of error messages, like:

docbook2ps -d ../stylesheet.dsl manual-en-sed.sgml
Using catalogs: /usr/local/share/sgml/catalog
Using stylesheet:
/usr/ports/print/muttprint/work/muttprint-0.73/doc/manual/en/../stylesheet.dsl
Working on:
/usr/ports/print/muttprint/work/muttprint-0.73/doc/manual/en/manual-en-sed.sgml
jade:/usr/local/share/sgml/docbook/dsssl/modular/print/../common/../common/dbl1mn.ent:8:28:E:
"1058" is not a character number in the document character set
jade:/usr/local/share/sgml/docbook/dsssl/modular/print/../common/../common/dbl1mn.ent:9:28:E:
"1090" is not a character number in the document character set
jade:/usr/local/share/sgml/docbook/dsssl/modular/print/../common/../common/dbl1mn.ent:10:28:E:
"1061" is not a character number in the document character set
...

If one looks into the referenced file dbl1mn.ent it looks like this:

<?xml version="1.0" encoding="US-ASCII"?>
<!-- This file is generated automatically. -->
<!-- Do not edit this file by hand! -->
(Continue reading)

Bob Stayton | 24 Feb 20:52 2016
Picon

DocBook Technical Committee Meeting Minutes: 24 February 2016

DocBook Technical Committee Meeting Minutes: 24 February 2016
=============================================================

The DocBook Technical Committee met on Wednesday,
24 February 2016 at 2:00pm ET.

1. Roll call

Present: Scott Hamilton, Larry Rowland,
Bob Stayton, Dick Hamilton

Regrets: Norm Walsh

Absent: Jirka Kosek

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

3. Next meeting: 16 March 2016

Norm could not attend and provide news about the adoption process
for DocBook 5.1.  The Committee decided to carry out the adoption
process through email.

Bob will contact Norm requesting an update on the status of
DocBook 5.1, and invite him to give us guidelines for further
actions.

-----

[1] https://lists.oasis-open.org/archives/docbook-tc/201601/msg00002.html
(Continue reading)


Gmane