This is the best answer only partially, but it may be useful for some people. In the CSS font stack, you can add a monolayer font that has good Unicode coverage. For example, Courier New in OS X includes over 1200 glyphs, which I assume includes most of the useful Unicode characters. If you list it after the main font in the font stack, you should at least have a consistent width for those characters that are not in your main font.
Of course, this really does not solve the problem if the width of the main font is different from the width of the backup. If you're lucky, you can find a fallback font with the same width that has enough Unicode coverage, in which case you can use it as is. Otherwise, I think you have no easy solutions. In this case, I can come up with a couple of alternatives.
- If the license permits this, you can change the width of the backup font so that it matches your main font.
- If you know in advance which Unicode characters you want to display, you can wrap them with a
<span> and adjust the styles to match the width of the main font.
Hard decision anyway, I'm afraid.
PS You might want to change your title. I think you mean "monolayers" because "monotype" is a casting type.
source share