Quote:
Originally Posted by JSWolf
If all you are doing it italicizing, why would you mix <i> and <em>? For that matter, why use <em>? I would just go with <i>. Two reasons for <i>. Less code and all programs to display the eBook should know exactly what's meant by <i>.
|
Read the 2017 thread. You even posted in there.
Quote:
Originally Posted by Jellby
I'm not saying <i> and <em> will make any actual difference in the real world, but since they are intended for different things, that could be a reason for keeping them separate. Who knows, maybe tomorrow you'd like to mark emphasis with a bold font, but leave italics as italic.
|
The 2017 thread covers most of these cases too.
Another case of <b>/<strong>:
For example, in Maths/Physics,
vectors can be displayed in three ways:
usually bold, but different fields and schools of thought display them differently.
Code:
<strong>Note:</strong> The vector <b>v</b> goes from point A to C.
Of course, it's best to go even further and markup with classes:
Code:
<strong>Note:</strong> The vector <b class="vector">v</b> goes from point A to C.
this allows you to easily manipulate it later if needed, but you're not reliant purely on CSS.
* * *
In certain citation styles, bold is used for "Volume #":
Code:
F. Last, <i>Journal of Examples</i> <b>84</b>(2), 449–495 (2012).
Of course, classes further help:
Code:
F. Last, <i class="journaltitle">Journal of Examples</i> <b class="volumenum">84</b>(2), 449–495 (2012).
If switching citation styles, you may not want bold volume #... but it's definitely not <strong>.
Side Note: Also highly recommend watching one of my favorite talks from
ebookcraft 2019, "Building Ebooks that Last"... especially around 19 minutes where she shows a poorly marked-up recipe book (using code like <p class="heading2"> instead of <h2>) "separated from its CSS".
Quote:
Originally Posted by Quoth
I've yet to find ANYTHING that does treat them differently [...].
|
Text-to-Speech (JAWS, NVDA).
Quote:
Originally Posted by Quoth
Nor do I know how to create an <em> in source text other than editing HTML directly.
|
Most tools probably default to all <i> or all <em> (similarly all <b> or all <strong>).
For example, Reddit changes **markup** -> HTML <em>markup</em>. Or if you post into a CMS (Content Management System), it may "helpfully" change every <i> to <em> (grumble, grumble, ask me how I know. :P).
But if you use Styles properly in your documents, you may generate code that can easily be manipulated into more semantic meanings. And if you
do mark things up properly, you'll be better off in the long-run.
Side Note: Similarly, see my recent thread
"Should Chinese Fonts be Embedded in Ebooks?". Proper markup for HTML lang is very important. Do most mark lang properly? No. Should they? Yes*.
Quote:
Originally Posted by Quoth
Computer software is rubbish at context. I've not heard text to speech improve much in thirty five years, it does sound a bit more human. But compared to even an inexperienced human it's rubbish.
|
You haven't been looking closely.
And TTS is currently one of the fastest growing fields, especially with the *shudder* "Personal Assistants".
Quote:
Originally Posted by Quoth
So I'm sceptical. I suspect the <em> is something some HTML guru thought up and it's not really important.
|
There was a little speedbump there in HTML4 where they deprecated <i>+<b>, but I think they made a step back in the right direction in HTML5.
Quote:
Originally Posted by Quoth
How would I decide to use <i> or <em>.
|
See 2017 thread.
Quote:
Originally Posted by Quoth
The Interobang never caught on.
|
Side Note: Seriously‽
You may be interested in some links in my Reddit post from a few days ago:
https://www.reddit.com/r/writing/com...bangs/fuyl3jp/