Quote:
Originally Posted by Hatgirl
Oh, it does (see the .ihatemobi class I mention in my first post). It's a legitimate workaround. But we shouldn't have to be finding workarounds, we should just be able to write code that complies with the W3C specs and have it bloody work  |
that will never happen. W3C is for a web browser, not an eBook reader. It would be more reasonable to ask for something that complies with ePUB spec which would have been ok for this problem. Amazon seems to be actively changing Kindlegen to be better at doing ePUB conversions so at some point they may fix this particular problem but so long as they hang on to Mobi/AZW format there will be some things that will never work.
Dale