Japanese translation

[mgeisler]

The Rust Book has been translated into Japanese. Let us see if we can reuse some of their terminology.

[mgeisler]

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.

[kantasv]

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?

#652 (comment)

[CoinEZ-JPN]

hello, just checking - the next PR should come directly from my branch post fetch origin, correct?
and still to this #652?

[keiichiw]

@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.

[mgeisler]

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?

#652 (comment)

Hey @kantasv, amazing, welcome onboard! Thank you very much for offering to help 😄

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.

[CoinEZ-JPN]

@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?

[HidenoriKobayashi]

Hi, @HidenoriKobayashi -san. The Poedit behaviors you mentioned weren't reproducible in my environment:

• My Poedit version: 3.51, Mac OS: Sonoma 14.2.1

• Triangle explamation icons on top of the text lists are visible:

  • Source texts do not always have explamation icons — only some but not all
  • Clicking a line with the icon shows me concrete feedback, such as 翻訳は"."で終える必要があります。

Do you still have the same issue?

Thanks @kantasv for the message! It somehow works as intended now.

[HidenoriKobayashi]

By the way, when the professional translations are merged, what else is left for this issue?

[henrif75]

By the way, when the professional translations are merged, what else is left for this issue?

There will be several translations that will need to be reviewed because they're marked as "fuzzy". Besides that, the original course is constantly updated and improved, and eventually translations need to catch up.

[HidenoriKobayashi]

@henrif75 Regarding the profession translation PRs, are the comments handled by yourself or they go back to the translation team?

I had naively regarded that they will be read by someone who can read Japanese. If that is not the case, maybe I should try to convert all my comments to suggestions that you can apply. Well, that obviously takes some time, but it's doable.

[mgeisler]

By the way, when the professional translations are merged, what else is left for this issue?

There will be several translations that will need to be reviewed because they're marked as "fuzzy". Besides that, the original course is constantly updated and improved, and eventually translations need to catch up.

I agree. I also wonder if we should mark the per-language issues as closed after we publish the first version? I think it could make sense to mark that milestone.

[kantasv]

Hi @mgeisler , could we add @HidenoriKobayashi -san to the repo? We already added Hidenori-san to CODEOWNERS, but now I remember a comment from you:

You need write permission on the repository to review things (we enabled this after we got a few spam reviews).

(#1472 (comment))

[mgeisler]

Yes, certainly! Welcome @HidenoriKobayashi!

[HidenoriKobayashi]

Now that the professional translation PRs went in (thanks @henrif75!), I think we can close this issue to mark that milestone. Although I see many parts that are behind the English main version, I think those should be easier managed if we handle them separately from this one.

What I'd like to do after this is that we create an issue to catch-up with the English main version every quarter or so. Plus, if there's something wrong, we create a specific issue and correct that.

Does anyone have an objection? (If so, please re-open this issue)

[mgeisler]

What I'd like to do after this is that we create an issue to catch-up with the English main version every quarter or so. Plus, if there's something wrong, we create a specific issue and correct that.

That sounds like a great idea, thanks @HidenoriKobayashi!