This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
4.6.7 The q element http://www.w3.org/TR/html5/text-level-semantics.html#the-q-element Not discussed in the i18n WG yet, but tracked by i18n tracker. [I'm putting this here as a placeholder, since we're near to the end of last call, and i need more time to consider and discuss but will be away on vacation.] I'm wondering whether we need a way to reset the embedding levels of quotes. This may involve markup, rather than just CSS (that's what I need to think more about). Here's the reason: If you have the following CSS: :lang(en) > * { quotes: '"' '"' "'" "'"; } :lang(no) > * { quotes: "«" "»" '"' '"' } And you have <p lang=no>Some Norwegian text <q>more norwegian <q>more norwegian</q></q>.</p> You'd expect to see Some Norwegian text «more norwegian "more norwegian"». which perfectly fine. But if you had <p lang=en>Some English text <q lang=no>Some norwegian <q>more norwegian</q></q>.</p> Then I think you'd see Some English text "Some norwegian "more norwegian"". I'd have thought that the quotes surrounding the text 'more norwegian' here should be surrounded by «...». This could maybe be done by a rule that says that if a q element carries a lang attribute, the next embedded q attribute should use the highest level quote marks. Or perhaps it needs some attribute to reset the levels? (which is why this comment is here) In addition, maybe that would also give you more control over how the quotes are used in other situations (such as to replicate the original text) - although perhaps that's best achieved using special class names or just by avoiding q altogether.
This should be brought up in the CSSWG; there is absolutely nothing here that HTML needs to care about.
Yes, I suspect that that is true, but I wasn't totally sure that we weren't looking at markup to do the reset function. That's why I put this here. But I do also intend to send the comment to CSS too.
(In reply to comment #0) [I agree that this has to go to CSS, but just a short comment while it's here.] > But if you had > > <p lang=en>Some English text <q lang=no>Some norwegian <q>more > norwegian</q></q>.</p> > > Then I think you'd see > > Some English text "Some norwegian "more norwegian"". > > I'd have thought that the quotes surrounding the text 'more norwegian' here > should be surrounded by «...». This could maybe be done by a rule that says > that if a q element carries a lang attribute, the next embedded q attribute > should use the highest level quote marks. That won't work always, because there may be other languages where "" is the quote convention on the top level, as for English, and you'd still end up with text where you don't really see what starts where and what ends where. > In addition, maybe that would also give you more control over how the quotes > are used in other situations (such as to replicate the original text) - > although perhaps that's best achieved using special class names or just by > avoiding q altogether. I guess you can always write some rule like :lang(en) > :lang(no) > * ... or maybe even something more generic. You don't need classes or HTML attributes for that. It won't work out of the box in a browser, but it's easy to put that in your own stylesheet unless you have hundreds of combinations of languages. Regards, Martin.
mass-moved component to LC1
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: I'm marking this bug WONTFIX because there doesn't seem to be a way to reassign bugs to the CSSWG. :-(