At the moment the font's are ignored, so I am not surprised by this. Although, there is a setting in which the used fonts are referenced and, if possible, embedded in the ePUB. It should do the trick I think. That being said, embedding is usually not allowed for most commercial fonts, that would include webdings.
One of the issues is that the support for these characters in the default fonts on the readers are probably non-existing. So the references would be there, but rendered as a question mark or box usually.
That all being said, I do see added value in this. In fact, at the moment I am working on a grand overhaul of the whole 'convert to html' part. It is being rewritten from the ground up using totally different techniques and methods. It should be a lot faster and better portable to other applications.
This topic actually came up in my notes several times (both fonts specific and symbols specifically), so it is something I am addressing there. The prep-work you did will probably help me a lot, so thanks!
The new library that I am building will feature support for both fonts and symbols in some form. It is nowhere near from finished yet, as I want to have at least support the same Word functions as I do now. The basics work, but currently I am working on more complex tables (row and column spans) and lists.
Work is slow, especially since my laptop decided to end his life after four years and I have no replacement.
|