I'm developing an OpenType font by byte-crafting it rather than using design tools, and now have a custom OpenType (CFF flavour) font that implements a really small subset of the Basic Latin unicode block (specifically it only implements .notdef and what under Basic Latin interpretation would be the tilde).
The CFF block passes "tx -3" validation, the font as a whole passes a round-trip de/recompile through TTX, and Microsoft's Font Validator does not report any errors in the font. Even loading it as a custom webfont (as plain otf in browsers that support otf, and wrapped as WOFF in browsers that don't) makes them style the implemented ~ glyph correctly.
However, even with all that apparent correctness, the windows font previewer reports that it is not a valid font file, and window will not let me install it (at least in windows 7. I do not have access to 8). I've looked high and low for information on what windows requires for a font to be installable, but haven't been able to find any decent docs; the internet seems to be filled with how to install a font as a user, rather than what requirements need to be met as developer =)
The font file, as both CFF block, .otf file, WOFF file, and TTX output, can be found over at https://github.com/Pomax/CFF-glyphlet-fonts/tree/gh-pages/binaries (in the base dir, not the "with GSUB" dir)
If there are any additional tools that I can use to determine whether or not this font is "done" enough to be installable, or if anyone knows where to find the documentation that explains which criteria a font needs to meet before it can be installed, that information is extremely welcome. And of course, if someone happens to notice something actually wrong with the font itself based on the TTX readout, I'm also keenly interested in your findings =)