MobileRead Forums - View Single Post

GrannyGrump · 09-24-2013, 02:31 AM

Ah. Great tutorial. this could also be adapted for fragments of any special text in-line.

I do want to warn about 16-shade pngs though. They display badly on some readers and some apps. See the thread I posted recently https://www.mobileread.com/forums/sho...51#post2633151

Jellby responded that it is a bug in the ADE engine, dealing poorly with 2-bit and 4-bit color.

I tried GMcG's suggestion for reducing to 16-shades and then back to 256 (8-bit). It does make a smaller size than an image with the full 256 shades, and in my testing came out about 10-25% bigger than the original 16-shade png. The resulting display seems to work fine. I was not working with web-safe palettes --- those would be a lot smaller, and should be fine for text.

09-24-2013, 02:31 AM	#4
GrannyGrump Obsessively Dedicated... Posts: 3,229 Karma: 35158061 Join Date: May 2011 Location: PA {back in the usa!} Device: Sony PRS-T2, ADE on PC	Ah. Great tutorial. this could also be adapted for fragments of any special text in-line. I do want to warn about 16-shade pngs though. They display badly on some readers and some apps. See the thread I posted recently https://www.mobileread.com/forums/sho...51#post2633151 Jellby responded that it is a bug in the ADE engine, dealing poorly with 2-bit and 4-bit color. I tried GMcG's suggestion for reducing to 16-shades and then back to 256 (8-bit). It does make a smaller size than an image with the full 256 shades, and in my testing came out about 10-25% bigger than the original 16-shade png. The resulting display seems to work fine. I was not working with web-safe palettes --- those would be a lot smaller, and should be fine for text.