Difference between revisions of "Weblate"

Revision as of 02:20, 1 January 2021

Weblate is a web based translation tool. On 2020-12-14 https://hosted.weblate.org/projects/gnucash/ was created.

Status

consider it still as experimental.

This page is organized by roles.

General

Many pages @ weblate link context sensitive help by i in a circle.

Weblate Documentation

Setup

Glossary

It tries to collect the common GnuCash specific terminology of all other components.

After it is completed, it can be uploaded into Weblates Gnucash glossary.

Currently it is using and ancient style of context "context: term" as MsgId.

Questions and tasks

1. Should MsgId "context: term" be converted to MsgContext, MsgId? Pros and cons?
2. Review of sources for updated lists
3. Other missing conventions?

Website

Set priority (default=100) to

105 for location:global

104 for location:header

103 for location:menu

102 for location:footer

101 for location:index

100 (remains)

99 for location:2.6-release

Translator

Everybody

can add suggestions as anomymous.

Everybody with a weblate account

can translate and gets mentioned in the po file. In the current configuration a review is required.

Our former language maintainers

are asked to tell us their weblate name, to get Review rights.

Ideally no checks should fail. In some cases, the mistake is in the source string. Then please report them by a comment or label.

Coder

With weblate you get feedback, where Translators have problems with your messages. Overview Program Source Messages Tasks by priority:

1. label:"Source needs review"
2. Multiple failing checks This is usually an indication that something could be done to improve the source string. Info

Tip

In both cases at the bottom select

1. Comments,
2. Other languages

to get an impression of the problem.

Maintainer

Concept

Weblate is more anarchistic than our hierarchical thinking with core devs accepting or rejecting patches:

Project settings

Some are derived from our status as libre hosted project.

https://hosted.weblate.org/settings/gnucash/#access is set public meaning:

• visible for all,
• every registered user can translate,
• unregistered can attach suggestions.

To avoid chaos in https://hosted.weblate.org/settings/gnucash/#workflow

• Review is activated, ideally a Gnucash Language :Team should have at least 2 reviewers (and unlimited users), confirming each others changes.

Component settings

Suggestions are enabled, but Suggestion voting and Autoaccept suggestions are currently not.

Lazy commits

The changes in this mode are committed once any of the following conditions are fulfilled:

• Somebody else changes an already changed string.
• A merge from upstream occurs.
• An explicit commit is requested.
• Change is older than period defined as Age of changes to commit on Component configuration.

Workflow

If Pushs (of Pull Requests)^[1] are disabled, you can get the current status of commits at https://hosted.weblate.org/projects/gnucash/#repository or do it separate for real components.

Tip

Set URL=https://hosted.weblate.org/git/gnucash/gnucash/ # for gnucash (program and glossary) or

URL=https://hosted.weblate.org/git/gnucash/website/ # for ht-docs, then

git remote add weblate $URL

to your repo. Then you can preview pending commits by:

git fetch weblate

If there are pending commits

1. Only required, if GitHub Settings->Hooks are misconfigured: rebase the weblate repo(s):
   • all together: https://hosted.weblate.org/projects/gnucash/#repository
   • or per component: https://hosted.weblate.org/projects/gnucash/gnucash/#repository …

   you need to zoom the window to see the buttons;

   Reason: merge conflicts would lock the repository;

2. Only required, if Push on commit^[1] is disabled: push, to create PRs;
3. review at github

   Note

   Because not all weblate users must be github users, it would be nicer to comment on the changes at weblate. This needs more research.

4. merge the PRs via code.gnucash.org;
5. rebase weblate. Now all lines should show 0.
6. ↑ ^{1.0 1.1} The first commit create a Pull Request at Github. On each further commit the PR is force pushed. After the PR is merged (or otherwise closed?), the whole procedure starts again. That means you will have to rebase your interim work on the repo.