thank you for this very interesting report. There are in fact two separate aspects to consider:
1. The font name restriction to 32 character:
This restriction is Windows specific. The Win32 API used to search for and load a TrueType font accepts 32 characters only (including the zero terminator sign). Effectively Windows uses 31 characters to find the desired font. To avoid potential user errors Embedded Wizard respects this restriction and if you specify a font name longer than 31 characters, it reports a warning. Consequently, the font names listed in the Assistant window are also truncated to 31 characters.
Nevertheless Windows is able to find the desired font as long as the first 31 characters match the name in a TrueType font file. In your case it is sufficient to use the name 'Fira Sans Extra Condensed Mediu' (without the last m letter). As you see in the following screenshot, it produces the correct outputs:
2. The second warning because of not available font:
Embedded Wizard double checks whether Windows has really found and loaded the right font. The background: if the specified font is not available on the Windows machine, Windows font engine simply selects another font without reporting any error code. Consequently, if you give your Embedded Wizard project to your colleague and he/she has not installed the appropriate TrueType font, Windows would use another font silently. This would produce another text outputs in your GUI application. To detect such errors, Embedded Wizard after selecting the font asks Windows for the real name of the selected font and compares this name with the originally specified.
Bizarrely, the for this purpose used Windows API returns the complete TrueType name (longer than 31 characters). As consequence, this name will not match the original truncated name. Embedded Wizard reports a warning again.
This behavior results from an evidently inconsequent implementation of the Windows API and is new for us. So far the technical background for the issue. In the next release we will adapt the comparison operation to respect the first 31 characters only so that the second warning is not reported anymore. For the moment I would ask you to simply ignore the warnings. Anyway Windows does select the right font.
I hope it clarifies the issue a little bit.