Jooyung Han
Jooyung Han
Publishing it was mentioned in #434 but no concrete plan yet. With #318 @djmitche is still working on enhancing `i18n-helpers`.
For production-ready translations, I'd translate comments and string literals as well (but not variables) in the code snippets. For this project, I put more focus on slide text and speaker...
While working on the Korean translation i found that keeping MD stuff(ie bullets) was helpful because it gave me freedom to do whatever fits better in the target language like...
IMO, the problem of working with PO file directly is that we need to handle the stack of two encodings: PO file's C-style string literals (with escaping) over MarkDown text....
I thought only fixing in the Korean translation 😃
Todo: * s/블록/블럭 per @jiyongp 's suggestion in https://github.com/google/comprehensive-rust/pull/455/files#r1117272813
> * s/블록/블럭 per @jiyongp 's suggestion in https://github.com/google/comprehensive-rust/pull/455/files#r1117272813 https://www.korean.go.kr/news/index.jsp?control=page&part=view&idx=10192&preview=null says 블록 is right.
https://github.com/jooyunghan/comprehensive-rust/commit/8a7331b8ae7098cf065d6d17993d99b41d623c27 is my WIP for this. Which depends on [another WIP changes in mdbook.](https://github.com/rust-lang/mdBook/pull/2029)