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

Remove English translations? #18307

Open
wkeese opened this issue Jan 8, 2025 · 0 comments
Open

Remove English translations? #18307

wkeese opened this issue Jan 8, 2025 · 0 comments

Comments

@wkeese
Copy link
Contributor

wkeese commented Jan 8, 2025

I would like Carbon to provide translations for all the boilerplate text (expand, collapse, etc.) in all the languages. However, you said in #9474 that you aren't going to do that. Instead, the application needs to provide the translations.

Carbon does provide the English strings, which is helpful for applications that only run in English.

However, that also means that IBM applications get no indication when they forget to provide translations. Typescript checking doesn't catch the problem, nor does PropTypes. They might catch the errors during manual localization testing.

However, there's almost no chance of catching untranslated ARIA labels, because accessibility-checker has no way to catch them, and nobody does manual tests for accessibility in "foreign" languages.

So, although Carbon is trying to be helpful by providing default English text, it's really encouraging low quality in most IBM applications.

Would it be better to just remove the English translations, so at least there's not the false sense that things are working when they aren't?

CC @tay1orjones @jeffchew

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant