Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chinese (Simplified) translation #324

Closed
hilbert-yaa opened this issue Feb 2, 2023 · 67 comments
Closed

Chinese (Simplified) translation #324

hilbert-yaa opened this issue Feb 2, 2023 · 67 comments
Assignees

Comments

@hilbert-yaa
Copy link

hilbert-yaa commented Feb 2, 2023

Hi Martin @mgeisler ! I've had a conversation with you via email about this translation a week ago. I'm working on this issue rn.

Edit by @mgeisler: See #324 (comment) below for instructions.

@mgeisler
Copy link
Collaborator

mgeisler commented Feb 2, 2023

For reference: https://github.com/KaiserY/trpl-zh-cn.

@hilbert-yaa
Copy link
Author

Sounds great. I'm currently taking this project as a reference.

@kiwiwarmnfuzzy
Copy link

Hey @mgeisler: I saw that there's a machine-translated version by running the i18n script, could you run the script for the zh_CN locale for us?

(I think Hilbert had a similar script but we noticed some off-by-one errors..., so just wanted to see if these errors are specific to zh_CN locale.)

Thanks!

@mgeisler
Copy link
Collaborator

mgeisler commented Feb 9, 2023

Hi @kiwiwarmnfuzzy, the script it here: #291. I asked the other translators, and they tell me that they haven't seen the same off-by-one errors.

Here is the output from a fresh run of that script: zh_CN.zip.

@hilbert-yaa
Copy link
Author

Hi @kiwiwarmnfuzzy, the script it here: #291. I asked the other translators, and they tell me that they haven't seen the same off-by-one errors.

Here is the output from a fresh run of that script: zh_CN.zip.

Oh no worries I wasn't using your script. And thanks this output looks good - we can start from here.

@mgeisler
Copy link
Collaborator

mgeisler commented Feb 9, 2023

Oh no worries I wasn't using your script.

Great to hear that!

@mgeisler
Copy link
Collaborator

Hi there, just a small note: please rename the file to zh-CN.po so that the translation will eventually appear under .../zh-CN/. The _ to - change should give us the right kind of language tag and this is the style we used for the Brazilian Portuguese translation in #381.

@mgeisler
Copy link
Collaborator

From reading https://developers.google.com/search/docs/specialty/international/localized-versions, I'm thinking we should name the Simplified Chinese translation zh-Hans like @taotieren does in #436.

@hilbert-yaa
Copy link
Author

From reading https://developers.google.com/search/docs/specialty/international/localized-versions, I'm thinking we should name the Simplified Chinese translation zh-Hans like @taotieren does in #436.

Got it. I've been occupied by my COVID and ISCA rebuttal lately. Will work on this from the coming week.

@mgeisler
Copy link
Collaborator

Got it. I've been occupied by my COVID and ISCA rebuttal lately.

Ugh, sorry to hear that! I had COVID myself last year and it was not fun at all... Good luck with the conference! 🙂

@hilbert-yaa
Copy link
Author

Got it. I've been occupied by my COVID and ISCA rebuttal lately.

Ugh, sorry to hear that! I had COVID myself last year and it was not fun at all... Good luck with the conference! slightly_smiling_face

Thanks for the kind words :)

@est7
Copy link

est7 commented Apr 26, 2023

@hilbert-yaa any update? can't wait to see it

@xusiwei
Copy link
Contributor

xusiwei commented May 24, 2023

I think called Chinese Simplified is better.
Can you post the WIP repo URL in this issuse?

@kiwiwarmnfuzzy
Copy link

@xusiwei Thanks for reaching out!

I think called Chinese Simplified is better.

Could you explain a little why 'Chinese Simplified' is better? Is the difference between Mandarin v.s. Simplified about speaking v.s. writing? (I'm not very experienced in internationalization and various terminologies, so I'm mildly curious.)

Can you post the WIP repo URL in this issuse?

#325 is the latest PR that I'm aware of. This Google Doc has all the pointers.

@mgeisler
Copy link
Collaborator

I think called Chinese Simplified is better.

