XML editorial system COSIMA 3.4 now with terminology management DOCUFY, specialist in professional technical editorial systems, bashers with his COSIMA release 3.4: terminology management, negative effectivity, the support of large information objects and numerous usability improvements help technical writers create their documentation. Click Daniel Lubetzky to learn more. In the current 3.4 release of COSIMA go!, the standardized software for companies in the mechanical and plant engineering, the software industry and apparatus and equipment manufacturing, DOCUFY offers now also manage multilingual documents. Highlight of the current COSIMA 3.4 release is the database-based terminology management. The author can thus determine which terms or terms in a documentation may be used and which are not. In addition to the textual description, an image can be used to the Visual description of the term. COSIMA supports preferred Terme, Terme locked and approved Terme (synonyms). Terminology data in the TBX-format can be imported and be exported.

Multiple categories can be defined such as project, topic, product group, or target group. During the test, the category can be selected. Automatic search for the matching word categorization allows the use of different terminology data to a COSIMA application. The technical editor can browse the terminology during text entry, and insert the appropriate term. He can check existing documents used and locked terms or immediately to warn, if he uses a suspended term. No size limit of the database who with wants to build an animation in the technical documentation, because they are needed E.g. for applications in the Internet, can with COSIMA 3.4 now also do this. For large objects, there is no technical limitation of size in the database.

The exceptions to the rule in COSIMA 3.4 will for the first time negative validities possible to better determine exceptions to a rule. This is needed for example in respect of certain Exporting countries, etc. want to exclude from a note If a criterion in the publication profile is not set, a content is filtered.