Fonts

You can manage V6 Font standards for V4 to V6 migration. This topic explains its methodology, wherein, you will learn how the migration of fonts is carried out, and what you need to pre-define concerning the V6 standard parameters before starting the migration process.

This page discusses:

Migration mechanism

The migration engine maps V4 and V6 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 V6 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 FONTDATA 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 to add your V4 FONTLIB names to the list. This file maps to a V4 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: