Skip to content

Russian translation#6516

Merged
MichaelChirico merged 5 commits intomasterfrom
gettext-russian
Jan 31, 2025
Merged

Russian translation#6516
MichaelChirico merged 5 commits intomasterfrom
gettext-russian

Conversation

@aitap
Copy link
Member

@aitap aitap commented Sep 21, 2024

First of all, big thanks to @Meeko28 and @Kate-lz! This would have never been possible without your work. I hope that you've received your grant payouts, or at least that the paperwork is on the way.

The *.po files are prepared against the current *.pot files, so a few of the strings containing fragmented sentences have been left untranslated.

Questions:

  • Should this pull request be WIP until all the *.pot files are updated? I've got to submit some edits for the R message templates too, and the vignettes and the help pages may need their own rounds of editing too.
  • Where do I put the data.table.ru package with the three vignettes (intro, reshape, importing) and (currently) 25% of the help pages translated? I ended up using a po4a-based workflow for the vignettes (thank you very much @phgrosjean for the hint) and a similar but more handmade workflow for the help files. The resulting package (when built) depends on only data.table and suggests a few of its dependencies (to build vignettes and run examples).

@aitap aitap added the translation issues/PRs related to message translation projects label Sep 21, 2024
@Meeko28
Copy link
Contributor

Meeko28 commented Sep 21, 2024 via email

@MichaelChirico
Copy link
Member

Should this pull request be WIP until all the *.pot files are updated?

Yea, given our normal workflow is to update .pot near release time, I think it's not ideal to trigger the update now... if it's not too much trouble, we could "left join" the the current .pot to your translations as a PR to merge now, then leave this one pending until the .pot is updated (which will probably end up invalidating some translations here).

@aitap
Copy link
Member Author

aitap commented Sep 30, 2024

we could "left join" the the current .pot to your translations as a PR to merge now

Let's try this. I've ran msgmerge -U on both files, so the new translations we had prepared with a manually generated data.table.pot should be commented out, ready for reuse.

@aitap
Copy link
Member Author

aitap commented Oct 2, 2024

Should I be preparing a new pull request? I think the current branch will msgmerge cleanly against the current *.pot.files.

@codecov
Copy link

codecov bot commented Oct 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.60%. Comparing base (32dfd8d) to head (9ccfdcd).
Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #6516   +/-   ##
=======================================
  Coverage   98.60%   98.60%           
=======================================
  Files          79       79           
  Lines       14642    14642           
=======================================
  Hits        14438    14438           
  Misses        204      204           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@MichaelChirico
Copy link
Member

Sorry @aitap, haven't had time to look closely. Will report back soon :)

@MichaelChirico
Copy link
Member

A new .pot will be generated shortly -- do you want to merge this as-is and start a second PR once that's done, or is it easier to have only one PR? I'm OK either way @aitap

@aitap
Copy link
Member Author

aitap commented Jan 30, 2025

Let me update this one.

@aitap aitap marked this pull request as draft January 30, 2025 15:09
aitap and others added 4 commits January 31, 2025 13:57
Co-authored-by: Nichole Haines <meeko28@users.noreply.github.com>
Co-authored-by: Kate Zhevelyuk <kate-lz@users.noreply.github.com>
Co-authored-by: Nichole Haines <meeko28@users.noreply.github.com>
Co-authored-by: Kate Zhevelyuk <kate-lz@users.noreply.github.com>
Unfortunately, Gettext doesn't like the %.0s workaround for %s => plural
"s" and gives a warning for different conversion specifiers.
There's probably a better way to avoid translating the "this document is
also available in the following languages:" paragraph.
@aitap aitap changed the title Russian translation of the gettext messages files Russian translation Jan 31, 2025
@aitap
Copy link
Member Author

aitap commented Jan 31, 2025

I think it's done. The individual commits can be omitted or split off if needed.

@aitap aitap marked this pull request as ready for review January 31, 2025 11:15
Copy link
Member

@MichaelChirico MichaelChirico left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent, thanks!!

@MichaelChirico MichaelChirico merged commit b089b74 into master Jan 31, 2025
10 checks passed
@MichaelChirico MichaelChirico deleted the gettext-russian branch January 31, 2025 14:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

translation issues/PRs related to message translation projects

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants