Keeping DITA simple
When thinking in terms of technical writing, one might at times confuse the people involved with documenting the software with those actually writing it.
Really Strategies provides comprehensive consulting and solutions for
DITA-based applications from specialists in DITA specialization design and implementation. Really Strategies' consultants are experts in the
application of DITA-based solutions for non-technical documentation
businesses (publishers, standards, business process documentation, etc.)
as well as for more traditional technical documentation applications.
J'ai commencé quelques didacticiels et visité FM7 et FM8, très peu, juste assez pour que je me concentre sur le contenu structuré. Il ya les composantes ouvertes qui concurencent FM mais c'est pas mal de taponnage à faire rouler. Saxon, OT1.4, FO, ,Java, Ant, RenderX, etc. Je jouais déjà avec ces outils avant, heureusement. Bref, je me suis plus orienté avec le open source et/ou les évaluations (FO- FOP).
The short description is an optional element in DITA, but it has powerful usability implications. Carefully-written short descriptions can help readers more successfully navigate information and locate topics that answer their questions. In addition, the act of crafting careful short descriptions can help writers clarify their understanding of the technical content. This session will cover how the content of the <shortdesc> element is displayed in various forms of output, such as PDF, Eclipse-based help, and Microsoft HTML Help.
Self on Help
When a DITA information set is transformed into a book, the deliverable is a self-contained. Its navigation devices (page numbers, TOC, index, cross-references) are constructed from the DITA source. Likewise, when a compiled Help deliverable is created, the navigation is constructed. However, a compiled Help file is typically read in a viewing program that allows full text searching; that form of navigation is provided by the viewing engine, and is not derived from the DITA source.