Hi @xusiwei, I tried looking this up and from what I can understand, you're right: we should call the translation "Chinese (Simplified)" since we're referring to the script. Google Translate uses "Chinese (Simplified)" so that's why I'm suggesting this variation.

@mgeisler mgeisler changed the title Chinese Mandarin translation Chinese (Simplified) translation May 24, 2023
@mgeisler
Copy link
Collaborator

mgeisler commented May 24, 2023

To everybody here (@est7, @xusiwei, @kiwiwarmnfuzzy, ...): could someone generate a nearly-empty po/zh-Hans.po file to get the translation kicked off? We've done that recently for #653 and #652 😄

It would be awesome to get this started so that people can have an easier time contributing follow-up translations.

@markx
Copy link
Contributor

markx commented May 24, 2023

Hi @mgeisler, just saw your email and I think this is very exciting! I was going to go through the course anyway so I'd love to help with at least some parts of this translation.

@mgeisler
Copy link
Collaborator

Hi @mgeisler, just saw your email and I think this is very exciting! I was going to go through the course anyway so I'd love to help with at least some parts of this translation.

Hey @markx, that's excellent! Please start by putting up a PR to create the PO file, see our translation instructions for how to do this.

@HangDu1995
Copy link
Contributor

Hi @mgeisler, I saw your email too. I can also help with the translation!

@jzpin
Copy link
Contributor

jzpin commented May 24, 2023

Hi @mgeisler I would like to help. How many people are needed for the Chinese translation? I was wondering how to avoid duplicate work?

@jzpin
Copy link
Contributor

jzpin commented May 24, 2023

To create the po file for Chinese, should we use zh-HANS or zh-CN for simplified Chinese? To give some context, see discussion here for Chinese variants. To me, maybe zh-CN makes more sense here, if we really want to consider the differences of usage at different regions.

@Doris-Ge
Copy link
Contributor

Hi @mgeisler, I'm Doris. I'd like to help! How should I coordinate with other volunteers?

@caott0503
Copy link

Hi @mgeisler, I'm Luke and I saw your email. I'd like to help with the translations! How should I participate in this?

@dav11b
Copy link

dav11b commented May 24, 2023

hey @mgeisler, My name's David and I'm also happy to help!

henrif75 added a commit that referenced this issue Jan 20, 2024
*Stats:*
Before: 1018 translated messages, 368 fuzzy translations, 2074
untranslated messages.
After: 1251 translated messages, 397 fuzzy translations, 1812
untranslated messages.
#324 #1463

---------

Co-authored-by: Emma Li <[email protected]>
henrif75 added a commit that referenced this issue Jan 20, 2024
#324 #1463
*Stats*
Before: 1018 translated messages, 368 fuzzy translations, 2074
untranslated messages.
After: 1250 translated messages, 530 fuzzy translations, 1680
untranslated messages.

You can ignore _fuzzy_ entries in sections outside Day 1, they should be
addressed by other PRs.

---------

Co-authored-by: Emma Li <[email protected]>
henrif75 added a commit that referenced this issue Jan 20, 2024
*Stats:*
Before: 1018 translated messages, 368 fuzzy translations, 2074
untranslated messages.
After: 1436 translated messages, 382 fuzzy translations, 1642
untranslated messages.
#324 #1463

---------

Co-authored-by: Emma Li <[email protected]>
henrif75 added a commit that referenced this issue Jan 21, 2024
*Stats:*
Before: 1018 translated messages, 368 fuzzy translations, 2074
untranslated messages.
After: 1280 translated messages, 383 fuzzy translations, 1797
untranslated messages.
#324 #1463

---------

Co-authored-by: Emma Li <[email protected]>
@AgainstEntropy
Copy link
Collaborator

Hi guys! This is Yihao (Ethan), and I'm exicited to make a meaningful contribution!🔥

@henrif75
Copy link
Collaborator

henrif75 commented Jan 23, 2024

Hi guys! This is Yihao (Ethan), and I'm exicited to make a meaningful contribution!🔥

