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

Language Display and Selection #778

Open
austinmatherne-wk opened this issue Dec 6, 2024 · 0 comments
Open

Language Display and Selection #778

austinmatherne-wk opened this issue Dec 6, 2024 · 0 comments
Labels
request New feature or request

Comments

@austinmatherne-wk
Copy link
Contributor

What should we change and why?

In the settings menu we display the "Document Language" and "Application Language". It's not clear what the "Document Language" term refers to.

Screenshot 2024-12-06 at 3 04 35 PM

There are actually three separate language concepts in the viewer:

  1. The language of the HTML content in the report:
    • This refers to the lang attribute in the XBRL inline report, which can be undefined. Some users think this is what "Document Language" refers to.
  2. The language of taxonomy details (e.g., labels in the inspector panel):
    • This depends on the languages supported by the XBRL taxonomy. In the menu, this is what's currently labeled as "Document Language."
  3. The language of the application's user interface:
    • This includes elements like the "Untagged Numbers" checkbox. It's consistent across all viewers and depends on the languages we've translated the app into (currently English, Welsh, and Spanish).

To reduce confusion, I suggest we clarify all three in a languages section of the menu with tooltips explaining their purpose. Here's how it could look:

  1. Document Language:
    • Show the actual language of the report document (if defined by the lang attribute). This is informational only and cannot be changed by the user.
  2. Taxonomy Language:
    • List the available taxonomy languages, allowing users to select one. The default would follow this priority:
      1. A saved taxonomy language from local storage (if the user has selected one in the past).
      2. The browser language.
      3. The document language.
      4. English (as a fallback).
      5. Any other available language (as a last resort).
  3. Application Language:
    • List the available UI languages, also user-selectable. The default would follow this priority:
      1. A saved UI language from local storage (if the user has selected one in the past).
      2. The browser language.
      3. English (default fallback).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant