Certain Fonts Are Not Available in LabVIEW

Updated Jul 2, 2018

Reported In

Software

  • LabVIEW
  • LabVIEW Base
  • LabVIEW Full
  • LabVIEW Professional

Issue Details

I installed some fonts for using in LabVIEW. The fonts are available to be selected from the drop-down menu of fonts that LabVIEW provides, however, the default application font is used rather than the font selected.

Solution

Some fonts do not work correctly in LabVIEW on a localized OS. The problem seems to happen only on certain localized versions of the Windows OS. You can prevent coercion to a font supported by your OS's code page by manually specifying a code page for the font in the ini file. Append a sentence to the C:\Program Files (x86)\National Instruments\LabVIEW 201X\LabVIEW.ini file as follows: 
FontCodePageList=Font name,Code Page Identifier 

If you want to use several fonts, Append the sentence to the ini file as follow: 
FontCodePageList=Font Name1,Code Page Identifier;Font Name2,Code Page Identifier;Font Name3,Code Page Identifier

The following table defines the available code page identifiers in Window.
 
 Identifier .NET Name Additional Information
 1250 window-1250 ANSI Central European; Central European (Windows)
 1251 window-1251 ANSI Cyrillic; Cyrillic (Windows)
 1252 window-1252 ANSI Latin 1; Western European (Windows)
 1253 window-1253 ANSI Greek; Greek (Windows)
 1254 window-1254 ANSI Turkish; Turkish (Windows)
 1255 window-1255 ANSI Hebrew; Hebrew (Windows)
 1256 window-1256 ANSI Arabic; Arabic (Windows)
 1257 window-1257 ANSI Baltic; Baltic (Windows)
 1258 window-1258 ANSI/OEM Vietnamese; Vietnamese (Windows)

Note: Originally, Windows code page 1252, the code page commonly used for English and other Western European languages, was based on an American National Standards Institute (ANSI) draft. If you want to know more code page identifiers, refer to External Link: MSDN: Code Page Identifiers.
 

Additional Information

Code Pages

Most applications written today handle character data primarily as Unicode, using the UTF-16 encoding. However, many legacy applications continue to use character sets based on code pages. Even new applications sometimes have to work with code pages, often for one of the following reasons:
  • To communicate with legacy applications.
  • To communicate with older mail and news servers, which might not always support Unicode.
  • To communicate with the Windows Console.

Note: New Windows applications should use Unicode to avoid the inconsistencies of varied code pages and for ease of localization.

WAS THIS ARTICLE HELPFUL?

Not Helpful