Bruno wrote:
> Changing and adapting the DTD to your domain is the big idea of DITA
> (IBM). It is time consuming (and why I choose Docbook) but it may be THE
> solution before XXE implement a GUI work arround.
I've tried DITA on XXE with good success just using the CSS stylesheets
from the DITA toolkit. For a given specialization, you can create a CSS
stylesheet of "delta rules" that imports its predecessors in the
specialization hierarchy, and thus inherits support for previous element
classes--see concept.css in the toolkit as a simple 2nd generation example.
DITA starts with fewer elements than DocBook, but adding new
specializations has the effect of increasing the number of elements in the
selection pulldowns, so DITA specializations also can benefit from
Hussein's suggested method of suppressing elements from view.
While it is useful to hide elements as a "training wheels" stage of
introducing writers to a new DTD, imagine the astonishment of a new user
who attempts to load an existing document that already contains "hidden"
elements and finds that he cannot use the insert menus to replicate what he
already sees as existing and valid markup examples. Hussein, you might
consider providing a way that a user can switch the editor between full and
hidden UI views, short of requiring an editing change to the configuration.
Regards,
--
Don Day <dond at us.ibm.com>
Lead DITA Architect
IBM Solution Technologies, Austin TX
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20040205/3b7299c8/attachment.htm
