Translating Content: Translate the handbook into other languages to reach a broader audience.

[speco29]

The most spoken language in the world by number of native speakers is Mandarin Chinese. With over a billion native speakers, it's the primary language of the majority of people in China, Taiwan, and Singapore.
It can help to reach broader audience to organize different events.
We can add five major languages in our project, let me know your views on that thought ;)

[aterrel]

There are several issues #53 and #54 already talking about translating content. It's a larger project that will take some time to get correct. It requires folks to create a system for:

1. generating the translation
2. adding switches in the book for the selecting languages
3. having a way to update the translations as the book changes in content
4. have a call for translaters to sign up and get tagged.

I recommend writing out a proposal that encompasses all this.

[speco29]

I will look through it on how to write prroposal, can you give me a heads-up like writing proposal and whom to send?
it would be really helpful:)

[aterrel]

I think you can just add your plan here. Basically say what you are doing, your technical approach, and how you we are going to accommodate the list of issues I mentioned.

[aterrel]

Hey @speco29 did you have any updates from your proposal?

[speco29]

Yes, It's my first time writing a proposal, i tried to put everything came up on my mind.
I made a readme file for it.

[speco29]

Here's the proposal

Translation Project for Discover-Cookbook

Introduction
The discover-cookbook is a valuable resource for culinary enthusiasts. Translating the content will make it accessible to a broader audience, fostering a global community of users.

Objectives
-Generate translations for the discover-cookbook.
-Integrate language selection switches within the book.
-Implement a system for updating translations as content changes.
-Engage and tag translators to contribute to the project.

1)Generating Translations
What We Are Doing: Translating the entire content of the discover-cookbook into multiple languages.

Technical Approach:
-Evaluate and select a reliable translation tool or service (e.g., Google Translate, Microsoft Translator).
-Establish a workflow for translating existing content, ensuring consistency and accuracy.

2) Adding Language Switches
What We Are Doing: Integrating switches within the book to allow users to select their preferred language.

Technical Approach:
-Identify and implement language switch mechanisms (e.g., dropdown menus, toggle buttons) within the book's platform.
-Test the functionality across different devices and browsers to ensure seamless language switching.

3) Updating Translations
What We Are Doing: Developing a system to update translations as the book's content changes.

Technical Approach:
-Create a process for tracking changes in the original content.
-Implement a notification system to inform translators of updates.

4) Engaging Translators
What We Are Doing: Calling for translators to sign up and get tagged for their contributions.

Technical Approach:
-Announce a call for translators on relevant platforms (e.g., social media, forums, community websites).
-Develop a tagging system to acknowledge and credit translators for their contributions.
-Provide resources and support for translators to ensure high-quality translations (e.g., guidelines, glossaries, support forums).

Timeline(I'm not sure how much time will it take for these contents, but to get a clear view for each step, I'm adding timeline here)
Phase 1: Initial translation of existing content .

Phase 2: Integration of language switches .

Phase 3: System for updating translations .

Phase 4: Engagement and onboarding of translators.

Resources
-Translation tools/services
-Developers for implementing language switches

Conclusion
Translating the discover-cookbook will significantly enhance its reach and impact, making it accessible to a global audience. By implementing a robust system for translation, language selection, and updates, and engaging a dedicated team of translators, we can ensure the success of this project.

[aterrel]

@speco29 Okay we should just follow the way Matplotlib handles this as a lightweight process in a docs repository. I've added the directory docs/proposals then we can check in your proposal there.

It's easier to comment inline there as this proposal is a bit too vague to be implemented.

@kamila-NF the numfocus gsoc docs say I need 2 mentors, okay to put you down as the back up mentor?

[OriolAbril]

I can take a look, but I am not a maintainer of the cookbook so can't really review much regarding alignment with the project. I am a maintainer of a couple numfocus sponsored projects and whenever possible I also volunteer for numfocus edia related initiatives

[speco29]

DISCOVER Cookbook Gsoc - Diya's proposal.pdf
This the proposal, please give any sort of pointers or feedback.

[OriolAbril]

My main comment would be to add some more details on specific solutions you'd go for, both technical regarding translations themselves, their storage and updates as well as organizational about how the different folks involved (maintainers, translators, contributors...) would interact . This doesn't mean you need to know everything about what you'll do during the project already, during the community bonding and the start of the project you can still discuss all these with the mentors and eventually go for different specific solution instead. But it is a good way to make your case for being a good fit for the project and showing the depth with which you are already familiar with the topic. I'd say this is related to point "Don't be afraid to give us lots of detail about how you would approach the project" in the numfocus gsoc guide and to the techincal details section of the proposal template. Also note that the proposal already checks most of all other points, so it is already in very good shape.

A specific suggestion to improve along these lines is the proof of concept repo you mention in the programming experience section. I have taken a look at the repository, but it is not completely clear what exactly it is I am supposed to take from there. It looks like a proof of concept of the language switcher (point 2 in the description) but the proposal itself says "an example translation page" so I initially wasn't sure what to expect, it could have also been a single translated page. If it is indeed a language switcher, it would be great to add a screenshot of how it looks and behaves, otherwise, us seeing this hands on work relies on cloning the repo and being able to preview its contents without instructions. Similarly, you mention that as a hands on example related to the work, but it is in the programming experience section even though it would mean you do already have specific implementation ideas at least for point 2 in the long description. Therefore, I would explain that in some more detail in the description section.

