accrescent / meta

Umbrella Accrescent issue tracker
6 stars 1 forks source link

Provide multiple language translations #5

Closed lberrymage closed 1 year ago

lberrymage commented 2 years ago

The scope of this issue is determining how we can provide accurate and timely translations for the Accrescent client, developer portal, web pages, etc.. There are many different approaches to this so we need to carefully consider which languages to support, who does the translations, how much translations will cost, and how maintainable they will be.

This is a long-term goal. I don't expect to be able to fairly evaluate all options until Accrescent is stable and has a sizeable user base.

lberrymage commented 2 years ago

For now we'll be taking the following best-effort approach to translation acceptance and maintenance:

lberrymage commented 2 years ago

For now we'll be taking the following best-effort approach to translation acceptance and maintenance:

  • missing translations will not be a blocker for code that adds new string resources
  • very out-of-date translations may be removed after a period of time
  • new translations should have at least one review from a fluent speaker of the language in question

Since the addition of Weblate I'm willing to make a few concessions for the sake of encouraging translations in the early stages when there are few translation reviewers. Specifically, new translations will not usually require review but trusted reviewers will be able to lock individual strings as "approved" after which they will only be directly modifiable in Weblate by said trusted reviewers. Others can still suggest changes to such strings.

Changes to existing translations provided by someone else should ideally come with reasoning for the change if not approval by other translators. This requirement is pretty lax for now but will likely become enforced more strongly as time goes on.

Of course all of this is subject to change since we just set up translations, the Weblate setup is recent, and Accrescent isn't even in production yet. I'm open to feedback.

lberrymage commented 1 year ago

Weblate seems to be working well so far so I'm going to close this issue since the overall goal of providing multiple translations is accomplished (at least for the client). Other issues should be created for Accrescent subprojects as the need arises.