MobileRead Forums - View Single Post

seanos · 05-10-2012, 11:22 PM

Thanks for the enlightenment guys! (still wasn't getting notifications since there seems to be another thread-level choice that was turned off).

It's mystifying that Adobe would choose to create another Microsoft-style monopoly-driven standards failure, but I suppose there's not much to be done about it. HTML/CSS is so standard and prevalent these days it really makes no sense to support only a random subset.

I had already tried faking small caps (font-size: 80%; text-transform: uppercase

, so I could easily just change styles. Don't suppose anyone's come up with a hacky way of detecting ADE like the old IE hacks?

I was also relying on percentage widths for <hr/> too; I wonder if it can be hacked around with <div>s. Time to download ADE I suppose.

05-10-2012, 11:22 PM	#68
seanos Zealot Posts: 104 Karma: 12 Join Date: Apr 2010 Location: Melbourne, Australia Device: Kobo Sage, Kobo Aura H2O, LG V20	Thanks for the enlightenment guys! (still wasn't getting notifications since there seems to be another thread-level choice that was turned off). It's mystifying that Adobe would choose to create another Microsoft-style monopoly-driven standards failure, but I suppose there's not much to be done about it. HTML/CSS is so standard and prevalent these days it really makes no sense to support only a random subset. I had already tried faking small caps (font-size: 80%; text-transform: uppercase, so I could easily just change styles. Don't suppose anyone's come up with a hacky way of detecting ADE like the old IE hacks? I was also relying on percentage widths for <hr/> too; I wonder if it can be hacked around with <div>s. Time to download ADE I suppose.