23.11.2013 Aufrufe

tekom-Jahrestagung 2012 - ActiveDoc

tekom-Jahrestagung 2012 - ActiveDoc

tekom-Jahrestagung 2012 - ActiveDoc

MEHR ANZEIGEN
WENIGER ANZEIGEN

Sie wollen auch ein ePaper? Erhöhen Sie die Reichweite Ihrer Titel.

YUMPU macht aus Druck-PDFs automatisch weboptimierte ePaper, die Google liebt.

Professionelles Schreiben / Technical Authoring<br />

TA 16<br />

Tutorial<br />

Crossing the divide – Advanced techniques<br />

for conversion to structured FrameMaker<br />

Jang F.M. Graat, JANG Communication, Amsterdam<br />

Most of the techniques that will be explained in this tutorial were developed<br />

in a project for one of my customers, who will be co-presenting<br />

that project with me in TA5: Changing the engine without stopping the<br />

car.<br />

Preparing the documents<br />

Some features of the unstructured FM interface do not translate well<br />

into the structured paradigm. In fact, some features break FM’s builtin<br />

conversion and cause a fatal crash. This means that such features<br />

have to be either removed or changed in such a way that FM can handle<br />

them properly.<br />

One particular case is anchored frames that contain text frames. In one<br />

project, such frames were used to place notes for the authors in the side<br />

heads. A script finds all occurrences of such constructions and moves<br />

the content into the main document, applying specific paragraph format<br />

tags so that they can be recognized for what they are. After conversion,<br />

the re-applied paragraph formats makes the notes appear in the side<br />

heads again.<br />

Another feature does not lead to crashes but offers an opportunity to increase<br />

the quality of converted materials: the use of different sidehead<br />

icons for different types of notes. If the images are linked instead of<br />

copied into the FM documents, their filenames can be used to apply new<br />

paragraph formats to the note texts. This allows distinguishing an „Info“<br />

note from a „Caution“ and „Warning“, or whatever note categories you<br />

may have. Again, after conversion, the icons can be brought back into<br />

the formatting (using a slightly different and easier to manage method).<br />

Conversion tables and their usage<br />

The information about creating conversion tables in FM’s documentation<br />

is more or less enough to do the straightforward conversion work.<br />

But the really interesting work starts where the documentation ends.<br />

Higher-level conversion rules can be applied until reaching the very top<br />

of the tree. The order in which certain rules are applied may become an<br />

obstacle if you do not have a clear idea of the structure that is inherent<br />

in the source document’s formatting.<br />

Creating complex expressions at higher-level rules can be made less<br />

error-prone by using variables for sets of elements that often appear<br />

together. You can go one step further by using text insets to create and<br />

manage a set of conversion tables: each conversion table being specifically<br />

optimized for one type of document. The tutorial, procedure and<br />

reference chapters may have different structures and can be converted<br />

using different conversion tables. Also, if you are a consultant like myself,<br />

you may want to use a number of modules that can be combined<br />

into a fitting conversion table for each particular customer, without having<br />

to copy and paste generic enhancements for often occurring formats<br />

and constructions.<br />

<strong>tekom</strong>-<strong>Jahrestagung</strong> <strong>2012</strong><br />

423

Hurra! Ihre Datei wurde hochgeladen und ist bereit für die Veröffentlichung.

Erfolgreich gespeichert!

Leider ist etwas schief gelaufen!