open-telemetry / open-telemetry/weaver
I18N support proposal
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 489
- Forks
- 108
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 40
Description
In theory, in a resolved registry, all fields are addressable by fully qualified and unique IDs. Therefore, we should be able to adapt Weaver—assuming we have an i18n file for each field (fully_qualified_field_id -> Translated Text)—to resolve a semconv registry for a specific language and generate documentation, code, or even configuration files accordingly.
The i18n files don't need to be fully complete. We can introduce commands to detect:
- missing translations,
- invalid fully qualified IDs,
- ...
To be defined: Develop a strategy to ensure this approach is compatible with the multi-registry project.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by defining how i18n files keyed by fully qualified field IDs fit the multi-registry project, then specify the commands for missing and invalid translations and the documentation, code, or configuration outputs that must be supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation, localization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100