Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Translation System Proposal #209

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Conversation

speco29
Copy link

@speco29 speco29 commented Feb 23, 2025

Made a proposal for the projeect DISCOVER-Cookbook to plan the translation of the cookbook.

Copy link
Member

@aterrel aterrel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a fine rough draft but we need to figure out our strategy here. I'm not a fan of just piping the content through google translate. Chrome has a the ability to just translate any website and I don't know that adds a lot of value.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please move to another PR. We are still in the process of deciding how to include more content in the repo.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rename to 001-Translations.md

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure!

Translation Project for Discover-Cookbook

## Abstract
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. The project involves generating translations for the discover-cookbook, integrating language selection switches, updating translations as content changes, and engaging translators to contribute.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the comment about culinary enthusiast? Seems out of place.

Also need to captialize the acronym, DISCOVER Cookbook.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My apologies, it's a typo, I was writing compassionate.
I'll keep that in mind.

**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).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, is there a better way than just running the content through an AI translation tool? There is a lot of nuance to this guide and we need to have readers who will catch that. I was thinking more of working with translation communities that could provide the translation and feedback, e.g. https://translatewiki.net/

We could also incorporate our own service like: https://pootle.translatehouse.org/

But if we are just going to be piping to Goolge Translate, I don't see much value over the people doing that themselves.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For some more context on why AI translations are not sufficient, see for example this blog post I wrote when we were starting on the translation effort for scientific python websites: https://blog.scientific-python.org/scientific-python/translations/

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, is there a better way than just running the content through an AI translation tool? There is a lot of nuance to this guide and we need to have readers who will catch that. I was thinking more of working with translation communities that could provide the translation and feedback, e.g. https://translatewiki.net/

We could also incorporate our own service like: https://pootle.translatehouse.org/

But if we are just going to be piping to Goolge Translate, I don't see much value over the people doing that themselves.

Sounds right, I actually didn't knew about the community who could provide translations. It would be better if we use the translation community, as it stands out and people will engage

@aterrel aterrel changed the title Proposal for Gsoc Translation System Proposal Mar 2, 2025
@aterrel
Copy link
Member

aterrel commented Mar 2, 2025

Updated title to be more accurate. @speco29 have you had any more time to update the proposal? Would like to get something accepted that we can iterate on in the discussion.

@speco29
Copy link
Author

speco29 commented Mar 3, 2025

Updated title to be more accurate. @speco29 have you had any more time to update the proposal? Would like to get something accepted that we can iterate on in the discussion.

I have this thought that for switches/toggles for language change, I can simply use HTML, CSS, JavaScript.
I'm thinking of adding these technologies and for translations, I would update the technologies to community that provide translations rather than sticking to AI help.
Would that be alright?

@speco29 speco29 closed this Mar 3, 2025
@speco29 speco29 deleted the prop-docs branch March 3, 2025 17:34
@speco29 speco29 restored the prop-docs branch March 3, 2025 17:40
@speco29 speco29 reopened this Mar 3, 2025
@aterrel
Copy link
Member

aterrel commented Mar 11, 2025

The issue with just adding HTML/CSS/JS is that it will need to be integrated with the jupyter book system. While doing something custom is probably easier, it would be harder to maintain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants