I don’t know the difference but I don’t think it’s relevant. Nowadays all software running on Windows support TrueType fonts, OpenType fonts and TrueType font Collections. We might be able to help if you describe the exact problem.
I am developing a custom application that uses a vendor provided font. This font needs to be embedded inside the application and not installed on the users system. The vendor does not want the font available to the public. I have made some changes to this font using FontCreator 5.5. The original font will not work embedded in the application either.
However if the font (original or modified) is installed on the users machine it works fine.
The problem I am having is that the font will not load correctly in Visual Basic labels and text boxes.
Here is a thread that sort of describes the problem I am having. The second post is the one the makes reference to GDI and GDI+ fonts.
To use the memory font, text on a control must be rendered with GDI+. Use the SetCompatibleTextRenderingDefault method, passing true, to set GDI+ rendering on the application, or on individual controls by setting the control’s UseCompatibleTextRendering property to true. Some controls cannot be rendered with GDI+.