Forum Moderators: open
However, with CFStudio 5 it puts in <em> instead of <i>, and <strong> instead of <b>. Are <em> and <strong> part of a new web standard or is CFStudio 5 acting the fool?
You are not entirely wrong though. These tags are deprecated. You are strongly encouraged to use Style Sheets whenever possible.
EM and STRONG are used to indicate emphasis. The other phrase elements have particular significance in technical documents. These examples illustrate some of the phrase elements:As <CITE>Harry S. Truman</CITE> said,
<Q lang="en-us">The buck stops here.</Q>More information can be found in <CITE>[ISO-0000]</CITE>.
Please refer to the following reference number in future correspondence: <STRONG>1-234-55</STRONG>
The presentation of phrase elements depends on the user agent. Generally, visual user agents present EM text in italics and STRONG text in bold font. Speech synthesizer user agents may change the synthesis parameters, such as volume, pitch and rate accordingly.
These are not deprecated tags. They have a secondary purpose besides allowing visual browsers to render them as <b> or <i>. I always wondered about these two myself; <strong> and <em>. I see more use of these tags now that CSS has come to the forefront. I think we will see many more topics on these and other phrase elements.
[w3.org...]
(edited by: pageoneresults at 10:55 pm (utc) on April 30, 2002)
Avoid the use of deprecated presentation elements and attributes (as well as B and I). Authors should use style sheets instead of presentation elements (TT, and FONT) and attributes ("align" and "background") that control visual presentation. Authors are encouraged to use elements (such as STRONG, EM, H1, H2, ABBR, etc.) that add structure to documents. Documents that use style sheets for presentation allow users to adjust the look of the document (e.g., larger print, color contrast, etc.) through personal style sheets or browser settings.
Documents that use style sheets for presentation allow users to adjust the look of the document (e.g., larger print, color contrast, etc.) through personal style sheets or browser settings.
Can users specify their own stylesheets to use with my pages? I've been using stylesheets partially as a means of preventing users from changing the look of my page via their browser settings - can they do something I never knew they could?
[w3.org...]
Good starting point for us all...
When you take the big picture into consideration, the fact that everything is being switched over to CSS, then it makes sense!
Sure, in some cases we'll end up with more characters, and thereby heavier documents, but in the end it's good and saves us a lot of work.
You can retain control...
If you, in your style sheet want to mark something as important, use the following code:
P { font-size: 18px ! important }
You are telling your user, that it is important, that you use 18px, as your fontsize.
(edited by: papabaer at 11:00 pm (utc) on April 30, 2002)
I'll agree that <b> is much easier than <strong>. But, only for visual browsers. Once you get into speech based its a different story. I can see the points from both sides.
I've almost put all of my <b>'s and <i>'s into external style sheets using the <span> tag. If I just need <b> or <i>, that is what I use and it still validates!
[w3schools.com...]
Well, close, papabaer .. it's ROTFASTC .. But either one works I guess :)
Makes me wonder though ..
Let me give you an example .. Here, at WebmasterWorld, it's so easy to write a script that replaces [ i ] with <I> .. But those kind of replacements won't be as easy in the future .. Or, should I say - they will result in tons of code, using <span> or something like that! :O
What would you use instead?
"<span class="italic">Italicized text</span>"?
It's less readable than "<i>", takes longer to write, and increases the size of your HTML file. It's lack of easy-of-use might also distract a web-developer from content - which many would think is paramount to concerns such as this.
I think we should tape his eyelids open and place him in front of monitor with the W3C pages scrolling in front of him. Of course at a pace where he can read each single line of text.
I'm definitely going to read more on the <em> and <strong> elements, thanks to Filipe and papabaer this time! I like the idea of moving towards 100% accessbility. Bobby, here I come! Oh, that will be one major task!
XHTML
[w3.org...]
[w3schools.com...]
XHTML is in!
(edited by: papabaer at 11:26 pm (utc) on April 30, 2002)