[Bug 10807] i18n comment 1 : new attribute: ubi

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10807

--- Comment #17 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-10-19 06:16:14 UTC ---
Ok, now we're getting somewhere. Thanks. This is why use cases are more
important than proposed solutions. Bugs should always be focused on problems
first, not proposals.

(by the way, please don't quote the whole comment you're replying to,
especially if it's immediately above your comment, as it just makes reading the
bug more difficult.)

(In reply to comment #14)
> 
> It is quite a common occurrence that the item needing isolation is already
> wrapped in an element like <a> or <q> or <span> (or <output>). [...]
> But having to wrap such items in *two* elements, e.g.
> <a><ubi>BLAH BLAH</ubi></a> - or is it <ubi><a>BLAH BLAH></a></ubi>, is surely
> rubbing salt in the wounds. An attribute with a short name and no need to
> specify a value is a lot less painless to use.

By that argument, we shouldn't have <bdo>, or indeed <a> (many links are given
on elements that are already in the markup) or indeed many of the phrasing
elements... I don't think that argument holds water.


Given the use cases of text that need isolation, I agree that <output>'s
semantic is inappropriate.

Is it the case that all these cases should also have a language specified? All
the examples so far seem to be english text mixed in with hebrew; would it be
correct to say that they should all be marked up with lang="" attributes? If
so, can we just make all elements with lang="" attributes have
unicode-bidi:isolate? Or are there examples of where setting the language
doesn't change (and you do know the language doesn't change, it's not just that
you don't know the language) but you still want this isolation behaviour?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You reported the bug.

Received on Tuesday, 19 October 2010 06:16:19 UTC