comprehensive-rust
comprehensive-rust copied to clipboard
google
Japanese translation
The Rust Book has been translated into Japanese. Let us see if we can reuse some of their terminology.
Hey @momotaro1105, @keiichiw, @CoinEZ-JPN and other people interested in the Japanese translation.
Just a small note: I've created spreadsheets to help organize some of the other translations, see #684 for an example. That might be useful for you too.
Hi, I've read your post and would love to contribute to this as a native Japanese speaker :) Do we already have the spreadsheet for the JA project? Or should I make one?
https://github.com/google/comprehensive-rust/issues/652#issuecomment-1562812496
hello, just checking - the next PR should come directly from my branch post fetch origin, correct? and still to this #652?
@CoinEZ-JPN If the branch on your forked repository is based on this repository's main branch and your commit message includes #652, that should be fine.
Note that it would be easier if one pull request translates only one chapter. That's said it'd be nice if you have branches such as japanese-translate-ch-3 or japanese-translate-ch-4 for each chapter.
Hi, I've read your misc-jp post and would love to contribute to this as a native Japanese speaker :) Do we already have the spreadsheet for the JA project? Or should I make one?
Hey @kantasv, amazing, welcome onboard! Thank you very much for offering to help :smile:
Please coordinate with @CoinEZ-JPN and @keiichiw about using a spreadsheet. It might not be necessary if it's just you and @CoinEZ-JPN who are actively working on the translation.
@keiichiw hi thanks instructions Is it alright if I commit the intro (ch.1 and 2) in a single PR? The rest I will separate into its own branch.
@kantasv apol missed, not aware of what misc-jp is, but would be nice to work together - what do you need me to do?
@keiichiw pls ignore first comment, just created PR for just ch.0, the welcome page from japanese-translation-ch-0
@mgeisler @CoinEZ-JPN @kantasv I just created a spreadsheet to gather the information on who is now working on which sections. Please take a look at it and put your name to the files you want to work on.
@kantasv Thank you so much for offering to help! We've started translation. Please take a look at po/ja.po and start translating whatever section you want!
Note that misc-jp is something Google internal. So, please avoid mentioning it in public places like here.
Thanks @mgeisler @keiichiw and @CoinEZ-JPN for the updates and guidance. The spreadsheet helps me to work in pararell with @CoinEZ-JPN . I'll send a PR in the near future :)
@kantasv - looking forward to working together FYI
- I'm simply working top to bottom atm
- done up to and incl. Ch.5 (PRs have NOT been created for all yet / spreadsheet is updated now)
Hi, @CoinEZ-JPN thanks for the headsup! Okay, then on my end I'll start from chapter corresponding to src/async.md with the top-to-bottom basis :)
Hi, seems like a lot of original English content have been updated so far, making ja.po file outdated. I try to figure out how to update translation according to TRANSLATIONS.md. Or if some of use are already familiar with updating po files, would be great if you do so :)
Example of update in the original content:
po/ja.po
https://github.com/google/comprehensive-rust/blob/c23da457ae62815477454290dde86d5b598c28df/po/ja.po#L13842
src/concurrency/channels/bounded.md
https://github.com/google/comprehensive-rust/blob/c23da457ae62815477454290dde86d5b598c28df/src/concurrency/channels/bounded.md?plain=1#L3
Thanks @kantasv! As you can see in your #1054, every paragraph that has changes is now marked fuzzy in the translation. This is the signal to you and the fellow Japanese translators that the translation is out of date and it should be double-checked by a human:
- If the paragraph changed because of a typo fix, then it's easy: just remove the
fuzzymarker from the translation. - If the paragraph changed because of a rewrite, then the translation will need to be reworked before you remove the
fuzzymarker.
Great. Thank you for pro tips. Okay, I'll resolve those fuzzy ones. Since we have many paragraph to translate, I've set up cloud-translate on my local computer, and seems it works to some extent. (Great workload reduction along with human correction!)
Hi! I'm interested in contributing to this! Please let me know if anyone comes up with a starting point that does not overlap ongoing work.
Hi @HidenoriKobayashi, glad to have you! Thanks to @keiichiw and @mgeisler , we have this spreadsheet that tracks who is working on which chapters, and this might be helpful :)
This isn't itself a JA translation problem, but today when I try to hotreload for local environment, I had to use the following commands to display translations properly on mdbook locally: rustup update and cargo install mdbook-i18n-helpers.
Just leaving a tip for other translators who have been using old configurations!
Thanks @kantasv! I assume the workflow here is that you mark the "state" to "in-progress" when you start working. Let me know if otherwise.
Hi, @CoinEZ-JPN would you mind if I cover the "Basic Syntax" chapter? --- I saw your ticks in the spreadsheet. I might be able to offload your work :) But of course, this is a very interesting chapter, and if you're still working on it, please go for it!
How do folks deal with a case where some phrases in ja.po are not appropriately split. For example, src/bare-metal/microcontrollers/probe-rs.md:6 is split into two chunks, but I suppose it should really be one.
How do folks deal with a case where some phrases in ja.po are not appropriately split. For example, src/bare-metal/microcontrollers/probe-rs.md:6 is split into two chunks, but I suppose it should really be one.
IIUC, it's being split because they're part of a bulleted list. With that said, I think you can consider both entry (probe-rs.md:6) as one, and enter the translation in either entry.
IIUC, it's being split because they're part of a bulleted list. With that said, I think you can consider both entry (probe-rs.md:6) as one, and enter the translation in either entry.
Thank you for the suggestion! I think your advice perfectly solves my issue.
I wondered if that was due to the html tag (abbr) and that if there was any way to deal with it in ja.po (i.e. without affecting other language translations).
Hi, @CoinEZ-JPN would you mind if I cover the "Basic Syntax" chapter? --- I saw your ticks in the spreadsheet. I might be able to offload your work :) But of course, this is a very interesting chapter, and if you're still working on it, please go for it!
@kantasv sorry for coming back so late - have been needing to re-prioritize quite aggressively. Yes, of course, but since I do have a draft, perhaps I can share them with you separately to at least try and save a few minutes of your day?
@CoinEZ-JPN Okay, I understand your situation. Since you already have some drafts, you can keep the chapter as yours for now :) I can work on other untranslated chapters!
I need to get the po file updated, but that might cause a conflict to somebody's working version. Please let me know if you want to get something done before that. I'm in no hurry. I plan to do the update this Friday (JST).
I need to get the po file updated, but that might cause a conflict to somebody's working version.
Just a small note: people will be able to merge in their work using msgmerge by hand:
msgmerge --update their-ja.po your-ja.po
That should use the messages found in your-ja.po as the source of truth, and it will clean up any unnecessary messages merged in from their-ja.po.
Hi @HidenoriKobayashi -san, I'm okay with refreshing the po file :) Thank you!
Hello, as a native Japanese speaker, I'm eager to contribute to this project. I've already put my name on the spreadsheet. If it's alright, I would like to start with the translation in the src/control-flow/ directory.
