Looking for a useful DocBook XML editor, I came across XXE which is not Open Source, but freely available as a “standard edition”. Definitely worth to give it a try.

Bob Stayton has released DocBook XSL: The Complete Guide, an online book covering “all aspects of DocBook XML publishing tools, including installing, using, and customizing the XSL stylesheets and processing tools.”

via Michael Smith, xmlhack

Volker John just arrived at LinuxTag. We started talking about our installer and Conesys, then Christian Egli popped in and asked a question about my Open Office Doc Book tutorial. While discussing a solution to the problem, Volker pointed me to his presentation Using Open Office for ETDs. There you’ll find some more infos on using DocBook in Open Office. Finally, Christian and Volker started their engines (notebooks) and started playing with OOo.

That’s what I love about LinuxTag: people meet, people solve concrete problems, on the spot, find new infos, learn some more - and enjoy the great atmosphere.

UPDATE:

Note that my tutorial is about 1.1beta1, Volker’s about 1.1beta2 which is easier to handle in respect to DocBook.

Rasmus is in favour of a Web app for the PHP documentation group. “Let’s give it a try”, he said at the PHP documentation group meeting at LinuxTag. Christian from Bitflux and me will see how the Bitflux Editor Next Generation can be used for Mozilla-based online translation of the manual inside of a Web app that fits the workflow requirements of the PHP documentation group (sepcifically the synchronisation of CVS and documentation Web app).

UPDATE

Just talking to Goba at LinuxTag, he sits next to me (hi :). These are the points we have to take care of:

- URLs are referenced with entities anywhere in the DocBook XML, see http://cvs.php.net/co.php/phpdoc/entities/global.ent?login=2&r=1.120

- some more entities are used for ready made paragrpahs (e.g. “This function is experimental…”), see http://cvs.php.net/co.php/phpdoc/en/language-snippets.ent?login=2&r=1.55

- taking a look at Livedocs, we should take care that we use the css definition attributes created by the PHP parsing the DocBook XML to format output in BXE NG

- browsing in the document is provided via Livedocs ToC. The idea is that translators choose a page from the ToC, and click on “edit” at the page. Then BXE NG will pop up an everything will be fine

UPDATe

Christian has a blog entry on this topic, too.

Lars wrote a great blogpost [1] on creating two columns output from DocBook in PDF.

[1] http://trieloff.net/docbook/archive/000365.html

Just found this weblog with a category on DocBook [1] and some very interesting entries by Lars Trieloff. Lars, why didn’t you tell me?

[1] http://trieloff.net/docbook/archive/cat_docbook.html

Sandro has written a tutorial [1] on OpenOffice with examples and discussion of the DocBook export filter. In general, he takes a look at OpenOffice Writer and its capabilities to serve as a WYSIWYG editor for DocBook XML.

[1] http://www.zzoss.com/projects/oowdbk

OpenOffice [1] 1.1 beta now supports DocBook [2] Import/Export as indicated by the feature list [3].

[1] http://www.openoffice.org
[2] http://www.docbook.org/
[3] http://www.openoffice.org/dev_docs/source/1.1beta/features.html

1dok.org[1] works on an open standard for free and unimpeded exchange of electronic documents via internet.

[1] http://www.1dok.org/eng/index.html

In case you haven’t already heard: The OASIS standardization organization founded a TC to create an open, XML-based file format specification for office applications.[1]

[1] http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office