Translation: We need to create guidelines around how we translate words to other languages/ spanish

[lwasser]

We have this document but this doesn't overview how particular words are chosen in the translation -- for instance the "wheel" in python packaging. Or do we use "tu" vs "vos"

This relates to #330

[yardasol]

Some translation items we discussed during the sprints today:

• "landing page" -> "página de entrada"
• "on the fly" -> "instantánea"

If there are any others that I forgot @RobPasMue @ncclementi please let me know!

[RobPasMue]

Thanks for listing the translations @yardasol! I have the feeling "landing site" might be better translated to "página de inicio" but we could open up the floor for discussion. =)

[flpm]

Hello everyone! Thanks for helping with this effort!

While I like the idea to have a 'memory' list, where we keep track of the choice of translation for key concepts or technical terms in English, some of the stylistic choices are more delicate.

One point we need to keep in mind though is that Spanish is a language spoken all over the world by people from many different cultures and this is expressed in their choice of vocabulary and phrasing.

I like the approach of the CONTRIBUTING guide (link is in Spanish) for the the Spanish translation of the Python docs. They accept and embrace this diversity, they only enforce that each section be consistent, so if you are modifying an existing section, you adopt the style that is already there. If you start a new one, you can pick.

There are pros and cons with both approaches. I personally lean towards accepting the diversity, but this sounds like a good question to pose to the PyOpenSci community at large and gather thoughts.

[kierisi]

@all-contributors please add @yardasol for code, review

[allcontributors]

@kierisi

I've put up a pull request to add @yardasol! 🎉

[lwasser]

all - thank you for this discussion. i really like @flpm suggestion about which relates to embracing diversity while also following the important work that core python has already done. that is a precedent that i think makes a lot of sense to follow. I personally had never considered all of the variations associated with spanish until this process began even tho i've noticed language differences among my friends who speak.

so is the take away here that we consider following what core python is already doing? If you are ok with doing that, please react to this post with a thumbs up. many thanks!!

I really appreciate learning from you all!

[tkoyama010]

@all-contributors please add @flpm for translation in e599ad8

[allcontributors]

@tkoyama010

I've put up a pull request to add @flpm! 🎉

[flpm]

I have been thinking more about this, maybe a good start would be to compile a list of key concepts/terms related to Python Packaging and basic open source development workflows.

This list can serve as a base to decide: if (1) we should translate a term or keep it in English and (2) what should be the translated version. Then contributors translating into Spanish could refer to this and we can assure that the translation is consistent across the entire guide.

One option would be to go through the guide and pick key concepts and terms. We can also look for similar lists, I found these ones that could be interesting to go through and select some of the words:

• Python Packaging User Guide - Glossary
• Python Documentation: Glossary and its Spanish version
• Terminos y bigramas section from Memoria de traducción - Documentación de Python en Español
• GitHub Glossary for git related terms

Depending of what the English list looks like, we can even consider turning it into a glossary for the English version later, which could be an appendix to the guide.

[lwasser]

Hi! 👋 it looks like we have consensus around using the approach that core Python takes. This means that we could also adapt language from that guide and cite it in ours to give them credit. So, let's move forward with that as a decision. Should I/we create an issue around embracing diversity in our translations? This is a new effort that we will learn a LOT from ✨ ; we can always modify the guidelines if we encounter future challenges.

The glossary is an excellent idea. We considered this idea (in English) in this issue, #141, opened by @kierisi. I opened a PR to demonstrate setting up a Sphinx glossary here. I closed it only because we didn't have any bandwidth to add terms at the time.

If we want to go this route, I'd suggest using the Python packaging glossary as a starting point, given its relevance to us here. Of course, whatever you all think, I'm open to it. That just seems like a great starting point. We could even see if anyone in our Slack community is interested in helping with the glossary, given that it's a discrete task that folks could chip away at.

@flpm @RobPasMue, please let me know what you think about both items! Then please let me know how I could support moving things forward!! 🚀