Quote:
Originally Posted by AntoniDol
 Well, it's 287 pages of family history with 171 images so it took two weeks to produce, a flow layout version wouldn't do...
Fonts are embedded and as far as I know not subset at all. It could be a difference between the font files on Windows and macOS, but that shouldn't be the case because the font is embedded...
I'll ask my client to test the e-book on a different reader, like Bluefire. |
You can try, but the long and short of FXL, as yuou know, is that precise placement of everything--everything--letter-by-letter, word-by-word, is required if you are indeed making an FXL eBook. You couldn't have set the precise display parameters for the screen to be used, right?
And how did you set the pixel offsets, for the words?
The reason that FXL is so bloody limited is because (by design) it's limited to a specific set of devices. That Kobo's FXL layout "matches" Apple's is only because they literally mooched Apple's. You can't run an FXL ePUB, for example, made with InDesign, designed for iOS, on a Kindle, no matter how you get it there. It crashes and burns and yes, corrupts the layout as seen here.
So, I am not sure how you
actually designed that, to be FXL, without taking into account all the various parameters? Did you size it by her custom requirement, to a specific screen and reader? It would seem not, as she's getting corruption on her device.
????
Hitch