|
Short Introduction on
Translation, Writing and Editing |
Professional and skilled translators know it well: Translation is not
merely a word-for-word conversion of the source language; it is also a
writing and editing task, even in a very technical field like
computing. Editing/reviewing the "raw" translation and making it
suitable for the location concerned is an important step in the L10n
process.
In fact, the translator's role can be summarized as two key points:
A motto: Make the work of the reader/user easier.
A goal: Facilitate the use of the product concerned while adapting the
source text to the needs of the target audience.
To achieve these aims, it is important to follow some common and
standard rules
for translating the GUIs, help systems and documentation into the
target
language: The terminology must be kept consistent and the language
style must
be suitable for the locale. In relation to these two concerns, Sun
provides access to its terminology tool
SunGloss as well as its
Language Style Guides.
Good style is an essential part of efficient communication: Product
translations written in language that meets the expectations of the
reader/user reduce the review work required and minimize support needs.
In fact, an accurate and well-translated document (product) is a
document
that appears to have been written in the native language of the
reader/user
from the outset. Accurate and functional documentation that permits
the user to master the product in question quickly and efficiently
achieves
one important result: User satisfaction.
In this sense, the "writer-translator" should possess the skills
required
to convey information and instructions to the user according to certain
principles resulting in clarity, accuracy and readability.
In your role as writer-translator, you must transfer information to the
readers/users in such a way as to give them complete confidence in your
mastery of the subject matter.
Many Sun products and documents are highly technical. Some are aimed
at end users who may have very little knowledge of and skills in the
use of the software; others are intended for readers/users who are
experts
in the subject. The translator is therefore confronted with the
following
tasks:
- understanding the source document and transferring information
with clarity and accuracy;
- clear and concise writing in the target language;
- due consideration of the level of technical knowledge of the
reader/user;
- use of style and terminology in line with the expectations of the
reader/user.
Information should be imparted with clarity and without any ambiguity;
the tone should be neutral and rigorous; the style should be simple
and direct, and immediately understandable to the user who wants to
proceed with an installation and work with the product in question
without wasting any time, or is seeking a fast solutions to a
specific problem.
Respect for some basic rules of technical writing in the target
language is a crucial aspect of the role of the "writer-translator":
- direct expression: use of the affirmative rather than the
negative in grammatical structures;
- compliance with correct grammar and syntax rules;
- use of the active voice instead of the passive, and the
indicative
case rather than the subjunctive;
- simple sentences that avoid repetition and redundant expressions;
- attention to punctuation and typographical rules;
- limitation of the use of colloquial language (slang);
- use of English words and business jargon only if they are more
commonly used than neologisms in the subject concerned;
- terminological accuracy and consistency.
Technical translation is not something to be done in isolation: Other
translators can surely prove to be a great help, and multiple opinions
are the guarantee of a certain objectivity, for instance with regard to
the use of terminology and phrasing.
In addition to this, it's highly recommended to work with a proofreader
or writer who will read the translation from the user's perspective and
provide comments and feedback to enhance the final text. In a spirit of
professionalism, translators are aware of the advantages offered by
the feedback of the proofreader who is, in a sense, the first "user"
to be faced with the translation.
With this in mind, Sun's in-house linguists invite everyone to work
together dynamically, to be proactive. Don't hesitate to get in touch
with them if you have any doubts, or need advice and answers to your
questions. Together, it's easier to decide on the terminology or style
to be used, and they'll work with you in defining and managing the
terminology.
If questions or doubts arise about the context of the source text,
ask developers and engineers for more explanation. In terminology
matters, they can be an excellent aid to understanding an underlying
concept in order to get the right interpretation (i.e. the right
translation), as well as for decisions like whether or not to
translate specific words and expressions.
For releases of Sun products, Sun's in-house linguists perform a
linguistic review of the final translations. During this review
cycle, they scrutinize the target language to verify the accuracy of
the
transferred information, whether Sun's terminology has been followed,
whether the translation is consistent and, of course, the correctness
of
generic language aspects (grammar, spelling, syntax, etc.). Their
feedback
and recommendations, and the interaction between you and them, will
help
you finalize your work and deliver high-quality translations.
Finally, it is highly recommended to regard language manuals (official
dictionaries, grammars) as your best friends during the translation
cycle. It's preferable to verify a word twice than write it incorrectly
because you mistakenly think you know how it's written...
If you would like to share your opinion regarding the content
of this page, please
contact
the Open Translation team.