I also think this lack of specifics bleeds a bit into the timeline section and it can make it a bit harder to follow than it should. As there aren't a lot of details in the description, some sentences have unclear objects or subjects. A couple examples: "Ensuring accuracy and consistency" in week 2 -> not completely sure the accuracy and consistency of what is being checked, "Testing and bug fixing" in weeks 4 and 6, "Running tests" in week 11 -> the repo currently has no testing so it is not clear if this implies you plan to set up some automated testing infrastructure, if this is more about manual testing of the rendered website and user experiments or something else entirely.

I hope it is helpful, I tried to do my best to comment as extensively as possible about the presentation and coherence of the content while trying to avoid adding implementation suggestions of my own both so the proposal can show your ideas which is its main goal and also so I don't inadvertently steer you into a different direction than what the project plans.

[GitHub7667]

Great👍

[speco29]

Thank you so much for these valuable pointers.
I'll modify my proposal and repo accordingly;)

[speco29]

hello @aterrel
Please check this repo once - https://github.com/speco29/Translation
I've created one example file on how can we add switch, let me know if it looks okay.

[AR21SM]

@aterrel can i work on this ??

PS: I’ve been reviewing the requirements and will soon raise a PR with my approach for implementing the translation system.

Looking forward to your feedback!
Best regards,
AR21SM

[AR21SM]

Hi @aterrel, @kamila-NF,

I've reviewed the DISCOVER-Cookbook’s structure and propose the following multilingual support plan:

• Translation Workflow Integration

  • .pot/.po Generation: Use Sphinx’s gettext builder to extract strings from DISCOVER/_tags/*.md and generate translation templates. These will reside in DISCOVER/locales/, aligned with the existing _static/ and _build/ structure. Reference: Sphinx i18n Documentation
  • Crowdin CI Integration: Configure .github/workflows/crowdin.yml to sync translations while ensuring minimal disruption to build-gh-pages.yml.

• Language Switcher Implementation

  • UI Integration: Add a dropdown to _static/Language-switcher.js to handle translations dynamically, similar to the approach used in this PR.

• Community Onboarding & Contribution

  • Documentation: Introduce docs/TRANSLATING.md to mirror CONTRIBUTING.md, guiding new translators.

I’d love to submit a proof-of-concept PR for Hindi (beginning with 01_about.md) to validate this workflow. Looking forward to your thoughts!

Best,
AR21SM

[VemuriHaritha]

Hello @aterrel, @kamila-NF, @speco29, I would like to work with you and your idea and extend it.
Here is my proposal for translation
My idea is to implement AI powered Adaptive Language toggle.
Approach:

• system automatically detects the language of the system and adapt to the language using AI.
• will use browser language detection to set default language.
• implement a NLP based learning model that learns the preferences .
• if the user selects other language than the system language then we can use the browser built-in translation feature for first time and then the learning model learn the language (or) use google translation API.
• if user will switch frequently, then next time an automatic suggestion comes to set the changed language.
• maintain the work flow and consistence
  Tech used:

• JavaScript for language detection and learning.
• Local Storage for storing user preference.
  Looking forward for any thoughts and feedbacks..!

[speco29]

Hello @VemuriHaritha!
I'm just a contributor here, so apparently I can't decide whether your solution is good or not, mentors will tell you shortly;)

[VemuriHaritha]

hi @speco29 actually I know that but as I want to further extend your idea I mentioned you and if you are interested we can collab :)

[Shweta-Rani1]

Hi @aterrel and @kamila-NF,

I am interested in contributing to the Translation System for DISCOVER Cookbook as part of GSoC 2025. I have reviewed the project description and related issues (#175, #53, #54) and have some ideas on how we can implement an efficient and scalable translation workflow.

My Proposed Approach:

1. Hybrid Translation Model – Combining automated translation APIs (Google Translate, DeepL) with community-driven validation for accuracy.
2. Version Control for Translations – Implementing a tracking mechanism that flags content changes and notifies translators.
3. Intuitive Language Switcher – Adding a seamless UI for selecting languages, ensuring responsiveness across platforms.
4. Community Engagement – Launching a translator recognition system to encourage participation.

I would love to discuss:

Any previous challenges the team has faced with translations?

Preferred translation tools/frameworks?

Additional considerations to make the system more efficient?

I am excited to contribute and refine my GSoC proposal based on your insights. Looking forward to your feedback!

Best,
Shweta Rani

[speco29]

Hello @aterrel!
I am absolutely thrilled and honored to have my proposal been selected for Gsoc! This opportunity means a lot to me, and I sincerely want to thank you for your invaluable guidance and support throughout the process. Your insights have been instrumental in shaping my understanding, and I am eager to learn even more under your mentorship.

I’d love to connect and get started right away! Please let me know the best way to proceed—I’m excited to contribute and collaborate. Looking forward to working with you!