Quote:
Originally Posted by nrapallo
That's a current limitation that you are up against! It recognizes the glyph, but doesn't render (support) it. Making images to replace common unsupported glyphs is a practical solution; just search and replace
Code:
"& # 601"
with
<img src="601image.gif">
I think this is your only choice. Just make ONE image for each unsupported legal gylph and search and replace as indicated above. For say a hundred "& # 601" you will only need one 601 image! |
heh, sorry, i should have been more clear. obviously, i will only need one image
for the 601 glyph. but i meant, in this book there are a lot of *other* glyphs which also would need to be replaced (there are a lot of phonetic spellings of words, using wacky phonetic glyphs, because it's a book about the creation of the dictionary. quite a few of them are not supported) ; potentially dozens or hundreds of *different* glyphs and each time i have to make an image (god help me...).
well, since there is no good way of doing this, i think i will go along to the eBook Publisher bug thread, and mention that it would be really nice if they could support all the special glyphs... (and some different fonts would be nice as well ! sheesh, if they just added Arial and Times New Roman i think we would probably have no more trouble with any wacky glyphs) i really don't like putting text in images if i can possibly avoid it, for many reasons. just an example, if i resize the text, the image will stay the same...
Quote:
Usually 'Tidy' used by 'LIT2SB' handles the conversions quite well, but I had it fail miserably recently for a test case of converting Esperanto. Maybe your html is similar.
p.s. I also got terrible results from Tidy when from converting UTF-8 (see post#44 here), however, I think your situation is different.
|
well, the meta tag *does* specify that this is UTF-8 character set, however i don't think that is the problem, since i can't imagine how the character set could affect the text alignment... could it ?
i'm getting close to a presentable text right now, even if i did cheat and use the .doc as my starting point. i suppose i probably will have to make those blasted glyph images, if i want to really make a nice text (well, "nice" as long as no-one looks at the code !!).
stupid drm lit... i swear, problems like this make me want to stop buying books altogether.
thanks for your help, even if there's not really anything to be done...