translations

[shanejonas]

There are 2 separate things to consider with translations:

1. As a developer, I'd like the OpenRPC spec translated to different languages, maybe the spec.open-rpc.org website that is generated can support loading different languages via a dropdown?

2. As a user of the documentation or generated tooling, I'd like the descriptions in different languages, could start out as a plugin maybe x-description-fr for french as an example.

[BelfordZ]

All for people maintaining mirrored translated copies of the spec. However, It's hard enough writing specification-worthy english, I cannot agree to maintaining official translated versions at this time.

That being said, perhaps you could add a link on the website repo to translated versions.

[BelfordZ]

@ChrisXK Please do not post links to downloadable documents here. Microsoft word is potentially a publishing format, but it's not acceptable to post here due to security concerns. I hope you understand.

Can we discuss a way to have the spec translated in an ongoing, maintainable fashion?

A good solution should:

• Allow the spec to be maintained in english. For now, all contributions must be made in english.
• When a pull request is merged that changes the spec, a new set of translation tasks are created for the change set.
• New github issues are created with the requested translations, and assigned to our translation buddies
• When the issue is closed, a bot sweeps the closed translation issues and makes a PR adding the translations into a 'translation map': a structure for getting the translated copy of a given paragraph of text.
• update the publish process to include publishing for multiple languages.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.