Online groups, autumn 2013

Writing for translation

A member asked how to tell a translator what text not to translate. For example, usually these types of content are not translated: samples of code, database table names, and file names. The member uses MadCap Flare. He does not use MadCap Lingo to prepare the content for translation ( Instead, he sends the MadCap Flare project to the translators.

With a termbase, you can specify the approved and the not-approved technical nouns and technical verbs. Possibly, a termbase is not sufficient. For groups of words and for sentences such as error messages, a translation memory system is necessary.

Possibly, use translation management software. An advantage of translation management software is that you can prepare the translation before you send it to the translator. Some examples:

Photographs for a manual

A member is writing a manufacturing manual for hardware. He must include photographs of the assembly process. Usually, the member uses either illustrations or a professional photographer, but for this project, he must take the photographs. During the assembly process, large items will be put on a workbench.

Members suggested this equipment:

When you take photographs, do these things:

US and UK software costs

Adobe Technical Communication Suite is more expensive in the UK than in the US. A member wants to know whether he can buy a US version of the software and use it legally in the UK.

Members gave many opinions. One member spoke to Adobe customer services, who gave this reply:

Other software companies sell the same software for different prices. In Australia, "pricing is such a source of contention within Australia that executives from Adobe, Microsoft, and Apple have been summoned to appear before Australian Parliament to answer questions specifically about pricing" (


RSS feed