Technical Writing and Localization

Writers who write technical documents for the location should pay much more attention to the verb and the active voice. These authors should also focus on the rules that allow translators to match the original in intention and structure and to minimize the cost of these translations in the process. When I researched articles and books on writing for the location , I found an interesting fact. Accordance with the rules of the location is usually best document in English.
Some basic guidelines
If you are serious about writing for the location, get this book , The Global English Style Guide : Writing clear , translatable documentation for a global market . Until the book , here are some guidelines to get you started:

    
Use short sentences . Avoid chained clauses or phrases.
    
Reuse or repeat whenever possible language : keywords , terms , notes and warnings.
    
Avoid using words that have more than one meaning.
    
Use names as nouns and verbs as verbs.
    
Use " that" in all the places you've learned not to use the word "only" . The withdrawal "that" as we have learned in Freshman English only more difficult and subjective translations .
    
Avoid idioms . Promote use a common dictionary.
    
Provide clear instructions for translation agencies . Make sure everyone is on the same page.
It should be simple with short sentences
It is always a good writing technique . I found that when I'm writing a concept and the concept can not be framed , I probably need to break the mind into two or more sentences . It's like trying to put 10 pounds of stuff in a 5 pound bag .
Note that the structures of sentences, even thought structures are not the same worldwide . If you want a more direct translation possible, do not use a sentence structure that is predominant in English only. You can easily disable .
according verbiage
This is a great rule because it allows translation allows readability in any language, and saves on the cost of translation. Obviously , the same words to all the controls on the user interface or the technical terms are used , but if you start most of its interface with the same phrase : " In the tasks in the command bar , select ... "O" in the main window , select ... " you just made the author's work easier , Working easiest translator , the user experience easier to read , and you will not have to pay for many" similarities " .
This is true for all words , phrases , paragraphs, such as notes, cautions and warnings , or constantly repeated and reused items. Repetition also puts the emphasis where it belongs : on the content.
Idioms for the idiomatic
Some idioms and idiomatic expressions are so ingrained in our culture that we have become aware that they are idioms . My best recommendation is to become aware . Some examples of words and phrases below:

    
baseline
    
mostly
    
keep in mind
Furthermore, the use of a word that has several meanings in the English language:

    
" Because" when you really mean " because."
    
" Understand " when you mean "determine" .
Rules for Translation Agency
Consistency rules recur and also set realistic expectations for your translated documents. In most cases, you do not want an interpretative translation of technical equipment . This means that you want your translation to fit the form and function of their tasks , concepts and reference copy . I do not know how it was all up to a translation agency , translation agency , usually reliable , totally botched the translation of our DITA XML files newly created . They had done very well with the copies of the test and in all languages ​​, but most complete records have been returned to them to fix .
First, they said they could handle DITA XML when not really know what it meant. Using the translation tool would have been simple. Pele expression , check the context , translate, put it back , no problem . Right? Oh, and validate the constructed against a DITA document type file ( DTD). Menucascade DITA is an element that allows you to enter a menu item > menu structure > Menu.
For example, select File> Print. Some files are returned to " Choose Print from the File menu. " It's not so bad. However, some of them were 3-level waterfalls and reads like a spaghetti when they were translated. But worst of all, he broke the code.
Another example of the interpretive translation occurred in the German translation . We noticed that some words were partially rendered in bold. We use bold for controls and selectable windows user interface . Translation agency has provided a translation of the results window and " Ergebnisfenster . This did not work for us style wise . Other translations of other German organizations were checked and found that the standard was " Fenster Ergebnis .
These are just some examples of agreements that you should do before going too far with the translations. Suggested actions include:

    
Rent very good proofreaders to check your translation against the original documents in English.
    
Keep track of any and all differences between expectations and translated documents . Use this list to each new project with each new translation agency.
    
Create a glossary of terms. It is an absolute necessity for most translation agencies .
    
Relax, have fun . It's easy .

No comments:

Post a Comment