I think this repository can support more languages

[Jzow]

have this plan at present?

[Jzow]

#126 I can do some translation for Chinese. At present, many people in China are studying driver develop. It happens that rust language has advantages in this respect. I think it can be translated into Chinese for easy reading

[eldruin]

We would be glad for translations of the book into Chinese and any other language!
mdbook does not have multilingual support yet so I think an easy way to do this for now would be to fork this repository and then translate it. You can then publish it to GitHub pages and we will link it here.
This is what @tomoyuki-nakabayashi has done for the Japanese version of the discovery book
Does that sound reasonable to you?
We can help you if some steps do not work.

[burrbull]

https://crates.io/crates/mdbook-i18n-helpers

[mgeisler]

Hi there, I wrote mdbook-i18n-helpers and we've been using it for some months now for Comprehensive Rust 🦀. I would be happy to help with setting it up for this book.

I see that there are already two hand-written translations available. Getting those converted back to the Gettext PO format will be a non-perfect process. I can try writing a convert tool which takes two Markdown files as input and outputs a PO file. If the translations have kept the Markdown structure intact (same number of paragraphs, same number of list items, ...), it should be possible to convert them back to a PO file.

[eldruin]

Sounds great @mgeisler, thank you. It would be great to draw more people into embedded Rust :)
However, please beware that we generally do not have much time to invest, so the setup would need to be easy to manage.

[mgeisler]

Sounds great @mgeisler, thank you. It would be great to draw more people into embedded Rust :)

Yeah, I would hope so!

However, please beware that we generally do not have much time to invest, so the setup would need to be easy to manage.

Makes sense! In general, the setup I use for the course favors long-term maintainability for some simplicity. The easiest no-setup-needed idea is to clone the repository and do the translations directly inside the English files. However, it's hard to impossible to track changes to the original files that way.

The Gettext approach helps here since it decouples the translation from the source. You extract source text into PO files and translators work on those. When you publish a translation, you read the translation from the PO files. The PO files are small version-controlled databases and there is tooling available which can merge new strings into these databases. This is described in detail in mdbook-i18n-helpers.

[burrbull]

@mgeisler Could you write CI for this repository for pot file update and release translated books?

[mgeisler]

@mgeisler Could you write CI for this repository for pot file update and release translated books?

Yes, I would be happy to do this! It might be a week or two before I get to it.

[mgeisler]

It might be a week or two before I get to it.

I nerd-sniped myself and couldn't help but working on it... please see #356 😄

[Jzow]

Excuse me, I have two questions.

Firstly, I have roughly reviewed the description of @mgeisler The mdbook-i18n-helpers warehouse is designed to help md convert to po, and I don't quite understand what the po here means. What is its purpose?

The second question is, do we need to wait for this plugin to complete before translating, and do we need a manual before translating.

[burrbull]

.po is translation file for https://en.wikipedia.org/wiki/Gettext

Supported by several editors. For example
https://poedit.net/