From: Ingo Schwarze <schwarze@usta.de>
To: Kristaps Dzonsons <kristaps@bsd.lv>
Cc: tech@mdocml.bsd.lv
Subject: Re: Is there any reason not to use <EM> for items emphasized with .Em?
Date: Thu, 14 Aug 2014 02:46:56 +0200 [thread overview]
Message-ID: <20140814004656.GH26534@iris.usta.de> (raw)
In-Reply-To: <53EBF3C1.9000604@bsd.lv>
Hi Kristaps,
Kristaps Dzonsons wrote on Thu, Aug 14, 2014 at 01:24:49AM +0200:
> I think this conversation is getting a little away with us.
> Let's please, please keep it simple::
Makes sense, so i simply reverted my broken commit.
> .Em <span class="em">
> .Bf -emphasis <div class="em">
> .Sy <span class="sy">
> .Bf -symbolic <div class="sy">
> .Li <span class="li">
> .Bf -literal <div class="literal">
>
> Then in CSS,
>
> .em { font-style: italic; }
> .sy { font-weight: bold; }
> .li { font-family: monospace; }
> div.em, div.sy, div.li { display: inline; }
Looks reasonable, even a bit simpler than what we have now.
Go ahead if you want to do that.
> This should really be stuck in the "default" CSS as I've provided in
> the HTML5 document. This way, we get consistent use of italics (or
> whatever the CSS override wants) without being tied to <i> (etc.)
> and it's consistent for both the .Bf and .Em versions.
Indeed, that's probably a case needing an in-document CSS fallback
because without it and without an external style sheet, it won't
be italic at all. I think a small amount of in-document CSS fallback
is still better than sticking font-*: display: foo into each and
every element.
> I understand it won't be "semantic", but we already lost that game
> with the ".Bf" versions of the same. Let's keep semantics where
> it's completely unambiguous, and these messages suggest the
> contrary!
Indeed; regarding the manual, i just argued that we should stop
calling .Em and .Sy semantic at all.
Yours,
Ingo
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2014-08-14 0:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 22:44 Guy Harris
2014-08-13 1:15 ` Ingo Schwarze
2014-08-13 2:06 ` Anthony J. Bentley
2014-08-13 14:51 ` Ingo Schwarze
2014-08-13 15:17 ` Anthony J. Bentley
2014-08-13 17:49 ` Ingo Schwarze
2014-08-13 1:44 ` Joerg Sonnenberger
2014-08-13 15:30 ` Ingo Schwarze
2014-08-13 17:20 ` Ingo Schwarze
2014-08-13 18:53 ` Guy Harris
2014-08-13 23:24 ` Kristaps Dzonsons
2014-08-14 0:46 ` Ingo Schwarze [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-21 0:30 Guy Harris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140814004656.GH26534@iris.usta.de \
--to=schwarze@usta.de \
--cc=kristaps@bsd.lv \
--cc=tech@mdocml.bsd.lv \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).