Rendering Drop Caps

[pdurrant]

Originally Posted by JSWolf

But it will break something because it's going to go against the eBook's CSS. If the CSS has a working dropcap, you'll mess that up. If the dropcap is broken, it's broken and you should not try to fix it.

Drop caps are impossible to do perfectly with CSS for arbitrary fonts. I think the renderer is correct to recognise the attempt and render it correctly for the current font.

[JSWolf]

Originally Posted by pdurrant

Drop caps are impossible to do perfectly with CSS for arbitrary fonts. I think the renderer is correct to recognise the attempt and render it correctly for the current font.

But that would be overriding the CSS and then publisher mode is dead. To have publisher mode, you need to respect the book's CSS even if it display's dropcaps poorly.

[pdurrant]

Originally Posted by JSWolf

But that would be overriding the CSS and then publisher mode is dead. To have publisher mode, you need to respect the book's CSS even if it display's dropcaps poorly.

All markup is to express the intent of the author. If the intent is a well formed drop cap, then rendering that intent is the correct thing to do.

I look forward to trying out the new code when the next version appears in the app store.

[JSWolf]

Originally Posted by pdurrant

All markup is to express the intent of the author. If the intent is a well formed drop cap, then rendering that intent is the correct thing to do.

I look forward to trying out the new code when the next version appears in the app store.

That's fine for when you turn off Publisher Mode. But the reason for Publisher Mode is to follow the CSS. So if you are helping out the dropcaps, then it's no longer Publisher Mode.