1155 proposition de

[Stolzenhain]

• create a i18n file structure
• propose an exemplary translation

---

📚 Documentation preview 📚: https://writethedocs-www--1849.org.readthedocs.build/en/1849/

[silopolis]

Hi,

So this is to manage translations without sphinx-intl nor gettext, by "direct" page translation ?

[ericholscher]

Yea, I'm curious about a bit more information here. Can you explain how we'd build and maintain this? I appreciate the translation!

[Stolzenhain]

Yea, I'm curious about a bit more information here. Can you explain how we'd build and maintain this? I appreciate the translation!

Hello! yes, this places a single German translation in a parallel i18n folder structure, since that was a good structural idea on the issue.

The current issue state proposes a sphinx-intl setup before continuing translation.

My original motivation was to keep translations on the Write the Docs platform since infos on these methodologies pop up elsewhere all the time with no means of reference.

[silopolis]

From my LinuxCNC docs Fr/En resynchronization experience, doing it this way is a ticket for a horror story!
This project deserves and needs a proper translation pipeline.

[Stolzenhain]

resynchronization

@silopolis Sorry, I may have misunderstood the whole thing – as summarized here we wouldn't need resynchronisation or a POT helper if a separate language path + config for the content folder would suffice for now?