Hello,
We ought not specify how the element gets rendered; however, we ought to declare a processing expectation. As Eliot pointed out, establishing a processing expectation for 'ol' sets a precedent for doing this sort of thing. Moreover, several aspects of the CALS table model would not be admissible if we were to insist upon maintaining a pure separation between semantics and presentation. While prudent designers respect this separation as much as possible, there are cases where execptions are warrented.
In the case of 'q', perhaps language such as the following would suffice:
The <q> element's content in the DITA source should never contain qoute marks. Processing is responsible for rendering the <q> element's content in a
distinct way. It is expected that processing will render the <q> element by surrounding its content with qoutes or by applying a distinct typeface to the content. Other reasonable renditions may also be possible.
Regards,
Bob Thomas
Tagsmiths, LLC
+1 720 201 8260
From: Robert D Anderson <robander@us.ibm.com>
To: dita <dita@lists.oasis-open.org>
Sent: Tuesday, January 6, 2009 8:44:27 AM
Subject: [dita] Behavior of <q> element
Hello,
Going through the review comments to the specification, I found that
somebody asked for examples of how <q> should be processed. Generally, we
try to stay away from processing behaviors, but this one may be an
exception. The current description gives no suggestions as to whether or
not quotes should be generated. I checked the HTML 4.01 specification to
see what they say; that specification says that q must be rendered with
quotations, and that users should not add their own quotes. It goes on to
say that the quotes should be rendered in a language-sensitive manner. See
the section on rendering quotations:
http://www.w3.org/TR/REC-html40/struct/text.html#edef-QShould we make a similar statement? I do not want to add behaviors that
MUST be done without consulting the full TC, so - this is my
consultation.
Thanks -
Robert D Anderson
IBM Authoring Tools Development
Chief Architect, DITA Open Toolkit
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php