Internationalization (i18n) and localization (l10n) #4302
Replies: 10 comments 21 replies
-
Thanks @svrnm for the heads up. The reasons why Japanese documentation doc has been stalled were:
I am personally super happy for this main repo to support i18n and we can contribute to the single destination. |
Beta Was this translation helpful? Give feedback.
-
+1 support for docs-cn. Happy to see the progress 👍 |
Beta Was this translation helpful? Give feedback.
-
@ymotongpoo, @windsonsea, @katzchang an important document for us all to review are the hugo and documentation in i18n&l10n: Additionally, here is the Localization Guide from Kubernetes: |
Beta Was this translation helpful? Give feedback.
-
following up on this, a few points on what needs to be done:
Thanks |
Beta Was this translation helpful? Give feedback.
-
@svrnm thanks for the update.
Does the set mean the subset of the current web site? If so, I personally think, the following can be the first milestone for i18n:
|
Beta Was this translation helpful? Give feedback.
-
Yes, exactly. The list you suggested is a good starting point, here are a few additional ones:
for the collector pages we might skip a few ones that are very specific and detailed (especially those around building your own components) |
Beta Was this translation helpful? Give feedback.
-
@katzchang @ymotongpoo @windsonsea we talked about localization during the SIG Comms meeting today. We want to provide a very low barrier for you to get started, so based on a proposal by @chalin here's how we want to kick this off:
I hope this helps you to get started quickly. If you have any questions, let us know here or in the #otel-comms slack space. If it helps we can also schedule an additional meeting that accomodates your timezones. Thanks, |
Beta Was this translation helpful? Give feedback.
-
https://opentelemetry.io/zh/ just landed as a first start! |
Beta Was this translation helpful? Give feedback.
-
@open-telemetry/docs-approvers @open-telemetry/docs-zh-approvers: do we want to implement a mechanism that will help For example, given that a Alternatives to the use of permatlinks could be one of the following front-matter fields:
I've posted to the Hugo forum to see if anyone else has tackled this issue: https://discourse.gohugo.io/t/measuring-multilingual-page-translation-drift/50090. |
Beta Was this translation helpful? Give feedback.
-
I volunteer to co-own docs-zh! I'm a native Chinese speaker and I have been learning and using opentelemetry recently. I found that the Chinese documentation on the official website is incomplete and very glad to participate in its improvement . I'm just not sure if I need any other experience to qualify for this work. |
Beta Was this translation helpful? Give feedback.
-
The purpose of this discussion is to have a central place to talk about the long-term goal to provide i18n and l10n for the OpenTelemetry Website and Documentation. Previous issues on this topic:
As of today there also exist to separate repositories housing localizations (https://github.com/open-telemetry/docs-cn and https://github.com/open-telemetry/docs-ja, although
docs-ja
has not been updated in ~2years).Last guidance on how we can accomplish a multi-language version of our website was the following (#2402 (comment)):
As stated above this project requires a set of individuals that are happy to take on ownership for their language and work with SIG Comms on implementing this. So any discussion on this page "how to do it" needs to be preceded by a "I volunteer to co-own
<language>
"cc @open-telemetry/docs-maintainers
cc @open-telemetry/docs-cn-maintainers
cc @ymotongpoo @katzchang @shirou (for docs-ja)
Beta Was this translation helpful? Give feedback.
All reactions