EPUB -> AZW3 images get squished

[Siavahda]

So you're saying that bad CSS is pretty much industry-wide, which is why I have this problem with every book I try to convert? Yikes. Thank you for explaining, though.

[theducks]

Originally Posted by Siavahda

So you're saying that bad CSS is pretty much industry-wide, which is why I have this problem with every book I try to convert? Yikes. Thank you for explaining, though.

I don't think that is quite what they meant.
MOBI is an old format. It had no CSS ability, so lots of tricks were used to create some styles. Those may need help (by hand editing since the HOW DONE was not standard).

Then there is the 'self pub' done by those that are coding challenged ? (not everything can be fixed by Otto )

Last is Boxed sets with minimal effort (Slap a Contents, copyright and cover and combine the rest ... mostly as is )

[Quoth]

Originally Posted by Siavahda

So you're saying that bad CSS is pretty much industry-wide, which is why I have this problem with every book I try to convert? Yikes. Thank you for explaining, though.

There is good to terrible css & HTML. Some big publishers are as guilty as worst amateurs because they are using tools intended for paper and kludged for reflowable ebooks, like InDesign.

We test all three main Amazon formats and epub on 3 kinds of Kindle and on apps on 4.3" screen to 14" screen when we do something new. So I know what to do do with the regular kinds of images we have.

If something really new on styling we check the Amazon KFX and azw3 published versions by buying them. Amazon, Apple and to a lesser extend Kobo reconvert the uploaded files. Kobo sales directing downloaded to PC are as uploaded, as are Smashwords and Google.

We can't test what B&N do, because Nook is not available (even as App) in Europe,

[Siavahda]

Originally Posted by Quoth

There is good to terrible css & HTML. Some big publishers are as guilty as worst amateurs because they are using tools intended for paper and kludged for reflowable ebooks, like InDesign.

I have DEFINITELY seen this. It's maddening.

Glad your publisher is so conscientious, gives me a little hope

[Siavahda]

Originally Posted by theducks

I don't think that is quite what they meant.
MOBI is an old format. It had no CSS ability, so lots of tricks were used to create some styles. Those may need help (by hand editing since the HOW DONE was not standard).

I don't understand how that jives with MOBI presenting perfectly every time.

EPUB -> MOBI: images are perfect. Every single time, regardless of publisher.

EPUB -> AZW3: images are almost never perfect.

In practice it's the AZW3 ones I always have to edit by hand...

[theducks]

EPUB to Mobi is probably the NEW (combined) Mobi

Why AZW3 has issues as it is usually just a Wrapper on EPUB.

Maybe that does not deal well with GIGO . Does the EPUB Validate? (I get a lot of books that have serious CSS errors ( not even valid code. wrong keywords)

[JSWolf]

Originally Posted by Quoth

There is good to terrible css & HTML. Some big publishers are as guilty as worst amateurs because they are using tools intended for paper and kludged for reflowable ebooks, like InDesign.

We test all three main Amazon formats and epub on 3 kinds of Kindle and on apps on 4.3" screen to 14" screen when we do something new. So I know what to do do with the regular kinds of images we have.

If something really new on styling we check the Amazon KFX and azw3 published versions by buying them. Amazon, Apple and to a lesser extend Kobo reconvert the uploaded files. Kobo sales directing downloaded to PC are as uploaded, as are Smashwords and Google.

We can't test what B&N do, because Nook is not available (even as App) in Europe,

Some use Vellum & Pages. Both are awful programs to use for anything.

You don't really need to test the nook. If it works on Kobo with RMSDK, it will work on the nook as B&N also uses an older version of RMSDK.

[Siavahda]

Originally Posted by theducks

EPUB to Mobi is probably the NEW (combined) Mobi

Why AZW3 has issues as it is usually just a Wrapper on EPUB.

Maybe that does not deal well with GIGO . Does the EPUB Validate? (I get a lot of books that have serious CSS errors ( not even valid code. wrong keywords)

I'm afraid I don't know what GIGO is or what it means for an EPUB to Validate anything more than the VERY basics, you need to explain like I'm 5.

[PeterT]

GIGO is simply Garbage In Garbage Out

Sent from my Pixel 7a using Tapatalk

[Siavahda]

Originally Posted by PeterT

GIGO is simply Garbage In Garbage Out

Sent from my Pixel 7a using Tapatalk

I'll try and remember that, thanks XD

[DNSB]

As for validate, in most cases, that means running epubcheck to check the epub and running a css validator such as the online W3C CSS Validation Service or a utility that uses that service. If there are any errors, your ebook is likely to have issues with publishers and Send to Kindle.

Originally Posted by PeterT

GIGO is simply Garbage In Garbage Out

Alternatively and sarcastically, Garbage In, Gospel Out.