Fonts

The following task explains the methodology for managing V5 Font standards for V4 to V5 migration. You will learn: 
  • how the migration of fonts is carried out,
  • and what you need to pre-define concerning the V5 standard parameters before starting the migration process.

Migration mechanism

The migration engine maps V4 and V5 fonts. This mapping is managed by a file called V4FontInteroperability.

Pre-definition

There are two possibilities:

  • If you used the standard V4 fonts, you do not have to customize anything in particular before migrating the V4 2D Models.
  • If you created specific fonts in V4, before starting the migration, you need to install the V4 FONT and FONTDATA files in the V5 installation folders, and you need to reference the V4FontInteroperability file. 

Here is what you need to do:

  1. If you have not migrated the V4 FONDATA files to FONT and FONTCODE files, do so in V4 using the CATFONT utility. 

  2. Install the V4 FONT files in installation_folder \resources\fonts\Stroke.

  3. Install the FONTCODE files in installation_folder\reffiles\NLS\fontcode.

  4. Rename the FONTCODE files using the following rule:
    XXXX.fontcode (where XXXX.fontcode  represents the V4 font code file) should be renamed FCUSERn.fontcode (where n represents the increment, 16 being the maximum number).

  5. Edit the V4FontInteroperability file in installation_folder\resources\fonts to add your V 4 FONTLIB names to the list. This file maps to a V 4 FONTLIB name, the FONT and FONT CODE that are associated with it. 
    The example below shows two fonts (ABBK and TIME) added to the V4FontInteroperability file with their corresponding font code: