<!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>Exporting Text Fonts</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_topic5" id="xps10_pagetitle">Exporting Text Fonts</div>
      <hr noshade="true">
      <p class="para_topic">Keywords related to text font mapping are ignored when exporting a CGM interactively and 1 Cals, 4 Cals or UG Fonts is chosen for the Fonts option in the Export CGM dialog. Thus, these keywords are only honored when, (a) the Default File is chosen for the Fonts option, or (b) when exporting a CGM through the Open C and C++ API, or (c) when importing a CGM, interactively or through the Open C and C++ API.</p>
      <p class="para_topic">When exporting a CGM these keywords ultimately determine the collection of font names exported with the CGM Font List element. The CGM Font List is initialized with the 4 Cals set of fonts. If the CGM Defaults File does not exist or cannot be read, or if it does not contain any text font mapping keywords, the 4 Cals set will be used. Otherwise, the keywords below effectively override this initial list.</p>
      <p class="para_topic">Note that these keywords only affect how exported text is represented when the Text Selection option is set to Text. Text rendered as Polylines is not affected.</p>
      <p class="para_topic">EXPORT_UG_TEXT_FONTS</p>
      <p class="para_topic">This keyword only applies to exporting a CGM. The effect is to cause all UG fonts presently being used in the part to be exported to the CGM. That is, the names of the UG fonts in the part will be listed in the CGM Font List element. This is most desirable if you intend to import the CGM back into Unigraphics NX.</p>
      <p class="para_topic">NO_TEXT_FONT_MAPPING</p>
      <p class="para_topic">This keyword is superseded by EXPORT_UG_TEXT_FONTS as of version 14.0. It is functionally identical.</p>
      <p class="para_topic">EXPORT_TEXT_FONT ALL_UG_FONTS destination_font</p>
      <p class="para_topic">This keyword only applies to exporting a CGM. Using this keyword causes all UG fonts in the part to be mapped to the destination_font.</p>
      <p class="para_topic">EXPORT_TEXT_FONT UG_font destination_font</p>
      <p class="para_topic">This keyword only applies to exporting a CGM. The usage of this keyword causes the specified UG_font to be replaced by the destination_font in the CGM Font List. If the UG_font does not presently exist in the part, this request is ignored.</p>
      <p class="para_topic">TEXT_FONT_MAPPING</p>
      <p class="para_topic">This legacy keyword accepts the same options as EXPORT_TEXT_FONT, and is functionally equivalent to it except that it is also used to specify how text fonts are to be imported. Because of the possible ambiguity this could introduce, usage of this keyword is discouraged.</p>
      <p class="para_topic">Note that the above keywords are applied in the order in which they occur in the CGM Defaults File, so they can effectively be used in combination. Consider, for example, the following sequence:</p>
      <p class="para_topic">EXPORT_UG_TEXT_FONTS</p>
      <p class="para_topic">EXPORT_TEXT_FONT  BLOCKFONT  AURORA</p>
      <p class="para_topic">These commands first load the CGM font list with the fonts currently in the part's Font Table Entity. Then all uses of BLOCKFONT are replaced by AURORA.</p>
   </body>
</html>