Add Spanish (es) version of website pages

[krol3]

Following the samples of Japanese and Portuguese version of websites. We would like to support the Spanish website page and translations for the docs.

We'll use this issue to track the added support of a sp (Spanis) localization.

Tasks

• Figure out which Spanish variety we are going to use (es_ES?, edited by @svrnm)
• Create homepage - [es] Localize index page to Spanish:
  • [es] Create homepage for Spanish localization #4989
  • Add mount points for es pages #5005
• Create an issue label for lang:es
• Create org-level groups for es maintainers and approvers:
  • @krol3 - you'll want to identify / list maintainers and approvers
  • @open-telemetry/docs-approvers will follow through and create the appropriate request for the group creation:
    New teams docs-es-approvers and docs-es-maintainers community#2262
• Update code/component owners
• Other pages (can be done outside of the scope of this issue):
  • Add Spanish translation for "What is OpenTelemetry" - [es] Add What is OpenTelemetry to Spanish site #5021
  • https://opentelemetry.io/ - [es] Localize index page - [es] Create homepage for Spanish localization #4989
  • https://opentelemetry.io/docs/demo/ - [es] feature: demo structure - spanish translation #5053
  • https://opentelemetry.io/docs/getting-started/ - [es] feature: getting started - spanish translation #5054
  • https://opentelemetry.io/docs/kubernetes/ - [es] kubernetes - spanish translation #5055
  • https://opentelemetry.io/docs/concepts/ - [es] feature: concepts - spanish translation #5057
  • https://opentelemetry.io/docs/contributing/ - [es] feature: contributing - spanish translation #5058

References

• Site localization
• Improved i18n support

cc: @chalin

[svrnm]

Hey @krol3,

thank you for raising this issue! Having a spanish translation of the OpenTelemetry website is something we are looking forward to have, so thanks for offering your help!

Localization & Internationalization is still a new topic to use, so we are at the moment intentionally slowing down the onboarding for new languages, to avoid overburdening maintainers and to avoid you having a bad experience. I say this upfront because it may take a few weeks until we can successfully add a new language.

Saying all that, here are the next steps:

• Find at least 1 more (ideally 2) people that are willing to help with the translation, such that someone who does the translation always has a person that can do the review.
• Create a PR for the homepage (and nothing more), following the example of other languages, e.g. pt. Leave editing the hugo.yml to us, we will update your PR accordingly
• Wait for this PR to be merged (this is where we might put a delay)
• We will after the PR has been merged setup the rest of the language (adding labels, groups, etc.)

[svrnm]

@krol3 @theletterf based on a discussion during the SIG meeting I updated the issue description, that as a first step we need to agree on the Spanish Variety

[chalin]

As discuss during the (end of the) Comms meeting: which ever Spanish regional variant @krol3 et al. decide upon, that will become the defacto/default region for the OTel docs. We'll eventually need to choose a language code (see below for choices), but regardless, the content subfolder will be es.

Here are some of the most commonly used Spanish language codes that start with es-:

• es-ES: Spanish (Spain)
• es-MX: Spanish (Mexico)
• es-AR: Spanish (Argentina)
• es-CO: Spanish (Colombia)
• es-PE: Spanish (Peru)
• es-VE: Spanish (Venezuela)
• es-CL: Spanish (Chile)
• es-419: Spanish (Latin America and the Caribbean)

Maybe either es-419 or es-ES, WDYT?

[krol3]

As discuss during the (end of the) Comms meeting: which ever Spanish regional variant @krol3 et al. decide upon, that will become the defacto/default region for the OTel docs. We'll eventually need to choose a language code (see below for choices), but regardless, the content subfolder will be es.

Here are some of the most commonly used Spanish language codes that start with es-:

• es-ES: Spanish (Spain)
• es-MX: Spanish (Mexico)
• es-AR: Spanish (Argentina)
• es-CO: Spanish (Colombia)
• es-PE: Spanish (Peru)
• es-VE: Spanish (Venezuela)
• es-CL: Spanish (Chile)
• es-419: Spanish (Latin America and the Caribbean)

Maybe either es-419 or es-ES, WDYT?

