- From: Marcos Caceres <marcosc@opera.com>
- Date: Mon, 29 Mar 2010 17:28:53 +0200
- To: "Phillips, Addison" <addison@amazon.com>
- CC: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>, Felix Sasaki <felix.sasaki@fh-potsdam.de>, Arthur Barstow <art.barstow@nokia.com>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>, public-webapps <public-webapps@w3.org>, Richard Ishida <ishida@w3.org>
Hi Addison, On 29/03/10 5:16 PM, Phillips, Addison wrote: > This doesn't make any sense to me. I think you are over-thinking this. > > The author element contains the author's *NAME*. It can also include an href and an email attribute. UTR#36 refers explicitly to IRIs and IDNA addresses, which would be the values of these attributes. However, it does NOT refer to plain text (the body of the element 'author') which is what the 'dir' attribute really applies to. To not provide bidirectional overrides for the author's name strikes me as incredibly short sighted, given that you can override any higher-level element. To have one place in your configuration document that requires controls is not to improve security, it is to reduce usability. Sorry, honest newbie mistake. This is all new to me, so please don't think I'm doing dumb things on purpose. I'll probably make a few more dumb-ass mistakes still, so please be tolerant. > It would make far more sense for you to cite UTR#36 with regard to an implementations presentation of the href or email attributes, suggesting (or forbidding) the application of the dir attribute to these values. But the body of the<author> element needs the bidi markup and should not depend on Unicode bidi controls. Ok, I'll have a go at fixing the text and re-post tomorrow. Kind regards, Marcos -- Marcos Caceres Opera Software
Received on Monday, 29 March 2010 15:29:40 UTC