Re: Upgrading to Docbook 4.3

Stefan Neufeind wrote:

But I strongly suggest we keep them (well, was there ever a real discussion about this?). For sure, we need to evaluate how e.g. OOo can handle them when editing. But there are many cases where they definitely make sense - especially for translation, URLs (consistency), readability etc. My comparison with text macros is a possibility how to deal with OO: We could have an 'checkout'-script which

evaluate entities to 'plain' XML (including keeping the entity itself enclosed in a XML comment). In OO you use macros for setting entities like 'deprecated'. In a commit-script the macro is transformed into the real entity and the 'plain' XML entities are replaced by the original entities in the XML comments. IE: a document in cvs ------------ blabla &type.bool; blabla ------------ --> checkout.php ------------ blabla <!-- DOCBOOK_ENT &type.bool !>boolean<!-- </DOCBOOK_ENT> blabla ------------ in OpenOffice a macro 'titel.deprecated'' creates something like ------------ blabla <!-- DOCBOOK_ENT type.bool !>boolean<!-- </DOCBOOK_ENT> blabla more text ... <!-- DOCBOOK_ENT title.deprecated !>Deprecated<!-- </DOCBOOK_ENT> ------------- -> commit.php ------------- blabla &type.bool; blabla more text ... &title.deprecated;