89 lines
6.4 KiB
HTML
89 lines
6.4 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en-us" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow" />
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<meta name="DC.Type" content="concept" />
|
|
<meta name="DC.Title" content="Translation process" />
|
|
<meta name="abstract" content="Translating the textual data is a very time-consuming process. The textual data should be available to translators very early in the development stage, even before the code is stable. Consider the areas in this topic when planning for translation." />
|
|
<meta name="description" content="Translating the textual data is a very time-consuming process. The textual data should be available to translators very early in the development stage, even before the code is stable. Consider the areas in this topic when planning for translation." />
|
|
<meta name="DC.Relation" scheme="URI" content="rbagsdevelopingappsprocess.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="rbagstranslationprocess" />
|
|
<meta name="DC.Language" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|
<title>Translation process</title>
|
|
</head>
|
|
<body id="rbagstranslationprocess"><a name="rbagstranslationprocess"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Translation process</h1>
|
|
<div><p>Translating the textual data is a very time-consuming process.
|
|
The textual data should be available to translators very early in the development
|
|
stage, even before the code is stable. Consider the areas in this topic when
|
|
planning for translation.</p>
|
|
<div class="section" id="rbagstranslationprocess__Header_494"><a name="rbagstranslationprocess__Header_494"><!-- --></a><h4 class="sectiontitle">Physical equipment</h4><p>Each translator
|
|
should have equipment compatible with the language being translated. The display
|
|
stations and keyboards should have all the characters needed to translate,
|
|
and the printers should be able to print the translated text.</p>
|
|
</div>
|
|
<div class="section" id="rbagstranslationprocess__Header_495"><a name="rbagstranslationprocess__Header_495"><!-- --></a><h4 class="sectiontitle">Translation tools</h4><p>Provide the translators
|
|
with tools that increase productivity and that prevent translation of non-textual
|
|
application data. When purchasing or developing a translation tool, the following
|
|
features should be included:</p>
|
|
<ul><li>An editor that provides the ability to show displays that
|
|
can be seen by the user, and the ability to translate the textual data on
|
|
the system but still protect the parts of the application that are not textual
|
|
data. The editor should also include functions such as scan and replace, find,
|
|
copy, move, and delete.</li>
|
|
<li>A dictionary function to provide consistency of words and phrases throughout
|
|
the product.</li>
|
|
<li>A validation process to check translation errors that might cause the
|
|
application to malfunction.</li>
|
|
<li>A merge function that provides the ability to merge the translated text
|
|
into a new version of the original text. This merge function allows for translating
|
|
only new text, and saves time and effort.</li>
|
|
<li>A print function for validation purposes.</li>
|
|
</ul>
|
|
</div>
|
|
<div class="section" id="rbagstranslationprocess__Header_496"><a name="rbagstranslationprocess__Header_496"><!-- --></a><h4 class="sectiontitle">Translation education</h4><p>It
|
|
is important that translators are familiar with the product they are translating
|
|
and also with the tools they are using. The translation process is not the
|
|
replacement of one word with another, but the formation of concepts in another
|
|
language. Knowledge of the product being translated provides more understandable
|
|
products to the user. Time and resources for educating translators should
|
|
be planned well in advance.</p>
|
|
</div>
|
|
<div class="section" id="rbagstranslationprocess__Header_497"><a name="rbagstranslationprocess__Header_497"><!-- --></a><h4 class="sectiontitle">Translation guidelines and instructions</h4><p>Translation
|
|
guidelines and instructions should be provided to ensure correct translation.
|
|
For example, to translate an error message properly, it is important to know
|
|
in what context this message is displayed. A note to translators telling them
|
|
what error caused the message to be displayed also helps.</p>
|
|
</div>
|
|
<div class="section" id="rbagstranslationprocess__Header_498"><a name="rbagstranslationprocess__Header_498"><!-- --></a><h4 class="sectiontitle">Translation glossary</h4><p>To ensure accurate
|
|
translation, use terminology based on definitions in standard, widely available,
|
|
dictionaries. If your application uses terms not found in standard dictionaries
|
|
or terms that are used differently from standard definitions, provide a glossary
|
|
of non-standard terms to the translators. Avoid using abbreviations and acronyms
|
|
in your application. If you must use abbreviations or acronyms in your application,
|
|
define them in the glossary. Remember, abbreviations and acronyms that are
|
|
obvious in your language might not be obvious in another language.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbagsdevelopingappsprocess.htm" title="Before you invest your time and money into the development of globalized applications, you will benefit from a planning process that gives you an opportunity to consider how you can efficiently and effectively serve your users. The information in this topic will help you develop such a plan.">Goals and processes</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |