Quote:
Originally Posted by paperwhite13
The advice I have come across is to just use the <small> tag instead of a span class; ADE renders it just fine. So that would be
<p>S<small>O </small>I<small> HAVE HEARD</small>, said Death.</p>
|
That is the same type of kluge that people have used for things like drop-caps. Unfortunately, there are still quite a few people who use it. It is NOT a recommended technique. It breaks up words so any spelling checkers, or search algorithms would not work, and it is not accessibility friendly...think what TTS programs would sound like: S...O...I...have heard...
In the example I gave above, none of that is an issue.
JSWolf is correct that a standards compliant device/app would just ignore any styling that it doesn't understand/support. So style from most basic to most complex, or older to newer, or least capable to most capable. The device/app will style to its highest level of compatibility without giving any errors. All MQs typically go on their own stylesheet in case older(er) devices that don't support MQs don't lose all the rest of the styling on the sheet.
Code:
So I have heard, said Death.
Is basic, but at least it is grammatically correct, readable, searchable, TTS able, etc. If the user doesn't LIKE that they have a basic device then it's up to them to decide if they want upgrade, or just live with it...if they even
notice they didn't have the small-caps...they've never seen it on that device.
You can also adjust your coding based on the capabilities of your target devices/apps. If you are marketing on Amazon, you only need to worry about kindle capabilities, not kobo quirks... swap the css sheet to a kobo version if you are going to sell there...not that difficult.