Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@lang attributes missing in HTML output #2114

Open
martindholmes opened this issue Feb 16, 2021 · 4 comments
Open

@lang attributes missing in HTML output #2114

martindholmes opened this issue Feb 16, 2021 · 4 comments

Comments

@martindholmes
Copy link
Contributor

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.

@sydb
Copy link
Member

sydb commented Feb 16, 2021

Problem verified.
Seems like a (reasonably bad, hopefully not too hard) Stylesheets issue to me.

@corbane
Copy link

corbane commented Feb 22, 2021

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.

@martindholmes
Copy link
Contributor Author

@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.

@sydb
Copy link
Member

sydb commented Mar 19, 2021

@martindholmes is right, but that is no excuse (IMHO) for the various chunks of stuff in other languages not to have a proper @lang.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants