<!DOCTYPE html
  PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!--
Copyright (c) 2006 UGS Corp.

All Rights Reserved.

This software and related documentation are proprietary to UGS Corp.
-->
<html>
   <head>
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <title>Localization and Internationalization</title>
      <script language="javaScript">
        abridged="false";
        displayConditions=new Array();
      </script>
      <link type="text/css" href="../css/main_styles.css" rel="stylesheet">
   </head>
   <body class="bodydocs" onload="top.pageLoader()" bgcolor="#FFFFFF">
      <div class="title_topic2" id="xps10_pagetitle">Localization and Internationalization</div>
      <hr noshade="true">
      <table cellspacing="4" align="center">
         <tr valign="top">
            <td bgcolor="#c0c0c0" colspan="1" rowspan="1">
               <p class="para_td"> <a class="links" href="javascript:void(0)" onclick="top.openFile('shared_func/tls_jrn_ov.html');return(false);">Overview</a></p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td"> <a class="links" href="javascript:void(0)" onclick="top.openFile('shared_func/tls_jrn_ht.html');return(false);">How To</a></p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td"> <a class="links" href="javascript:void(0)" onclick="top.openFile('shared_func/tls_jrn_op.html');return(false);">Options</a></p>
            </td>
            <td bgcolor="#f4f4f4" colspan="1" rowspan="1">
               <p class="para_td"><a class="links" href="javascript:void(0)" onclick="top.openFile('shared_func/tls_jrn_rt.html');return(false);">Related Topics</a></p>
            </td>
         </tr>
      </table><br><p class="para_topic">This topic explains how the system handles localization and internationalization issues in journals.</p>
      <div class="title_division">Journals</div>
      <p class="para_division">The system generated journals are Unicode (if you set journal preferences as such), which can handle any character in any language.</p>
      <div class="title_division">Commands</div>
      <p class="para_division">The commands that are recorded in a journal are always in English. Therefore, for example, a line is always of type &quot;Line&quot; and you create it using the &quot;CreateLine&quot; method.</p>
      <p class="para_division">If you are trying to use a string that contains characters other than the local language's character set, and a function is not yet able to internally process that string, the system generates errors at runtime that you can catch and display.</p>
      <div class="title_division">String Arguments</div>
      <p class="para_division">However, string arguments fall into one of three of the following categories: which correspond to NX internal processing.</p>
      <table cellspacing="0" align="center">
         <tr>
            <th bgcolor="#ffffff" colspan="1" rowspan="1" width="5%"></th>
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1" width="20%">
               <p class="para_th">String Characteristics</p>
            </th>
            <th bgcolor="#c0c0c0" colspan="1" rowspan="1" width="75%">
               <p class="para_th">Description</p>
            </th>
         </tr>
         <tr>
            <td colspan="1" rowspan="1" width="5%"></td>
            <td colspan="1" rowspan="1" width="20%">
               <p class="para_td">ASCII Text Only</p>
            </td>
            <td colspan="1" rowspan="1" width="75%">
               <p class="para_td">The only text that is limited to ASCII are filenames.</p>
            </td>
         </tr>
         <tr>
            <td colspan="1" rowspan="1" width="5%"></td>
            <td colspan="1" rowspan="1" width="20%">
               <p class="para_td">Local Language Only</p>
            </td>
            <td colspan="1" rowspan="1" width="75%">
               <p class="para_td">Some functions limit string arguments to the language in which NX is run. This is equivalent to the regional &quot;locale&quot; setting in the Windows Control Panel. For example, if your NX system is set to run in Greek, you can use Greek characters in your strings. However, you could not use Japanese characters. Most string arguments fall into this category. If you use a character string that doesn't match the current locale, the system either replaces each untranslatable character with a &quot;#&quot; or generates an error message, indicating the mismatch. Note: ASCII is always a subset of locale so English is always preserved. As NX matures, more and more functions move to the &quot;All Languages&quot; category (below).</p>
            </td>
         </tr>
         <tr>
            <td colspan="1" rowspan="1" width="5%"></td>
            <td colspan="1" rowspan="1" valign="top" width="20%">
               <p class="para_td">All Languages</p>
            </td>
            <td colspan="1" rowspan="1" width="75%">
               <p class="para_td"> Some functions fully support all languages. This allows you to use any language in any locale without restriction. For example, even if your locale is Greek, you could use Japanese text. This is because that particular call uses Unicode internally. This is supported in various places such as object attributes and Drafting.</p>
            </td>
         </tr>
      </table><br><div class="title_division">Comments and Variable Names</div>
      <p class="para_division">When editing a journal, you can use any language to enter comments or variable names.</p>
      <div class="title_division">System Generated Menu and Dialog Names</div>
      <p class="para_division">The system localizes menu and dialog names and other user interface elements that are written to the journal.</p>
   </body>
</html>