Martin Geisler

> @mgeisler, i'm sorry for the delay, it took me some time to test the PR, but first of all, thank you for your work. No worries at all, thanks...

> Having to manually modify book.js isnt ideal, but with this PR, atleast it gives determined users the ability to actually do it successfully Okay, thanks, that makes sense to...

> So at least in my expectation, a _chapter-by-chapter_ approach fits better here: i could imagine writing something like `chapter1..md` and `chapter1..md`and just having a simple language switch in my...

> No, i am not on Windows, but i added additional line breaks after the sentences for better styling (my test text was a poem), this could be the reason....

Hi @trdthg Thanks so much for testing this out! > #1306 needs the translated book to have its own SUMMARY.md. So do I have to translate and copy it manually?...

> If I understand correctly this adds better support for translator focused tooling to my original code, is that accurate? Yes, that is precisely the idea. The new commands in...

Hi all, I'll close this PR in favor of https://github.com/google/comprehensive-rust/pull/130. It's the same code there, but it's refactored to not require any changes of mdbook. Instead, I use a renderer...

Just in case someone finds this much later: the tooling has been released as a set of mdbook plugins: https://github.com/google/mdbook-i18n-helpers.

Hi all, the latest version of [mdbook-i18n-helpers](https://github.com/google/mdbook-i18n-helpers) significantly improves on how the text is extracted by removing unnecessary Markdown syntax. Please try it out if you're still interested in translating...

> I think it'll be useful for users who install `mdBook` using `cargo`. And this will let them know that a new version is available and it's time to update....