You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the root html element has lang="en". The element gloss, which is in Japanese, has no @lang attribute. Captions such as "module" and "attributes" have lang="ja", but the actual blocks of content (remarks etc.) are missing the @lang attribute. This will make indexing and rendering a little harder for any person or process that cares about language distinctions.
The text was updated successfully, but these errors were encountered:
I joined this post to avoid duplicates.
A reader or voice / braille translator is unable to work with the documentation pages. There is little semantics and little accessibility to your documentation pages.
The main reason is the lack of indication of the language of an HTML element.
On all pages other than English, there is no lang attribute indicating the switch from English to another language.
The xml examples are simple div elements. They are not surrounded by the code element (indicating the language) and the "pre" element (indicating the formatting).
The notion of language ("es", "fr", or even "xml") is only visual and typographic.
@corbane You're absolutely right. One problem is that for the vast majority of pages, the content of the page is English even if the
"language version" of the Guidelines is not; this is because the prose of the Guidelines is untranslated. The only components that are regularly translated are portions of the specifications pages as well as captions and examples.
This may need a solution in the Stylesheets repo, but I'm raising it here for the moment.
If you visit a Guidelines page in another language, like the Japanese page here:
https://tei-c.org/release/doc/tei-p5-doc/ja/html/ref-activity.html
the root html element has lang="en". The element gloss, which is in Japanese, has no
@lang
attribute. Captions such as "module" and "attributes" have lang="ja", but the actual blocks of content (remarks etc.) are missing the@lang
attribute. This will make indexing and rendering a little harder for any person or process that cares about language distinctions.The text was updated successfully, but these errors were encountered: