70 lines
4.5 KiB
HTML
70 lines
4.5 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="Development process" />
|
||
|
<meta name="abstract" content="Before you are ready to develop NLS-enabled applications, consider this information for a successful development process." />
|
||
|
<meta name="description" content="Before you are ready to develop NLS-enabled applications, consider this information for a successful development process." />
|
||
|
<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="rbagsdevelopmentprocess" />
|
||
|
<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>Development process</title>
|
||
|
</head>
|
||
|
<body id="rbagsdevelopmentprocess"><a name="rbagsdevelopmentprocess"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Development process</h1>
|
||
|
<div><p>Before you are ready to develop NLS-enabled applications, consider
|
||
|
this information for a successful development process.</p>
|
||
|
<div class="section" id="rbagsdevelopmentprocess__Header_518"><a name="rbagsdevelopmentprocess__Header_518"><!-- --></a><h4 class="sectiontitle">Education for developing internationalized
|
||
|
applications</h4><p>When you intend to develop NLS-enabled
|
||
|
applications, you need to consider additional initial education. The following
|
||
|
topics are important to learn about:</p>
|
||
|
<ul><li>General globalization concepts</li>
|
||
|
<li>Available globalization support on i5/OS™</li>
|
||
|
<li>Available globalization support on other systems and applications with
|
||
|
which your application operates</li>
|
||
|
<li>Isolation of different parts of an application</li>
|
||
|
<li>Data presentation corresponding to cultural conventions</li>
|
||
|
<li>Design and coding for textual data parts</li>
|
||
|
<li>Translation process</li>
|
||
|
<li>Product and system integration</li>
|
||
|
<li>Packaging, installation, and setup</li>
|
||
|
<li>Product support and maintenance</li>
|
||
|
</ul>
|
||
|
<p>Based on the globalization enabling guidelines, first prepare a prototype
|
||
|
application and test the chosen way of implementing the application for your
|
||
|
specific environment. Afterward include the globalization enabling guidelines
|
||
|
in your general application development processes, guidelines, and standards.</p>
|
||
|
</div>
|
||
|
<div class="section" id="rbagsdevelopmentprocess__HDRAPPIMPL"><a name="rbagsdevelopmentprocess__HDRAPPIMPL"><!-- --></a><h4 class="sectiontitle">Implementing internationalized applications</h4><p>When
|
||
|
implementing an internationalized application, the most important objective
|
||
|
is to produce only one set of running code. You must differentiate consistently
|
||
|
between running code and textual data. It is essential that you standardize
|
||
|
the chosen approach throughout the whole application. Work with unique and
|
||
|
clearly defined naming conventions. To understand and to maintain this information
|
||
|
in the application, handle parameters called from a program in a consistent
|
||
|
way.</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>
|