A Weblate instance for data.table translations?

Open
#6,370 25 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
r
Domain
documentation, localization

Research direction

Start by reading the Weblate and Codeberg Translate links, then inspect the translation paths mentioned: src/library//po/.po and vignettes/datatable-intro*.Rmd. The issue does not define an agreed instance, project setup, or acceptance criteria, so what counts as done must be decided before implementation.

Written by the indexing model from the issue text.

Description

translation

Cc: @tdhock

Dear @Rdatatable/translators,

Would any of the existing translation teams be interested in moving to a Weblate instance?

Many languages supported by the R project itself are now being translated on the translate.rx.studio instance instead of translation team leaders manually submitting archives of src/library/*/po/*.po files to the R core team shortly before a new version is released. Having participated in both processes, I must say that Weblate is more convenient (because someone else manages the repositories and regularly prepares patches), although of course tastes can differ.

It turns out that while Weblate's Markdown mode does not understand R Markdown well enough, it's still possible to translate the vignettes as plain text files. Every vignette will have to become a new translation project, with a file format of Plain text file, the file mask specifying the future translated vignettes as (for example) vignettes/datatable-intro-*.Rmd and a separately specified monolingual base language file vignettes/datatable-intro.Rmd:

Weblate screenshot showing settings for a "plain text" translation of the data.table intro vignette

You will have to disallow adding new translations, but as soon as a file matching the mask appears in the repository (e.g.), Weblate will recognise it as available for translation (e.g.).

@daroczig, if a data.table language team desires to move to https://translate.rx.studio, would it be possible to create data.table as a project there?

Alternatively, Codeberg Translate is a public Weblate instance hosted by Codeberg, where any free software project can get translated into various languages. We could register https://translate.codeberg.org/projects/data-table/ for the overall project. I was not aware of the option to move to https://translate.rx.studio, so the Russian translation team is currently set up at https://translate.codeberg.org/projects/data-table-ru/, but I could definitely move to https://translate.rx.studio or https://translate.codeberg.org/projects/data-table/ after we are done if that becomes an option.

Dominant language
R
Stars
3.9k
Forks
1.1k
Avg merge
14h 4m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Rdatatable/data.table

All issues in Rdatatable/data.table

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.