View Single Post
Old 11-16-2015, 08:27 PM   #13
AlanHK
Guru
AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.AlanHK ought to be getting tired of karma fortunes by now.
 
AlanHK's Avatar
 
Posts: 681
Karma: 929286
Join Date: Apr 2014
Device: PW-3, iPad, Android phone
Quote:
Originally Posted by RbnJrg View Post
To convert a glyph in a svg image is a piece of cake. Do the following:
Making the svg isn't the problem. It's that I was told the pages using svg simply did not appear on some devices. (iPad using their Kindle player.)

Since it worked for me, in Sigil, Calibre, and Amazon's Kindle previewer, but not my client, who is on another continent, trying to track down the problems(s) is impractical. Every modify/check takes a day and we have a deadline.

I've had to back off from using elegant code several times because of this kind of issue.

I know some people leap into things like media queries and try to code for every device separately, I don't have the time and am not earning enough from this one job to devote the time and money (to buy hardware) to make it work. So I use the simplest, least demanding code that works in all cases.

In this case, I have 2 solutions that do work: embedded font and embedded image. Going forward I hope I can make the font subsetting work better. A file that works and has standard coding is preferable, to me, even at the cost of a bloated file.

Last edited by AlanHK; 11-16-2015 at 08:38 PM.
AlanHK is offline   Reply With Quote