Tracking: Turing Way

[rowanc1]

We had a wonderful conversation this morning with the TuringWay team on how best to support the TuringWay team in their adoption of JupyterBook v2, which will be using mystmd. There were a lot of exciting possibilities that we talked about in terms of creating an ecosystem of content that the TuringWay could expose (figure, equations, glossaries), and that be included, linked to and cross-referenced by other books, tutorials, and communities in the wider open-science ecosystem. There are also some current deficiencies in MyST MD at the moment, one of the core ones is around internationalization. We got a really good demo from @BatoolMM on how that process is working, and some of the sticking points on how to bring content together to have a unified experience between languages. The localization also must include right-to-left languages, which will require a number of style updates and improvements across the components.

Resources for translations:

• https://turingway-arabic.netlify.app/welcome.html
• https://github.com/TWTranslation/the-turing-way/tree/main/book/translation

Example of Turing Way content deployed in MyST

• https://rowanc1-turingway.curve.space/ (this is deployed using Curvenote)

Some cool things

Updates that need to happen

• Glossary Compatibility with RST Glossaries #618
• Improve the upgrade process 🆙 Upgrade Jupyter Books in myst init #1223 (in progress)
• Internationalization and localization (this is a big task that we need to break down, what is necessary is a lot clearer to me notw after @BatooIMM's demo) Add support for translations / internationalization of page elements #166
• Host multiple languages in a single theme
• PR: fix admonitions with Note --> note (that can be upstreamed right away)
• Way to turn off @username references on a page (e.g. changelogs) or have those fallback to a configured list of IDs and improve, e.g. our GitHub person cards.
• Discuss and demo different ways to build out the infrastructure for the book (and tradeoffs between the different approaches)
• Idea (curious on your take): Add source attribution information to images/figures #1305
• Improved header / footer information

There are probably a number of other things that will come out as we work towards these goals, I encourage members of the TuringWay team to jump in here and let us know how we can support you. Please try the preview above and get a sense of where we are at. One of the cool wins is that the performance of navigating between pages should be improved quite a bit. There are also some abbreviations that will work and increase accessibility etc. for various pages.

I know that my team and @agoose77 do have some time to help with specific things, and some issues are in progress this week, so hopefully when we meet again in a few weeks there will be some progress to show!

@JimMadge @da5nsy @BatoolMM @agoose77 @sgibson91

We have had some previous conversations with the Environmental DataScience Book as well:

https://github.com/alan-turing-institute/environmental-ds-book

@acocac

[da5nsy]

Amazing, thank you so much for getting the ball rolling on this @rowanc1. Really excited to see where we can go with this. And happy to assist where we can!

Linking to the issue over on TTW where we've been tracking our own attempts/progress on enabling multi-language support: the-turing-way/the-turing-way#3255

[agoose77]

@rowanc1 was this meeting recorded in any fashion? I had some pre-conceived ideas around what TTW is doing regarding Crowdin, etc, and I know a bit about the space of tools. My read is that there are many ways to do this, so any guidance on the solution that TTW is converging on would be useful context.

[da5nsy]

Hi @agoose77!
Not recorded I'm afraid, but I'm happy to answer (or redirect) any questions you have.

@BatoolMM is the person to ask about translation, or have a look here at our existing documentation.

And then from an infrastructure perspective this is the latest. In summary, there's currently no obvious out-of-the-box tools that we could use to deploy a multi-language site. We might be able to get something working with RTD, but honestly we would prefer an internal process that didn't rely on an external build service (so that we would be able to host anywhere).
(@JimMadge, @sgibson91, @bsipocz - correct me if I've misunderstood!)

[rowanc1]

@fwkoch just made a change that takes turing way from >1min to build to 17 seconds. 🚀

[JimMadge]

Just leaving some of my thoughts/opinions,

Hosting isn't the same as the build. However, hosting that we have considered/used (Netlify, RTD) do place restrictions on the build.
Ideally, I would prefer that we control the build and just copy the output somewhere to host.

Multilingual support seems surprising difficult given how many languages are commonly used.
A lot of the solutions we have looked at seem to have inherited the idea of translations from software, where you have either

• A set of messages with .po files for each language
• A primary language with translations for each other language

Neither of these feel like they suit us. We don't want to enforce the idea of a primary or default language. We don't really see the task as reproducing the same information in each language.

Maybe we want something more like Wikipedia, where different languages are fairly independent but if there are pages on the same topic in two languages, you can switch between them.

This really isn't my area so I have no idea how difficult or possible that is 😆