From NSIS Wiki
|Author: Vytautas (talk, contrib)|
This plugin will retrieve the Display name from a TTF font file. I wrote it to make it easier to register TTF fonts in windows.
Note: This plugin could only get the English name of a font file. If the file contains more localised names, you may want to get the name of current language of your system. More information at: http://nsis.sourceforge.net/Get_localised_font_name.
How To Use
This is an extract from the included readme showing an example of usage:
To use the plugin simply include the FontName.nsh file into your script then use one of the following macros:
!insertmacro FontName "fontfile.ttf"
Now the stack contains the name of the Font or if the errors flag was set, the error message translated to your current language, or English if the translation is not yet available.
This macro will push to the stack the translated version string for the FontName Plugin.
Please note that the font file MUST exist for the plugin to work, so you should check that before calling the plugin. For a more detailed example of the plugin's usage check out the Register Fonts and Advanced Font Installation pages created by me.
Un.installation part for this plug in generate error nd wont work but other things work correct.
[UPDATE: 2005-08-03] Added more translations. The installer now also installs the latest font registration header files.
[UPDATE: 2004-02-19] Added french translation to distribution. Optimized source code somewhat.
[UPDATE: 2004-02-10] Used a different compiler, reduced the plugin's file size from 32kb to just 9kb.
[UPDATE: 2004-01-29] Added an include file so that you need only use the macros provided. Now the plugin is translatable if your language is not included please add it to the list in this forum. Changed error reporting prefix to enable better international support.
[UPDATE: 2003-11-27] Added error reporting functionality. Check for 'error:' at the start of the returned string on the stack.
[UPDATE: 2003-11-26] Fixed plugin crash in Win9x Family.
[UPDATE: 2003-11-18] Fixed problem with plugin reporting 'FontFamily' instead of 'FontName' affecting certain fonts, e.g. Arial Bold and Arial were both being reported as Arial.