Following the kubernetes documentation spanish translation, we don't use a local/region/country variant in spanish. We collaborate with each other to translate to spanish (es).

[theletterf]

+1 to what @krol3 said. If we can just go with the root (es) I'd do that.

[theletterf]

@krol3 For the priority pages, I was thinking of the same list as pt-BR, plus perhaps the contribution guide. What do you think? #4922

[svrnm]

@theletterf based on our conversation on Monday, I was under the assumption that while we are going to use es we still need to agree on the defacto variant that we use (similar to what we do with pt and zh).

[theletterf]

@svrnm I've no strong feelings about it at this stage. I'd go with es-ES, but I'm guessing here that K8s chose to go with just es to foster contributions and avoid conflicts with lexical variants. FWIW, their site reads as es-ES; I doubt regional vocabulary from all around the Hispanosphere will ever make it to the docs — and we'll edit it if it does.

[theletterf]

lang:es label created.

[theletterf]

Opened open-telemetry/community#2262 to request the creation of the groups.

[theletterf]

Created #4989

[krol3]

Hey @krol3,

thank you for raising this issue! Having a spanish translation of the OpenTelemetry website is something we are looking forward to have, so thanks for offering your help!

Localization & Internationalization is still a new topic to use, so we are at the moment intentionally slowing down the onboarding for new languages, to avoid overburdening maintainers and to avoid you having a bad experience. I say this upfront because it may take a few weeks until we can successfully add a new language.

Saying all that, here are the next steps:

• Find at least 1 more (ideally 2) people that are willing to help with the translation, such that someone who does the translation always has a person that can do the review.
• Create a PR for the homepage (and nothing more), following the example of other languages, e.g. pt. Leave editing the hugo.yml to us, we will update your PR accordingly
• Wait for this PR to be merged (this is where we might put a delay)
• We will after the PR has been merged setup the rest of the language (adding labels, groups, etc.)

Hi @svrnm , I would like to propose to help in the Spanish translations to @electrocucaracha, @ramrodo. They're contributors and maintainers in the k8s website. I know more people will be interesting to help too.

[krol3]

Here are some of the most commonly used Spanish language codes that start with es-:

• es-ES: Spanish (Spain)
• es-MX: Spanish (Mexico)
• es-AR: Spanish (Argentina)
• es-CO: Spanish (Colombia)
• es-PE: Spanish (Peru)
• es-VE: Spanish (Venezuela)
• es-CL: Spanish (Chile)
• es-419: Spanish (Latin America and the Caribbean)

Maybe either es-419 or es-ES, WDYT?

hi @theletterf yeah I will prefer just "ES" for the code spanish language, and don't use the region or country. For example in the kubernetes spanish documentation we use "ES". The contributors are from Guatemala, El Savaldor, Peru, Mexico, etc. We all colaborate to the ES language.

[ramrodo]

I agree with @krol3 , at the official Kubernetes documentation we use es to avoid region word conflicts and variants. The es dictionary is valid and available at cspell:

https://github.com/streetsidesoftware/cspell/blame/main/packages/cspell-trie-lib/src/lib/models/locale/knownLocales.ts#L197

[chalin]

Thanks @ramrodo for the reference into the cSpell code. IMHO, that says that es is recognized as a valid language code, but that doesn't give us an es dictionary. I'm not aware of an es dictionary, only an es-ES one via:

• https://github.com/streetsidesoftware/cspell-dicts
• Specifically, https://github.com/streetsidesoftware/cspell-dicts/tree/main/dictionaries/es_ES#readme

In summary, we can adopt es as the language code used as the folder name below content, but if we enable spell checking, then either you'll need to supply a "generic" es dictionary, or we'll go with the es_ES one.

[theletterf]

@svrnm Could component owners be updated without waiting for the OTel community issue to be solved?

[svrnm]

@svrnm Could component owners be updated without waiting for the OTel community issue to be solved?

Without the team being in place the process would run into an error everytime it runs. I am annoying people already to create the teams.

[theletterf]

@krol3 All initial actions completed. I'd close this task and follow with PRs.

Example: #4922