For some time now, machines have been constructed and built using modules. i.e. encapsulated and reusable standard components. In manuals, the modular approach has only slowly been gaining acceptance. With XML and a wide variety of editing tools, the technical prerequisites for the change are by now only a matter of the individual requirements – a right solution can be found for virtually every purpose. But for technical communicators the question arises what needs to be considered when texting under these changed conditions. This language tip is intended to be a basic aspect: how can one determine whether a text component is suited as a module?
Nickl, Markus. tekom (2005). Articles>Language>Technical Writing
Practical Tips for Language: The Ladder to the Top
We the Technical Editors are spared of one worry which our colleagues from journalism generally have: In our work we need not pay 'so much' attention to 'as much as possible' large number of editions. But the situation is different, if we--as is always the case--are to also look after the company's web presence. What is an edition in the context of printing is here the so-called 'page ranking' among the major search engines like Google and Yahoo. Many imagine that a listing in the hits lists depends on chance or, that it is mainly due to some technical means. That is all wrong: by employing some clever textual work the chances of web pages being found can be significantly increased. In reality, even elaborate techniques can lower the chances of hits: Frames, JavaScript and Flash Intros often derail the search engines. And the results may look all right, but regrettably the page will no longer be found.
Nickl, Markus. tekom (2006). Articles>Language>Editing>Business Communication
There are 18 readers currently online: 1 registered user and 17 guests. Register.

![]()
![]()


![]()
![]()
![]()