Hi, ja translation team (#652 ). Here's an MR for the chapter "Shared
States." Could you review the translations? any feedback would be
appreciated. Thank you 😄
cc: @keiichiw , @chikoski , @HidenoriKobayashi , @ternbusty
(Retrieved translaftion draft #1636 Chapter 60 draft, after recent
`ja.po` file refresh #1676 )
Hi, ja-translators, #652 ! I've refreshed `ja.po` file as of today, Jan
8th 2024.
I used the following procedures. Could you review the diff? Thanks 😊
```
MDBOOK_OUTPUT='{"xgettext": {"pot-file": "messages.pot"}}' \
mdbook build -d po
```
```
msgmerge --update po/ja.po po/messages.pot
```
Before we would run `mdbook test` using the current Markdown sources.
This is subtly wrong: we publish the course using back-dated sources,
so we should therefore also run the tests using the same sources (this
ensures that the code snippets actually work).
After this commit, all translatable content lives in exactly two
directories:
- `src/`
- `third_party/`
We need to restore both directories when testing and when publishing.
This ensures consistency in the Markdown text and in the included
source code.
A new `.github/workflows/build.sh` script takes care of preparing the
two directories according to the date in the PO file (if any).
To ensure we can restore all of `third_party/` to an old commit, the
non-changing `third_party/mdbook/book.js` file has been moved to
`theme/book.js`. The file is generated by `mdbook init --theme`,
making it suitable for modification by the user (us). Symlinks have
been added to `third_party/mdbook/` to indicate that the files
ultimately came from upstream.
Konnichiwa, JP translation folks #652. Here's a MR for **Traits**
chapter. I'm open to suggestions and feedback :) Could you take a look
at it? Thank you!
Hello, JA translation team!
(https://github.com/google/comprehensive-rust/issues/652)
As part of #1460, I normalized ja.po using mdbook-i18n-normalize 0.3.0.
Steps taken: `mdbook-i18n-normalize`.
I'm open to any feedback or suggestions. Thank you in advance!
Hello, JA translation team! (#652) I've just included some translations
for the "control-flow" section (chapter 8). I'm open to any feedback or
suggestions. Thank you in advance!
Refresh the po file for Japanese translation. Part of google#652.
Steps taken:
1. MDBOOK_OUTPUT='{"xgettext": {"pot-file": "messages.pot"}}' \
mdbook build -d po
1. msgmerge --update po/ja.po po/messages.pot
This updates each PO file to the date when it was last touched:
for po_file in po/*.po; do
POT_DATE=$(git log -1 --date=short --format=%ad $po_file)
sed -i -e 's/"POT-Creation-Date:.*"/"POT-Creation-Date:
'$POT_DATE'\\n"/' $po_file
done
The dates will be updated with `msgmerge` in the future via
https://github.com/google/mdbook-i18n-helpers/pull/87.
The dates here can be adjusted by hand if needed — the starting point
here only serves as a rough anchor to let us freeze the translations
from further updates. So if you know that you ran `msgmerge` most
recently on a given date, please update the file to that date in a later
PR.
Hi, JA project folks (#652), here's a MR for the chapter "Control Flow".
When you have some time, could you review the diff? Any feedback or
suggestions are greatly appreciated. Thank you in advance.
Hi, JA translation folks (#652), here's a MR for the chapter "Send and
Sync". This chapter is particularly interesting and contains very
rust-specific concepts which seems unfamiliar to me. Any feedback and
suggestions are welcome :)
Before, po/ja.po had these statistics:
351 translated messages, 32 fuzzy translations, 1398 untranslated
messages.
Afterwards, the statistics for po/ja.po is:
472 translated messages, 46 fuzzy translations, 1949 untranslated
messages.
The number of translated messages changed from 20% to 19%.
With this change, it becomes important to use the latest version of
mdbook-i18n-helpers when viewing the translation locally. To update to
the latest version, run
cargo install mdbook-i18n-helpers
You will now be able to serve the translation locally.
Part of #330.
* ja: Ch5.0 #652
・not confident about the translation "access to low-level hardware"
* ja: Ch.5.1 #652
* ja: Ch.5.2 #652
・"integer overflow is defined" -> 「整数オーバーフローの挙動が定義されている」 not confident here
* ja: Ch.5.3 #652
・a tad nit-picky, but believe the "The reasoning behind this..." should be on a line of its own, adding a "\n" between any of the three bullet points can fix this, BUT it will add a line between them. I personally prefer adding the "\n", but left as is
* ja: Ch.5 #652
fixes suggested by @keiichiw
* ja: Ch.4 #652
・"C/C++/Java tradition" -> 「C/C++/Java系統」: could not think of anything better
・"# Small Example" left untranslated
* ja: Ch.4 #652
fixes suggested by @keiichiw
