comprehensive-rust
comprehensive-rust copied to clipboard
google
Ukrainian translation
Thanks @git-user-cpp for starting this in #835. This issue is to track the translation. Please read the instructions linked in #282, in particular, please read the translation instructions and the style guide.
The Rust book has been translated into Ukrainian and it would be good to use its terminology where possible.
If there are many translators, consider using this sheet to coordinate the work. This has been helpful for the Chinese and Japanese translations.
Thanks @PetroProtsyk and @yaremam! The first thing to do would be to skim through #835 so we can get it merged. The first commit is always huge, so don't worry about that — we just need the ~73 translated messages proofread and someone needs to click the "Approve" button (anybody can do this).
If you end up being many translators here, then I suggest using the spreadsheet template linked above to coordinate. But it's really up to you — comments on this issue could also be more than enough. I'll let you discuss this with @git-user-cpp.
Merged the initial PR and we can start working on improvements in the next iterations. FYI - there is an amazing vocabulary (proudly borrowed from Rustbook Ukrainian repo) we can reuse & contribute to.
Is anyone actively working on this? I created the spreadsheet from the template above - https://docs.google.com/spreadsheets/d/10is7_b4dTzHTzzAJB067vG2LGEY-VekJFsaVjV1j6DU/ Please request access and pick your files to translate. I am going to start with welcome.md
Hi @yaremam, welcome! I don't think anybody is working actively on this.
Consider using https://github.com/mgeisler/cloud-translate to seed the translation with a machine translation. The results are sometimes hilarious, but sometimes helpful :smile:
You should start by refreshing the PO file by extracting new strings with a 0.2 version of mdbook-i18n-helpers and then run msgmerge. That will give you a gigantic PR which @henrif75 or myself can auto-approve. After that, you can submit smaller PRs for a while.
Can't change the reviewer on the PR to @henrif75 or @mgeisler . Looks like previous version was already using 0.2.2 version of mdbook-i18n-helpers though
I think it is best to split the work by ID range, not by source file. I will update the sheet accordingly, let's divide in ranges of 200 strings, so we can merge the work frequently to the master. Looks like these IDs are generated on the fly by poedit, but the id is simply the order of the string in po/uk.po file, so it should be the same for anyone using poedit. WDYT? List of files in the sheet is outdated. @PetroProtsyk @dyeroshenko
Should we try running cloud-translate? Last time I was using google translator to translate US Army manuals to Ukrainian it produced very good results. @PetroProtsyk @dyeroshenko
Hello guys! I would like to help you with this issue. If there any translations that I can do? @yaremam
@thefirans - pick an available range from https://docs.google.com/spreadsheets/d/10is7_b4dTzHTzzAJB067vG2LGEY-VekJFsaVjV1j6DU/ . You can also try cloud-translate as mentioned here - https://github.com/google/comprehensive-rust/issues/836#issuecomment-1715231643
@yaremam - I translated uk.po file using cloud-translate + made some edits to the translation. But I can't run the book with the updated translation, the book still runs on the default localization (even other localizations are not applied). Can you try to run my uk.po file on your computer?
I am OOO, without a computer, will be back on October 23rd…
пт, 13 жовт. 2023 р. о 16:27 Alex Leoshko @.***> пише:
@yaremam https://github.com/yaremam - I translated uk.po file using cloud-translate + made some edits to the translation. But I can't run the book with the updated translation, the book still runs on the default localization (even other localizations are not applied). Can you try to run my uk.po file on your computer?
— Reply to this email directly, view it on GitHub https://github.com/google/comprehensive-rust/issues/836#issuecomment-1761615094, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBPPKUO6IGTFZKOSUTCVJDX7FFUZANCNFSM6AAAAAAZMZ3TCQ . You are receiving this because you were mentioned.Message ID: @.***>
Hi @thefirans, I can give it a try. How can I get your translated uk.po?
Hi @thefirans, I have tried your uk.po file. I have used the following commands:
MDBOOK_BOOK__LANGUAGE=uk mdbook build -d book/uk
MDBOOK_BOOK__LANGUAGE=uk mdbook serve -d book/uk
This will indeed not display many new translations. This is because all of them are marked with fuzzy flag. See: https://github.com/google/mdbook-i18n-helpers/blob/main/i18n-helpers/USAGE.md#using-translations
If you want to see translated text - you should open your uk.po and remove all #, fuzzy lines from it. Once you do this, you will see all translations.
I suggest to commit cloud-translate work, and we'll further focus on correcting all fuzzy translations
Would you mind if I create a PR and commit to the main branch for the cloud-translate work, or is there a specific branch for commits like this? This way, we won't have to translate the uk.po file from scratch.
Sure, why not, let's commit to the main branch
@yaremam I would love to help with the translation, would you mind if I work through https://github.com/google/comprehensive-rust/pull/1425 to fix the translation? Thank you.
@mgeisler we are in a good shape to have Ukrainian translation published (final touches are here https://github.com/google/comprehensive-rust/pull/2176), what is the process to do that? Thank you!
That's great, @reta ! I'll send the PRs to "officially" add the UK translation to the language selector!
