- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 09 Sep 2009 11:51:35 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7508
--- Comment #3 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2009-09-09 11:51:35 ---
(In reply to comment #0)
> <dialog> and <dl> should permit <dt> in same contexts.
[ ... ]
> <dt><time>14:23</time> Leif leaves the chat.</dt><!-- no dd here -->
To make <dialog> and <dl> fully equal w.r.t where <dt> is allowed and how it is
used, this has to be defined different from the proposal above. Namely
subsequent <dt>'s has to be considered alternatives.
Thus, in the above example, there would have to be an empty <dd> to indicate
lack of speech:
<dt><time>14:23</time> Leif leaves the chat.</dt><dd></dd>
While one could mark up alternative representations of the dialog participants
using subsequent <dt> elemetns - for instance if the participant should be
written in two different languages:
<dialog><dt lang="it"><cite>Pinocchio</cite></dt>
<dt
lang="ru"><cite>Пиноккио</cite></dt>
<dd lang="it">[ speech in Italian ] </dialog>
This is equivalent to how the draft gives examples for how to define the
English and the French word for color:
<dl><dt lang="en-US"> <dfn>color</dfn> </dt>
<dt lang="en-GB"> <dfn>colour</dfn> </dt>
<dd> [ definition in English ]</dl>
The same goes for <dd>, for which <dialog> has a limitation on where it may
appear, compared with <dl>. <dialog> should permit a <dd> to follow another
<dd> also inside <dialog>. This could be used to express alternatives - the
participant may say - or may have said - this, or he/she/they may have said
that. Or it could represent what was said in different languages.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 9 September 2009 11:51:47 UTC