Hi Ethan, thank you! It's great to have you with our efforts to make the course accessible to Chinese-speakers!
Feel free to check the TRANSLATIONS.md with the instructions on how the localization engine works.
Feel free to send me a PR as well if you want to help with PR reviews by adding yourself to the CODEOWNERS file.
Thanks again!

@AgainstEntropy
Copy link
Collaborator

Hi guys! This is Yihao (Ethan), and I'm exicited to make a meaningful contribution!🔥

Hi Ethan, thank you! It's great to have you with our efforts to make the course accessible to Chinese-speakers! Feel free to check the TRANSLATIONS.md with the instructions on how the localization engine works. Feel free to send me a PR as well if you want to help with PR reviews by adding yourself to the CODEOWNERS file. Thanks again!

Hi Henri. Thanks for your reply. Sure I'm willing to help and I have created a PR #1734

henrif75 added a commit to henrif75/comprehensive-rust that referenced this issue Jan 25, 2024
Updates the `zh-CN.po` (google#324) with the v.2 English strings, without
adding new translations.
It will set the base to merge the professional translations later
(google#1463).

To avoid disruptions on the live zh-CN version, this will be merged into
a new branch (zh-CN-cr2), until all PRs are reviewed.
henrif75 added a commit to henrif75/comprehensive-rust that referenced this issue Jan 25, 2024
*Stats:*
Before: 1018 translated messages, 368 fuzzy translations, 2074
untranslated messages.
After: 1143 translated messages, 383 fuzzy translations, 1934
untranslated messages.
google#324 google#1463

---------

Co-authored-by: Emma Li <[email protected]>
henrif75 added a commit to henrif75/comprehensive-rust that referenced this issue Jan 25, 2024
*Stats:*
Before: 1018 translated messages, 368 fuzzy translations, 2074
untranslated messages.
After: 1132 translated messages, 456 fuzzy translations, 1872
untranslated messages.
google#324 google#1463

---------

Co-authored-by: Emma Li <[email protected]>
henrif75 added a commit to henrif75/comprehensive-rust that referenced this issue Jan 25, 2024
*Stats:*
Before: 1018 translated messages, 368 fuzzy translations, 2074
untranslated messages.
1214 translated messages, 381 fuzzy translations, 1865 untranslated
messages.
google#324 google#1463

---------

Co-authored-by: Emma Li <[email protected]>
henrif75 added a commit to henrif75/comprehensive-rust that referenced this issue Jan 25, 2024
You can ignore _fuzzy_ entries in sections outside Day 2, they should be
addressed by other PRs.

*Stats*
Before: 1018 translated messages, 368 fuzzy translations, 2074
untranslated messages.
After: 1218 translated messages, 487 fuzzy translations, 1755
untranslated messages.

google#324 google#1463

---------

Co-authored-by: Emma Li <[email protected]>
henrif75 added a commit to henrif75/comprehensive-rust that referenced this issue Jan 25, 2024
*Stats:*
Before: 1018 translated messages, 368 fuzzy translations, 2074
untranslated messages.
After: 1251 translated messages, 397 fuzzy translations, 1812
untranslated messages.
google#324 google#1463

---------

Co-authored-by: Emma Li <[email protected]>
henrif75 added a commit to henrif75/comprehensive-rust that referenced this issue Jan 25, 2024
google#324 google#1463
*Stats*
Before: 1018 translated messages, 368 fuzzy translations, 2074
untranslated messages.
After: 1250 translated messages, 530 fuzzy translations, 1680
untranslated messages.

You can ignore _fuzzy_ entries in sections outside Day 1, they should be
addressed by other PRs.

---------

Co-authored-by: Emma Li <[email protected]>
henrif75 added a commit to henrif75/comprehensive-rust that referenced this issue Jan 25, 2024
*Stats:*
Before: 1018 translated messages, 368 fuzzy translations, 2074
untranslated messages.
After: 1436 translated messages, 382 fuzzy translations, 1642
untranslated messages.
google#324 google#1463

---------

Co-authored-by: Emma Li <[email protected]>
henrif75 added a commit to henrif75/comprehensive-rust that referenced this issue Jan 25, 2024
*Stats:*
Before: 1018 translated messages, 368 fuzzy translations, 2074
untranslated messages.
After: 1280 translated messages, 383 fuzzy translations, 1797
untranslated messages.
google#324 google#1463

---------

Co-authored-by: Emma Li <[email protected]>
henrif75 added a commit that referenced this issue Jan 27, 2024
Publishes the new translations for CR2 (originally from zh-CN-cr2) #1463
which were previously reviewed.
It also removes line numbers (#1753)
#324

You can skim this PR with the [GitHub CLI](https://cli.github.com/):

```
gh pr diff 1764 | bat -l patch
```
@henrif75
Copy link
Collaborator

The v.2 content is now published. There's still several fuzzy translations that will need to be reviewed and corrected or confirmed.

henrif75 added a commit that referenced this issue Feb 8, 2024
#324

---------

Co-authored-by: Yihao Wang <[email protected]>
Co-authored-by: Henri F. <[email protected]>
mani-chand pushed a commit to mani-chand/comprehensive-rust that referenced this issue Feb 16, 2024
google#324

---------

Co-authored-by: Yihao Wang <[email protected]>
Co-authored-by: Henri F. <[email protected]>
henrif75 pushed a commit that referenced this issue Feb 16, 2024
The po file has been refreshed. Translation range: L1173-L2241.

#324

---------

Co-authored-by: Yihao Wang <[email protected]>
mani-chand pushed a commit to mani-chand/comprehensive-rust that referenced this issue Feb 29, 2024
The po file has been refreshed. Translation range: L1173-L2241.

google#324

---------

Co-authored-by: Yihao Wang <[email protected]>
JasperPluijmers added a commit to nedap/comprehensive-rust that referenced this issue Mar 8, 2024
* Fix typo in googletest.md (google#1804)

The word `strings` is repeated unnecessarily

* Update try.md - syntax error (google#1807)

Add second `:`

* Use existing function as an example for automatic dereferncing (google#1799)

* Fix Chromium link in README.md (google#1812)

Fixes google#1806.

* Make content of variable "name" an actual name (google#1816)

In the example, somebody who is trying to understand this code has to
follow a lot of moving pieces: prefix, name, make_greeter, and then also
learn the new move concept at the same time.

It'd be better if the content were to actually match the name of the
variables. "Hi" is a good prefix, but "there" is not a name, so let's go
with an actual name.

* Added break-continue section. (google#1793)

This is a contribution of a break-continue section for Comprehensive
Rust.


![image](https://github.com/google/comprehensive-rust/assets/65899331/e68bf439-bcbd-43c9-88bd-f66470a5956f)

![image](https://github.com/google/comprehensive-rust/assets/65899331/1644a460-8373-4878-b6b9-0ce498e8c95d)

---------

Co-authored-by: Dustin J. Mitchell <[email protected]>

* Change String representation to actual (google#1817)

Tested with rust 2015, 2018, 2021 and 2024, on amd64 musl, amd64 glibc
and aarch64 musl, all of them represent Strings with (ptr, capacity,
len).

This is an internal implementation detail, that shouldn't be exposed
anyway, so it's no big deal, but in the speaker notes, we provide a
debugging tool for demonstration purposes, so at least that should have
a correct output.

* zh-CN: index & preparation translation (google#1800)

The po file has been refreshed. Translation range: L1173-L2241.

google#324

---------

Co-authored-by: Yihao Wang <[email protected]>

* Added blocks and scopes section (google#1822)

* Translation correction on Update es.po (google#1780)

I added a tranlation correction on the line 1287, I change "tres"
instead "cuatro", because "cuatro" is the meaningful of four in Spanish.

---------

Co-authored-by: Henri F <[email protected]>

* da: refresh translation for January 2024 (google#1742)

This is a clean refresh, requires only a syntactical review.

You can skim this PR with the [GitHub CLI](https://cli.github.com/):

```
gh pr diff 1742 | bat -l patch
```

* fa: refresh translation for January 2024 (google#1751)

This is a clean refresh, requires only a syntaxtical review.

You can skim this PR with the [GitHub CLI](https://cli.github.com/):

```
gh pr diff 1751 | bat -l patch
```

* Translation correction on Update es.po (google#1781)

I added a tranlation correction on the line 1287, I change "tres"
instead "cuatro", because "cuatro" is the meaningful of four in Spanish.

---------

Co-authored-by: Henri F <[email protected]>

* cargo: bump the patch group with 1 update (google#1828)

Bumps the patch group with 1 update:
[clap](https://github.com/clap-rs/clap).

Updates `clap` from 4.5.0 to 4.5.1

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* uk: Day 3: morning (google#1826)

Day 3: morning

Signed-off-by: Andriy Redko <[email protected]>

* Suggest --locked for cargo installs (google#1792)

This is already used in the GitHub actions, and avoids issues like those
in google#1791.

Fixes google#1791.

* Fix style in glossary.md (google#1825)

`id` of `h1` title in the translated version will be changed to the
translated text.
Fixed `id` configured here will not take effect in the translated
version.

Correct style: https://google.github.io/comprehensive-rust/glossary.html
Wrong style (zh-CN): https://google.github.io/comprehensive-rust/zh-CN/glossary.html

* Add heading attribute to glossary.md (google#1829)

Add heading attributes[1] to avoid ID changes in translation.

[1]: https://rust-lang.github.io/mdBook/format/markdown.html#heading-attributes

Related: google#1825

---------

Co-authored-by: Martin Geisler <[email protected]>

* Rendered PDF improvements (google#1805)

Updates `mdbook-pandoc` to
[0.5.0](https://github.com/max-heller/mdbook-pandoc/releases/tag/v0.5.0)
to use some new features:
- Table wrapping (closes google#1709)
  
The wrapping logic mirror's
[Pandoc's](https://pandoc.org/MANUAL.html#extension-pipe_tables) (i.e.,
compare the relative widths of the `---` columns to determine column
widths) so tables in the source may need tweaking to get the proportions
right
- Replace broken links in PDF with corresponding links to
https://google.github.io/comprehensive-rust/

* Make the "break with label" example more illustrative (google#1830)

In the old version, using "break 'outer;" and using "break;" (without
the label) produce the same output.

This version fixes that to make the example more illustrative.

---------

Co-authored-by: Martin Geisler <[email protected]>

* fr: Updating the first few pages (up to 1.1). (google#1778)

* Update translations.md with new Korean contributor (google#1823)

Co-authored-by: Martin Geisler <[email protected]>

* Reformulate speaker notes regarding Box (google#1819)

The first change is to reformulate the English in a way, that
emphasizes, that this is not a decision of the compiler, but the
impossibility of computing an infinite value (e.g. changed the language
from "not compute" to "would not be able to compute").

The second change is to fix the error message, of course the error
message from the compiler is "recursive withOUT indirection", as
"recursive with indirection" is actually what we want.

* Put a header on schedule comments (google#1814)

This will add a little more context. See the current result in
google#1813.

* Add missing editable attribute to exercise (google#1827)

I was reading the docs and I stumbled upon this.

I'm unsure about when exercises should be solved directly on the site
and when they should be copied and pasted into a playground. But since
the previous chapter's exercise is solvable in the site [(fibonacci
sequence)](https://github.com/google/comprehensive-rust/blob/0cb7f496b542d76468fa950718f57f4037abc8fa/src/types-and-values/exercise.md?plain=1#L15),

I figured this one might be missing the attribute. Anyway amazing work
on the docs!

* Change hardcoded vector update to a for loop (google#1833)

iterating over the vector instead of hardcoding each item

---------

Co-authored-by: Martin Geisler <[email protected]>

* Expand Traits, add associated types (google#1815)

This breaks the "Traits" slide into three smaller sub-slides. It also
addresses part of google#1511 by explicitly addressing associated types.

---------

Co-authored-by: Martin Geisler <[email protected]>

* Update exercise to add also the tests, in a TDD style (google#1832)

Having the tests only in the result brings less value, so the
participants can do it following TDD practices

* Update user-defined-types/exercise.md (google#1835)

Allow us to edit so we can complete the exercise :)

* Move hello world example to second section (google#1838)

The current location for the hello world example is awkward since the
two surrounding pages are both talking about Rust from a high level
without talking about syntax at all. I think starting the second section
(types and values) with the hello world example would help the first
section flow more smoothly.

* Add translation comment to glossary (google#1831)

With google/mdbook-i18n-helpers#107 merged, we
can begin adding comments for the translators to our Markdown files.

* Tweak timings of exercises to better reflect teaching times (google#1839)

A few of the early exercises had much larger estimates than were
actually necessary for the super simple early exercises. I've gone
through and reviewed the time estimates for exercises and tweaked the
estimates based on how much time students have actually needed in my
classes so far.

* Flesh out `for` loop example (google#1841)

* Add example of iterating over a collection.
* Update speaker notes to call out the use of iterators.

I think it's useful to call out that `for` loops primarily are used to
iterate over a collection of objects, even though we haven't yet talked
about any concrete collection types at this point. I think using the
array literal syntax is simple enough to understand that it should be
quick to explain when we get to this slide.

* pt-BR: Merge CR v.2 pt-BR translation back into main (google#1846)

This PR merges the pt-BR v.2 translation back to main.
Also, it refreshes the .po file format removing the line numbers.
This requires just a syntactical review, as the partial PRs into this
branch were reviewed already.

You can skim this PR with the [GitHub CLI](https://cli.github.com/):

gh pr diff 1846 | bat -l patch

google#317 google#1463

---------

Co-authored-by: João Victor Mendes <[email protected]>
Co-authored-by: azevedoalice <[email protected]>

* Fix definition of Rust Fundamentals in glossary.md (google#1844)

Small nitpick: Days 1 to **4** are Rust Fundamentals

* Fix typo in cargo.md (google#1847)

* Remove tangential text from `if` slide (google#1840)

* Update cargo.md to fix typos (google#1848)

* cargo: bump the patch group with 6 updates (google#1850)

Bumps the patch group with 6 updates

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* cargo: bump the patch group in /src/bare-metal/aps/examples with 1 update (google#1851)

Bumps the patch group in /src/bare-metal/aps/examples with 1 update:
[cc](https://github.com/rust-lang/cc-rs).

Updates `cc` from 1.0.83 to 1.0.88

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* cargo: bump the patch group in /src/exercises/bare-metal/rtc with 1 update (google#1852)

Bumps the patch group in /src/exercises/bare-metal/rtc with 1 update:
[cc](https://github.com/rust-lang/cc-rs).

Updates `cc` from 1.0.83 to 1.0.88

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* uk: Day 3: afternoon (google#1849)

uk: Day 3: afternoon

Signed-off-by: Andriy Redko <[email protected]>

* Link to PDF version of course from first page (google#1836)

Re
google#1805 (review)

---------

Co-authored-by: Martin Geisler <[email protected]>

* Skip translation of large bare-metal code blocks (google#1853)

This was done a bit inconsistently before. We now skip all of these
large blocks which are meant to be used as-is by the students.

This removes 700 lines from the PO files. I found this during the review
of google#1651.

* Sort `mdbook` redirects (google#1761)

There were a few comments, but I think it’s better to make it all
uniform and avoid these comments. The comment was about the v2 rewrite,
but this is now done and so the comment is less useful.

I also normalized the quotes to double-quotes instead of single-quotes.
The latter is a literal string in TOML, but we don’t actually have any
special characters to escape here.

* Rework introduction of pattern matching (google#1843)

* Update course-schedule PR comments in-place (google#1856)

Instead of always adding a new comment, just update the existing comment
if one exists.

This fixes google#1834.

* cargo: bump the patch group in /src/bare-metal/aps/examples with 1 update (google#1871)

Bumps the patch group in /src/bare-metal/aps/examples with 1 update:
[log](https://github.com/rust-lang/log).

Updates `log` from 0.4.20 to 0.4.21

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump crate-ci/typos from 1.18.2 to 1.19.0 (google#1872)

Bumps [crate-ci/typos](https://github.com/crate-ci/typos) from 1.18.2 to
1.19.0.

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* cargo: bump the patch group with 4 updates (google#1873)

Bumps the patch group with 4 updates:
[log](https://github.com/rust-lang/log),
[tempfile](https://github.com/Stebalien/tempfile),
[cxx](https://github.com/dtolnay/cxx) and
[cxx-build](https://github.com/dtolnay/cxx).

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* cargo: bump the patch group in /src/exercises/bare-metal/rtc with 1 update (google#1874)

Bumps the patch group in /src/exercises/bare-metal/rtc with 1 update:
[log](https://github.com/rust-lang/log).

Updates `log` from 0.4.20 to 0.4.21

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* cargo: bump the minor group with 2 updates (google#1870)

Bumps the minor group with 2 updates:
[scraper](https://github.com/causal-agent/scraper) and
[tokio-websockets](https://github.com/Gelbpunkt/tokio-websockets).

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* URGENT: Fix course schedule watcher github action (google#1867)

@djmitche Currently all PRs are marked as schedule change PRs.

This is my try to propose a fix for this, but please review diligently,
I'm no github actions expert, and I don't have an environment to test.

* Small formatting fix (google#1866)

This is a typo, that actually @mgeisler stopped in my previous PR, I was
just not around to fix it fast enough to make it to the previous merge.
Thanks for the catch!

* Move Mockall and GoogleTest slides to Android section (google#1533)

After google#1528 and google#1532, we now have actual slides which showcase the
crates in action. So we can reclaim a few minutes by removing the slide
which mentions Mockall and GoogleTest slide.

The slide mentioned [proptest](https://docs.rs/proptest) and
[rstest](https://docs.rs/rstest) as well. While I'm sure the libraries
are useful, we don't have them imported into AOSP and I've never
personally used them. We should therefore not advertise them yet at this
point since they won't be useful to Android engineers.

Of course we can mention things that are not in AOSP (or in Chromium),
but I think we should do it in the speaker notes at most.

* Always install and run `mdbook-pandoc` (google#1713)

Before, we only installed and ran `mdbook-pandoc` when publishing the
course — which means that a PR change could accidentally break the
publish workflow. We now test that it works on every PR.

From a discussion in google#1704.

* Add a dev theme to help with slide aspect ratio (google#1842)

Added a dev theme to help with slide aspect ratio while updating content
or for reviewing PRs.

Fixes google#1796.

---------

Co-authored-by: Dustin J. Mitchell <[email protected]>
Co-authored-by: Martin Geisler <[email protected]>

* cargo: bump mio from 0.8.10 to 0.8.11 (google#1877)

Bumps [mio](https://github.com/tokio-rs/mio) from 0.8.10 to 0.8.11.

* Fix some typos (google#1864)

Signed-off-by: geekvest <[email protected]>

* es: Merge CR v.2 Spanish translation back into main (google#1879)

This PR merges the Spanish (es) v.2 translation back to main.
This requires just a syntactical review, as the partial PRs into this
branch were reviewed already.

You can skim this PR with the [GitHub CLI](https://cli.github.com/):

gh pr diff 1879 | bat -l patch

google#1463 google#284

---------

Co-authored-by: David Martínez Martí <[email protected]>

* tr: cr2 update changes (google#1865)

updated for cr2 and added some translations

Part of google#500

* Divided Array and tuples (google#1859)

google#1824 PR Changes

* Make diagram consistent with code (google#1855)

* Retire @duyguisler as a Turkish reviewer (google#1880)

Thanks for the work so far, feel free to come back if you have more
time!

* Tweak solution to iter exercise (google#1884)

Because `.zip()` is limited to the shorter length, the `.take()` call
here is unnecessary. When explaining this solution I don't want to have
to explain a call to a method that, used as it is, does nothing.

* concurrency: Add detailed teaching notes for welcome and threads slides (google#1885)

These follow the flow of what I actually teach, which spends a
significant amount of time on the latter slide. I think it's worthwhile
to have a real flow documented in the teaching notes, both to make sure
nothing gets forgotten and to structure the experience of teaching.

* Do not show trait vtables as located in the heap in memory diagram (google#1882)

This diagram is misleading and I often explain that the character data
of string literals resides in the executable's static data, with vtables
working the same.

* concurrency: Update async trait slide (google#1883)

Clarify that the basics are stable, but dyn support is still missing.
This slide was outdated and didn't explain the current state of stable
correctly.

* set fallback fonts for PDF rendering (google#1728)

Once a new version of Pandoc is released that includes
jgm/pandoc#9204 and
jgm/pandoc#9353 (both merged), this will fix the
emoji and symbol rendering issues in google#1708.

It doesn't seem to be possible to set fallback fonts with
`luatexja-fontspec` (used to configure CJK fonts), which results in some
missing symbols in the translations but at least renders the emoji
properly.

Closes google#1708

* Fix typo in associated-types.md (google#1887)

A minor nitpick, but as someone new to the language I did spend a bit
more time than I'd like to admit trying to understand the meaning of
`allow` before realizing this is likely a typo. Maybe I still don't
understand, and in that case I'd appreciate a correction!

* Refreshed Bengali Translations and Added New Translations to Bengali (google#1876)

This PR aims to do the following:
1. Refresh the Bengali Translations
2. Add new translations in line with google#653 to complete up to 10%.
3. Corrections to existing translations.

Edit: Recent commits bump up the % completed to 12.

---------

Co-authored-by: abhik-bits <[email protected]>
Co-authored-by: Mir Wasi Ahmed <[email protected]>

---------

Signed-off-by: dependabot[bot] <[email protected]>
Signed-off-by: Andriy Redko <[email protected]>
Signed-off-by: geekvest <[email protected]>
Co-authored-by: IP1llar <[email protected]>
Co-authored-by: Gergely Risko <[email protected]>
Co-authored-by: Dustin J. Mitchell <[email protected]>
Co-authored-by: Manichand Kondapaka <[email protected]>
Co-authored-by: Dustin J. Mitchell <[email protected]>
Co-authored-by: mobyw <[email protected]>
Co-authored-by: Yihao Wang <[email protected]>
Co-authored-by: Diego Romero <[email protected]>
Co-authored-by: Henri F <[email protected]>
Co-authored-by: Martin Geisler <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Andriy Redko <[email protected]>
Co-authored-by: Martin Geisler <[email protected]>
Co-authored-by: Max Heller <[email protected]>
Co-authored-by: Marja Hölttä <[email protected]>
Co-authored-by: AdrienBaudemont <[email protected]>
Co-authored-by: titong0 <[email protected]>
Co-authored-by: Jean Carlo Vicelli <[email protected]>
Co-authored-by: Michael Graf <[email protected]>
Co-authored-by: Nicole L <[email protected]>
Co-authored-by: João Victor Mendes <[email protected]>
Co-authored-by: azevedoalice <[email protected]>
Co-authored-by: Adrian Taylor <[email protected]>
Co-authored-by: geekvest <[email protected]>
Co-authored-by: David Martínez Martí <[email protected]>
Co-authored-by: Enes Aydın <[email protected]>
Co-authored-by: Yuri Astrakhan <[email protected]>
Co-authored-by: Frances Wingerter <[email protected]>
Co-authored-by: Aaron M <[email protected]>
Co-authored-by: Abhik Banerjee <[email protected]>
Co-authored-by: abhik-bits <[email protected]>
Co-authored-by: Mir Wasi Ahmed <[email protected]>
@henrif75
Copy link
Collaborator

Closing this issue since we're done with the core translation work.

mgeisler pushed a commit that referenced this issue Aug 28, 2024
The po file has been refreshed. Translation range: L22164-L22764.

#324

Translations of terms refer to the Chinese version of the TRPL and
https://github.com/rust-lang-cn/english-chinese-glossary-of-rust/blob/master/rust-glossary.md

Note: Since italics are not used in Chinese to indicate quotation or
emphasisin Chinese, English italics have been translated into Chinese
bold, and the original English text of terms is marked in full-width
parentheses.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests