View Single Post
Old 07-19-2022, 11:02 PM   #211
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by Turtle91 View Post
You are, and have always been (AFAIR), thinking of <i>/<b> <em>/<strong> as purely visual presentations. You consistently ignore other functions - I suppose because they are not functions of your device. No matter how many times people point this out to you, you continue to ignore the non-visual applications of <em>/<strong>...


For even more <i> vs. <em> use-cases + differences, see my post:

Why did HTML5 make each one have separate uses?

Accessibility + Internationalization

Billions more people are on the Internet now, and HTML5 had to take into account many more languages + not just having a purely English-/Euro-centric view.

* * *

Italics and Emphasis are two distinct functions.

In English—through a quirk of history—it just so happens to be that emphasis looks the same as italics on the surface.

But there are thousands of other languages out there. Many languages don't have italics at all + they handle emphasis completely differently.

Here's a few examples I gave in the 2021 topic above:

Quote:
Originally Posted by Tex2002ans View Post
Auto-Translation

[...]

For example, emphasis in:
  • Arabic
    • extra lines above/below, different fonts, or extra stretched-out lettering.
  • Hebrew
    • bolder, underline, or larger gaps between letters (letter-spacing).
  • Chinese/Japanese/Korean
    • extra dots/symbols around characters.

Imagine you were a Japanese reader, and after an English->Japanese translate, every single word in your book titles had extra emphasis dots placed on it. That's not correct.
If you want more East Asian examples, see the CSS3 specs on "Emphasis Marks".

They show graphics and examples of different:
  • symbols (dots, circles, double-circles, sesame, [...])
  • locations (over/under/left/right)

That's just one small piece of italics <i> ≠ emphasis <em>.

- - - - -

Side Note: If you want even more on Asian-language emphasis, see:

If you want to see how Hebrew (+ Cyrillic + Korean/Hangul) handles emphasis, see the fantastic talk:

If you want to learn even more about the history/usage of Italics (which was only invented in the ~1500s):

- - - - -

Quote:
Originally Posted by JSWolf View Post
So how is <em> and <strong> visually different to <i> and <b>? The answer is there's no difference. <i> shows The Lancet exactly the same as <em>. And as you see in your post and this post, italics are being used and not emphasis.
The difference has been described to you dozens and dozens of times.

I'd highly recommend rereading this thread from the beginning, this time with an open mind.

Quote:
Originally Posted by bookman156 View Post
But when I started in web design it was considered bad practice to use i and b as everyone was moving to em and strong. So that is my habit as yours is for i and b. I wouldn't be surprised if I and b are chucked in the bin again some time.
No.

HTML4 wrongly deprecated <i> + <b>, which was an enormous regression.

And that started ~15+ years of the "Replace all <i> -> <em> + <b> -> <strong>" overcorrection.

HTML5 fixed that mistake.

* * *

I know it's information overload, and I recommended MASSIVE amounts of "homework" for you the past few weeks...

But read the 2021 link above + the entirety of this thread (and the original 2017 one too!).

Emphasis vs. italics has been described in extreme detail, with dozens of examples + HTML+CSS code samples.

And why is this so important to get right?

Text-to-Speech + Auto-Translation has gotten huge—and is only getting more popular/better—so tagging your markup properly has become even more important than ever before.

- - - - -

Side Note: And if you want one more thing to toss on the list, see my multiple in-depth comments in:

I described:

And I still stand by my advice at the end of that last post:

Quote:
And just because other people create disastrous documents doesn't mean you have to join them.

Create the cleanest and best dang documents you can, and you'll reap the benefits. I guarantee it!
- - - - -

Quote:
Originally Posted by JSWolf View Post
The last time this issue came up, nobody was able to mention such a program.
Those same exact words were spoken in this same exact thread!

See Post #75:

Quote:
Originally Posted by Tex2002ans View Post
Quote:
Originally Posted by Quoth View Post
I've yet to find ANYTHING that does treat them differently, [...]
Text-to-Speech (JAWS, NVDA).
I've described time and time again:

Text-to-Speech can, and does, treat these differently.

And if you're an advanced user, you can also customize the software to create extra noises/dings when hitting certain markup. (So italics can get a "[beep]" and emphasis can get a "[boop]".)

How do you think blind web developers read HTML?

Last edited by Tex2002ans; 07-20-2022 at 04:37 AM.
Tex2002ans is offline   Reply With Quote