Martin Geisler

One way of solving this would be to write a tool which can add the necessary HTML after the book has been rendered. The advantages of this would be -...

> The first thing we should do is add a way to embed a JSON config inside of the page. Then we'll be able to use the data from Javascript...

Oh, another point: the translation infrastructure is now used by a handful different projects, so we should take care to make it as easy as possible for them to use....

> My first thought is that we could move the translation logic to the renderer so we wouldn't need to do this as part of the CI with a different...

Hi @sakex, I was just playing with the new renderer from #80 and it works really well! I tried solving this issue and it's just a few lines of template...

Hi @Demian101! Good question: we don't have a good solution for this right now and so we're also hand-coding the list of languages right now. Eventually, @sakex's work on #70...

The changes for this should ideally be made in polib: https://github.com/BrettDong/polib/issues/8.

What should a GitHub action do? - it should download a pre-compiled `mdbook-gettext` binary so that `mdbook build` can be fast. - when #84 is done, the action should also...

Hey @trooper2013, thanks a lot for looking at this! I would love for you to start simple here: building a fully automatic publishing pipeline is complicated, but making a very...

Hi @carreter, thanks for looking at this! > @mgeisler If I'm understanding correctly, this action should do the following (modeled after [publish.yml](https://github.com/google/comprehensive-rust/blob/main/.github/workflows/publish.yml) from Comprehensive Rust): > > * Install `mdbook`...