Martin Michlmayr wrote: > I've read this page: http://www.w3.org/TR/i18n-html-tech-lang/ > in the meantime which explains the best practice. > > In short: > > - HTML 5: use <html lang = "..."> > > - XHTML 1.0: use <html lang="..." xml:lang="..." xmlns > ="http://www.w3.org/1999/xhtml";> > > - XHTML 1.1: use <html xml:lang="..." xmlns ="http://www.w3.org/1999/xhtml";> > > The patch below implements this: > > - it uses the lang_code template variable (already defined by po) to > put the language into page.tmpl
Well, po's LANG_CODE template variable is used on translated pages, to show the language code of the translation. Although this is only provided, AFAICS nothing uses that variable in the current template. A meta lang should surely only affect the "master" page, not change the LANG_CODE for translation pages too. I have not verified to my satisfaction that this gets along right with po. Beyond that one template variable, there's the question of how this should interoperate with po generally. Since po assumes that all pages are in one "master" language, using it in addition to meta lang would result in some confusion like a page that claims in the html header to be the meta lang set value, but has po-plugin inserted content that indicates it's in eg, English. -- see shy jo
signature.asc
Description: Digital signature
