Tracking issue for Chinese translations

[0xPoe]

This is a tracking issue for Chinese translations. If you have any questions/problems with Chinese translations, feel free to leave a comment here!

[phil-opp]

There was a comment from @Guo-weijian about the x86_64 dependency in https://github.com/phil-opp/blog_os/issues/934#issuecomment-786434482:

please update crate x86_64 from 0.11 to 0.12, the old version didn't work now

[0xPoe]

There was a comment from @Guo-weijian about the x86_64 dependency in #934 (comment):

please update crate x86_64 from 0.11 to 0.12, the old version didn't work now

I'll take a look tomorrow.

[phil-opp]

@hi-rustin Thanks a lot!

[plko345]

@hi-rustin 第二章节 "A Minimal Rust Kernel" 从 "Building our Kernel" 开始有较大差异, 原文去掉了 "cargo xbuild" 作为构建工具, 同时添加了 "The build-std Option", "Memory-Related Intrinsics" 小节的内容作为替代.

[Salpadding]

对于最新的 bootimage 需要在 Cargo.toml 中添加如下配置指定编译命令, 否则会默认使用 cargo build 编译，导致编译报错

[package.metadata.bootimage]
build-command = ["xbuild"]

[bjorn3]

@Salpadding cargo xbuild has been subsumed by the build-std functionality of cargo. This is why newer bootimage versions default to it. It looks like the chinese translation hasn't yet been updated for this. If you add

[unstable]
build-std = ["core", "compiler_builtins"]

to .cargo/config.toml you can use cargo build. See https://os.phil-opp.com/minimal-rust-kernel/#the-build-std-option in the english version.

@hi-rustin would you mind updating the translation for https://github.com/phil-opp/blog_os/pull/836?

[0xPoe]

@hi-rustin would you mind updating the translation for #836?

I'll give it a try this weekend.

[xtexx]

use cargo build instead of cargo xbuild.

See #1125

[HuSharp]

Thx for ur tracking! And I think it can be combined with this repository

[phil-opp]

There is a new Chinese translation for post-09 ("Paging Implementation") in https://github.com/phil-opp/blog_os/pull/1189. We're still looking for someone that can give it a quick review.

[zhc7]

In https://os.phil-opp.com/paging-introduction/#paging-on-x86-64, paragraph 3, "We see that each table index consists of 9 bits, ...", "bits" is translated into "字节", whereas it actually means "bytes". Correct translation should be "比特", "位", or "字"。

[zhc7]

missing spaces when using *

[zhc7]

should be "字节"(byte), not "比特"(bit)

[acyanbird]

https://os.phil-opp.com/zh-CN/testing/ 内核测试章节 最后一块代码引用

// in tests/should_panic.rs
use blog_os::{QemuExitCode, exit_qemu, serial_println};

应该为 use blog_os::{QemuExitCode, exit_qemu, serial_println, serial_print};

[phil-opp]

@acyanbird @zhc7 Thanks a lot for reporting these errors! Please create pull requests to fix these things, as it's difficult for me to work with Chinese text.

You can find the source files for each post in https://github.com/phil-opp/blog_os/tree/main/blog/content/edition-2/posts . For editing, you can either fork the repo or just use GitHub's web editor. Thanks!

[acyanbird]

@phil-opp Sure! I've created PR to fix all errors raised by me and @zhc7. #1262

[acyanbird]

https://github.com/phil-opp/blog_os/pull/1274 Hi I open a new PR to fix some format errors

[acyanbird]

And sorry to ask here, but can I visit edition 3 through web page, or it only available from github repo branch edition-3? It's too hard to read from there qwq

[phil-opp]

And sorry to ask here, but can I visit edition 3 through web page, or it only available from github repo branch edition-3? It's too hard to read from there qwq

Only through the repo right now, sorry. I want to finish the screen output post before publishing. I try my best to get to it soon!

[acyanbird]

And sorry to ask here, but can I visit edition 3 through web page, or it only available from github repo branch edition-3? It's too hard to read from there qwq

Only through the repo right now, sorry. I want to finish the screen output post before publishing. I try my best to get to it soon!

OK thank you so much! And by the way, I may have time to translate some posts. I could directly raise the PR right?

[phil-opp]

Yes, thanks a lot!