-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[i18n] replace hardcoded english strings with i18n #127705
Comments
Pinging @elastic/kibana-core (Team:Core) |
I will keep this issue open until 8.2 GA to allow more feedback until the next extraction in May. After this issue is closed I will create another issue for I'm fighting with the exalate-issue-sync to keep this open since I linked it to a resolved task 🙃 |
A user has graciously provided a list of Japanese translations. Based on Kibana 8.1.0.
|
Thank you @rseldner |
Closing this as resolved. If we need another run of testing we'd open a new issue |
There are a few obvious places we have in Kibana that are missing i18n. This issue does not include everything missing; The goal of this issue is to make sure we have decent coverage in each main user flow, landing page, welcome screen, date pickers, sidenave, topnav, etc.
Preparations:
8.2
test cluster to identify missing i18n (French and pseudo english)Missing i18n
Create dashboard
button (https://github.com/elastic/sdh-kibana/issues/2706)Notes
Why are we manually testing coverage?
Unfortunately, we don't have any tooling around testing i18n coverage at the moment. I've opened an issue to discuss supporting frontend coverage to at least have some guarantees on the frontend #127708
Why not aim to have full i18n coverage?
We have 120k+ words in kibana and checking for coverage manually as a diminishing return on time invested. Since we do not have an automated tool to ensure a minimum level of coverage, the level of coverage will keep fluctuating between releases so it is impossible.
Some labels are internationalized but still in English?
8.2
extraction.Canvas
,Kibana
,Elasticsearch
, etc are intentionally left in English by translators. We do not have a list of keywords that we keep in English but I refer to the elastic.co website to see which keywords are not translated when I get asked.The text was updated successfully, but these errors were encountered: