- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Wed, 04 May 2011 12:54:24 -0400
- To: ext Marcos Caceres <marcosscaceres@gmail.com>, Charles McCathieNevile <chaals@opera.com>
- CC: public-webapps@w3.org
On May/4/2011 12:29 PM, ext Marcos Caceres wrote: >> Hi, >> >> I just realised that I actually localise my own name in certain >> languages >> (most particularly to ensure that I get my preferred transliterations >> when >> I am publishing). But I cannot do that in config.xml. Likewise, I would >> like to localise the href for me which would be possible if I could >> localise the author element but isn't at the moment. > > Yes, this was a mistake. > >> I don't now if this is too late for the current version, in which case >> please log it as an issue for the future. > > I think it is too late for this version. We have runtimes now at 99% > and even 100% conformance and adding this would make most runtimes > non-conforming. I think its more important now to push this spec to > REC and address these kinds of cases in a future version of the spec. > >> Changing it to allow >> localisation would mean a change to the schema - and at least to Opera's >> implementation. I haven't yet checked (I only realised I want to do this >> but it isn't allowed today) whether we have any preference for making >> that >> change now or later. > > I think we should definitely add this to any future versions of the > spec. In fact, authors could actually start using multiple localized > author elements today and have them work in the future. > > If it is ok with you, we will add this to a future version of the spec? FYI, the widget spec "v2" feature list is: http://www.w3.org/2008/webapps/wiki/Widgets2_UC%26R
Received on Wednesday, 4 May 2011 16:55:26 UTC