This is the fourth “candidate release” of Docbook 5.0.

Last month we achieved our “feature freeze” milestone. We incorporated the following fixes and enhancements into DocBook V5.0CR4:

  1. Fixed RFE 1708032: Pattern naming inconsistency; changed db.href.attribute to db.href.attributes.

  2. Fixed RFE 1700154: Added sortas to <termdef>.

  3. Fixed RFE 1686919: Added an NVDL rules file.

  4. Fixed RFE 1705596: Aded db.programming.inlines (<classname>, <exceptionname>, <function>, <initializer>, <interfacename>, <methodname>, <modifier>, <ooclass>, <ooexception>, <oointerface>, <parameter>, <returnvalue>, <type>, and <varname>) to the content model of <code>.

  5. Fixed RFE 1689228: Fixed typo in Schematron assertion.

Please report any bugs that you find.

I also updated DocBook 5.0: The Definitive Guide to reflect these changes.

The next stop, possibly as early as June, is the 5.0 official release. You know all that testing you've been planning to do? Now's the time!

Comments:

Is there any chance of changing the names of the elements "firstname" and "surname" to "givenname" and "familyname" respectively to be culturally more neutral?

You may laugh at me, but because of these two elements, I still hesitate to use DocBook. Otherwise, it's an amazing XML application.

Posted by Potential user of DocBook on 09 Aug 2007 @ 07:46am UTC #

The "givenname" and "familyname" suggestion makes a lot of sense. In Chinese for example, the family name comes first so "firstname" is confusing.

Posted by Ken Morse on 10 Aug 2007 @ 11:54am UTC #
Add a comment or subscribe to (existing and future) comments on this essay.
Name:
Email*:
 *Please provide your real email address; it will not be displayed as part of the comment.
Homepage:
Comment**:
 **The following markup may be used in the body of the comment: a, abbr, b, br, code, em, i, p, pre, strong, and var. You can also use character entities. Any other markup will be discarded, including all attributes (except href on a). Your tag soup will be sanitized...