Re: com web/php: Removed bold style on em; this is mostly important for the wiki, but always making 'italic' also bold is overwhelming.:
styles/site.css

On Wed, Oct 23, 2013 at 8:16 AM, Levi Morrison <levim@php.net> wrote: > Commit: c036828cbd87a5977810c9cd4e099e91e6e14cd8 > Author: Levi Morrison <levim@php.net> Wed, 23 Oct 2013 09:16:41 -0600 > Parents: 586bfaf0b8c04a77f4f72ee49b9f85dbb8217554 > Branches: master > > Link: > http://git.php.net/?p=web/php.git;a=commitdiff;h=c036828cbd87a5977810c9cd4e099e91e6e14cd8 > > Log: > Removed bold style on em; this is mostly important for the wiki, but always making > 'italic' also bold is overwhelming. > > Changed paths: > M styles/site.css > > > Diff: > diff --git a/styles/site.css b/styles/site.css > index e5351ea..b4a7373 100644 > --- a/styles/site.css > +++ b/styles/site.css > @@ -197,7 +197,6 @@ ul li { > } > > em { > - font-weight: bold; > font-style: italic; > } > Since docbook is extremely semantical, it misses to differentiate italic rendering and bold. There is however an option (role="bold") that can be used, defeating the purpose of the semantics, and not used at all (until mysqlnd* started using it outof the blue for unknown reason, probably edited in a docbook editor?) - which is why it was never implemented. The rendering expectations is italic and/or bold[1]. We have always done the "and" as it has been used in ways a "heading" would be expected. The example you posted is excellent example of that, where a more semantically meaning markup may have been more useful :/ I think we still need it in tables, at the very least, due to our abuse of it. -Hannes [1] Formatted inline. Emphasized text is traditionally presented in italics or boldface. A role attribute of bold or strong is often used to generate boldface, if italics is the default presentation.