TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Hi, I attended a special lesson about preparing of texts (for translation, that is the topic, of course).
There are some rules.
1. Write short and concise.2. Use the same wording for the same content.3. Prepare a style guide. (This is what you actually do for this.)
But the original must be true and concise, of course.
I did not know the "combine not and words" part for asian language.
So I have to add: Do not forget the destination languages.
PS: For the original question, is there any context?
Steve Hudson <sh1448291904 -at- gmail -dot- com> schrieb am 0:26 Dienstag, 6.Oktober 2015:
If a target language is Asian, I would avoid the "not" versions of words.
Â - a is unable to do b * > * a is not able to do b
Â - x is unsuccessful * > * x is not successful
Many machine translations have difficulty associating the 'not' with the
correct word, and often end up missing the not altogether, which is very
There are also a bunch of other tips, such as being very rigid with the
order of time, place and so on, and keeping phrases punctuated and simple.
I noticed many of the replies were actually answering "Best way to write
this" and missed the "for translation"...
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com