Eric Vaandering wrote: > Two questions: > > 1) Can I assume that someone that is familiar with latex will feel > reasonably comfortable with DocBook?
The markup is a bit different (obviously), but the idea of marking up for semantics rather than appearance is important and would transfer. > 2) Does DocBook have the ability to define and use variables, so we can > define a variable $PRODUCT such that PRODUCT=Mozilla and > PRODUCT=Netscape versions of the documentation can be easily produced > with the right subs everywhere? I think you said something about this in > your message above. Direct substitution like that can be easily done with Entites (just like l10n is currently handled in the chrome) so you'd have &product;, which would be replaced as stated above. The KDE documentation does this, as seen at http://i18n.kde.org/doc/markup/actions-and-commands.html (under the <application> tag header). I think, however, that we can do better. By marking up features of the browser in their own tags, it's conceivable that vendors can use an XSL sheet to filter out the features that their browser doesn't have. e.g. popup blocking is not a GUI element in NS7 PR1, so NS could filter that out without having to edit the doc. -- grayrest http://grayrest.com/moz
