Q&A: Multilingual support improvements #135
Replies: 10 comments 16 replies
-
|
Hi @thibaudcolas, It's great to see you here. We met at DjangoCon Africa in Arusha!😅 I have been going through the discussions you linked above and then digging into the source code of wagtail and wagtail-localize directly for some time. The locale-after-creation problem stands out to me as the most critical piece. I got some insights when I read the code, but two questions remain that I would appreciate a response to:
Understanding and getting more insights on this would help me massively in scoping the proposal that I am putting together. Thank you for your time! |
Beta Was this translation helpful? Give feedback.
-
|
Hey @thibaudcolas , Following your recommendation on my participant file, I’m very excited about the Multilingual support improvements project. My production Wagtail EIP at Pou Chen Group included full i18n with English + Traditional Chinese (URL prefixes, LocaleMiddleware, custom menu translation tags). I also documented everything with detailed SOPs and architecture guides. I’ve already started contributing to bakerydemo (PR #653 for block-based menus) and am now setting up wagtail-localize locally to analyze and begin small PRs here too. I am fully available for the entire GSoC period and my internship is flexible and ends this June. (35–40h/week confirmed). Would you have any early guidance on which pain points from #13693 to prioritise for a strong proposal, or should I start with a small improvement in wagtail-localize first? Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @thibaudcolas, Shreyas here. I’m excited about the “Multilingual support improvements” idea for GSoC 2026 and have been (https://wagtail.org/blog/our-projects-for-gsoc-2026/?utm_source=openai)) A few questions to help me focus:
Thanks & regards, |
Beta Was this translation helpful? Give feedback.
-
|
Hello @thibaudcolas , I have some questions regarding this project
Thank you for your time, please others can also discuss about this with me!! |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
-
|
Hi everyone, thanks again for all the insights in this thread! I’ve pulled together a shortlist of multilingual workflow
Could you let me know which of these would deliver the most value for the upcoming release cycle, and whether there’s |
Beta Was this translation helpful? Give feedback.
-
|
Hi @thibaudcolas The current fine-grained segment approach is what makes translation memory effective, since small changes in source content can still reuse previous translations. At the same time, this same approach seems to be behind two of the biggest pain points in #13693: machine translation losing sentence-level context (word order, agreement), and translators seeing inline elements break apart or move around in the editor. The improvements I’m exploring, like grouping segments by paragraph and using richer editor components, are mostly about giving translators more context. But that starts to look a lot like coarser segmentation, which could reduce how reusable translation memory is. I’d love to understand the project’s direction here: is the expectation to keep segment-level storage and improve only how segments are presented, or is there openness to revisiting the segmentation strategy itself? That distinction affects how I scope both the translator experience work and the translation memory UI. |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I reviewed PR #882 in wagtail-localize, which adds The PR (by @Andreew4x4) builds on @freddiemixell's original PR #752, cherry-picking the core implementation and adding comprehensive tests and documentation. The feature allows developers to control which sub-fields of a A few things I noticed during the review:
My full review is here: wagtail/wagtail-localize#882 (review) This was a great way to get deeper into the wagtail-localize codebase ahead of my GSoC proposal for the Multilingual Support Improvements project. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you everyone for taking part in this thread! We’ve received 24 proposals for this project. We’re going to hold off from responding to further questions, just so we can focus on reviewing the proposals. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
👋 use this discussion thread for any and all questions relating to our project idea: Multilingual support improvements.
Check out our recommended (optional) tasks for contributors, including tasks geared towards getting up to speed for this project idea.
Beta Was this translation helpful? Give feedback.
All reactions