View Single Post
Old 10-04-2021, 01:01 PM   #6
Hitch
Bookmaker & Cat Slave
Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.Hitch ought to be getting tired of karma fortunes by now.
 
Hitch's Avatar
 
Posts: 11,503
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
Quote:
Originally Posted by RBossler View Post
Thank you for the response.

I'm running everything on a Chromebook (ChromeOS and Linux) so I couldn't find a way to run Kindle Create.

I'm actually still in the midst of reworking the code with my "fix" above. I'm hopeful it will work (it makes sense to me), but I'm relatively new at coding and I don't know exactly how the amzn-app-magnify code works. Do you have much experience with FXL on KDP? Any thoughts on coding this to work?
Yes, we've done a bunch. I wouldn't say a thousand, (ha!), but hundreds of fxl, over the last 12 years, yes.

Well, Region Magnification ("RM") zooms text, by and large. I don't mean to argue with you, really, but you're hampering your ebook, because to use RM, you create an eBook wherein the pages cannot zoom. This standard, using FXL with not-zoomable pages, and RM is...gosh, 7-8 years old and hasn't been updated, really, in all that time? And more importantly, is more or less abandoned?

Have you tried to see if Kindle Kids' Book Creator will run on your Chromebook? I ask because KKBC does exactly what you're trying to do. I do not pretend to remember what that does and doesn't run on, but if you can get it working, use it. You're manually doing a lot of extra work, otherwise.

The problem with FXL on Kindles, whether you hand-code them or not, is that no two Kindles are the same. They're not. You have at least 5x different Fires, with different screen resolutions, and dimensions; you have an endless list of variables, on the desktop readers--Kindle for PC, Kindle for Mac, for Chromebook, for Win8, for this tablet, for that tablet, for iPhones, for iOS, for...I mean...it's bloody endless.

If you use the method you're using now, you present the reader with fait-accompli and here's the thing--no way to size the background of the eBook to suit themselves. They can't zoom the pages larger or smaller. All they can do is tap-zoom the text, up to 200-250%, if it works. They don't have virtual panels, like comic books. (n.b.: you use magnify in both, kids' books and comics, but you have to declare the meta for a comic, to get the panel view to work. And then you can't make the text zoom in addition to the panel.

It's one trick and one trick only. Increased RM for text, or a pop-up panel and that's all she wrote.

So...RM works for text, only. It doesn't really magnify the backgrounds. You create your text by re-entering it (at least, we do) in the RM coding.

I assume, since you're familiar with magnify, etc. that you got all this from the 2019 Publisher's Guidelines, right? 2019.2, which I believe was the last new release? (You should be able to tell how old those coding instructions are, by the devices that they talk about in the Kids' book sections, by the way and the pixel resolutions.)

I doubt that helps. Do you have a friend or a library with a PC? It's one thing for my guys to make hand-coded FXL; it's another thing altogether for a newbie to try it.

Hitch
Hitch is offline   Reply With Quote