Translation does not work in Logged Out Page and Apply Filters in Unified Search

Hi,

We are using Elasticsearch 8.7.1 and some actions does not be translated.

How to solve this problem?


Captura de Tela 2023-07-13 às 11.49.19

Captura de Tela 2023-07-13 às 11.51.59

Kibana supports translations in French, Japanese, and Chinese.

Where does your translation from Portuguese come from?

I created my own translation file with this instructions

like this guy does in Russian

I don't know why some parts still in English.

Captura de Tela 2023-07-25 às 12.49.10

Captura de Tela 2023-07-25 às 12.49.19

Captura de Tela 2023-07-25 às 12.49.32

Captura de Tela 2023-07-25 às 12.49.48

Sorry I could not replicate your issue, check a couple of examples I could locate from your screenshots:

What I did is:

  • Start a development environment from the main branch of the Kibana repo
  • Copy the fr-FR.json as es-ES.json to start with texts in French
  • Add i18n.locale: "es-ES" to my kibana.dev.yml configuration file
  • Add the translation to the x-pack/.i18nrc.json file
    "@kbn/translations-plugin/translations/es-ES.json"
  • Locate a few messages in es-ES.json and translate them
  • Start the Kibana development server

I'm not sure if you need to run yarn kbn bootstrap for the translations to be picked up, but other than that the translations are showing correctly on my environment.

Does this help?

I think the problem is because we use i18n.locale: "pt-BR"

Original French file, saved as fr-FR.json, everything it is ok:

Same original French file, but now saved as pt-BR.json: some text blocks aren't translated

If we use i18n.locale: "es-ES" with our "pt-BR.json" renamed to "es-ES.json" it works! :thinking:

But in this cenario, the days of the week and months of the year stay in Spanish. :sob:
Captura de Tela 2023-07-25 às 18.15.39

The same if we use i18n.locale: "ru" with pt-BR translations inside "ru.json" file. Everything stays in Portuguese, except the days of the week, the months of the year....
Captura de Tela 2023-07-25 às 18.26.11

I tried to use "pt-PT" or "pt" and in this cases the result is same as "pt-BR": some parts still in English.

Hi @wsbr, just checked with the team and you indeed need to tweak this file to include those strings

For reference, this topic, actually also for Portuguese, was discussed on this other thread

Cheers!

Thank you a lot! It worked perfectly.

I suggest to commit the pt / pt-BR in the main code.

1 Like

Issue created

PR requested

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.