HI Leif.
On 21 February 2013 12:53, Leif Halvard Silli <
xn--mlform-iua@xn--mlform-iua.no> wrote:
> The main benefit here is to introduce the new isolation behavior. Thus
> by first doing <html dir="auto">, you can, if you want, continue to tag
> languages like you do today. So you could e.g. do this:
>
> <html lang="he" dir="auto"><body dir="rtl">Lorem.</body></html>
>
> This would work both in legacy browsers and in updated browsers.
>
so for unsupported AND supported languages we'd have the markup up:
<div lang="langcode" dir="auto">
<div dir="rtl">Lorem Ipsum</div>
</div>
which would make the idea of automatically applying direction based on
language redundant, wouldn't it?
Since for backwards compatibility and for unsupported languages the markup
would be the same the same. And for environments where you need to use both
supported and unsupported languages, the markup would still have to be the
same?
--
Andrew Cunningham
Senior Project Manager, Research and Development
Social Inclusion Unit
Public Libraries and Community Engagement
State Library of Victoria
328 Swanston Street
Melbourne VIC 3000
Australia
Ph: +61-3-8664-7430
Mobile:
Email: a <andrewc@vicnet.net.au>cunningham@slv.vic.gov.au
http://www.openroad.net.au/
http://research.vicnet.net.au/
http://www.mylanguage.gov.au/
http://www.vicnet.net.au/
http://www.slv.vic.gov.au/
Received on Tuesday, 26 February 2013 00:50:12 UTC