Feature: Add Spanish translation

[gruumsh1]

Hello!

I have translated the english.json file to Spanish (español.json) to add Spanish language support to Pluto.

Let me know if any changes are needed.

Try this Pull Request!

Open Julia and type:

julia> import Pkg
julia> Pkg.activate(temp=true)
julia> Pkg.add(url="https://github.com/gruumsh1/Pluto.jl", rev="main")
julia> using Pluto

[gruumsh1]

[fonsp]

Hi @gruumsh1 , thank you for your contribution!

Can you write a bit more about the process?

• Did you localize to Spanish of a specific region (e.g. Equador)? Would the localization look different for other regions?
• Did you use AI tools, and how was the process? Did you review the results, and did you need to make any changes?
• Was there anything difficult to localize to spanish? Any intersting/difficult decisions that you needed to make?
• Do you have experience with other Spanish localizations of IDEs? How are words like "notebook" and "cell" localized there?

[gruumsh1]

"Hi @fonsp , thanks for reviewing my contribution! Here are the answers to your questions:

1. Region and Localization: I am based in Mexico, so the translation leans towards Mexican Spanish, which is widely understood across Latin America. I aimed for a Neutral Spanish tone to make it accessible to most Spanish speakers. While there are some dialect differences (like "ordenador" in Spain vs. "computadora" in LatAm), I tried to use standard technical terminology used in academia and data science here.

2. Process and AI Tools: Yes, I used an LLM (Gemini) to assist with the initial translation of the strings to speed up the process. However, I manually reviewed every string within the context of the application to ensure they made sense. Since I modified the frontend files to test the language support, I was able to verify that the translations fit the UI correctly.

3. Difficulties and Decisions: The main challenge was deciding whether to translate specific technical terms or keep them in English, as many developers are used to the English terminology. I decided to translate terms that have a strong equivalent in Spanish while keeping the meaning clear.

4. Terminology (Notebooks and Cells): Regarding your specific examples:

Notebook: I translated this as "Cuaderno". In the Spanish data science community (especially in academic environments like my university), "Cuaderno" is the standard translation for Jupyter or Pluto notebooks.

Cell: I translated this as "Celda". This is the universal standard in Spanish for spreadsheets and code blocks.

I hope this clarifies the process. Let me know if you would like me to adjust any specific terms!"

[fonsp]

Hi @gruumsh1, that sounds really good, thanks so much! I'm also happy to hear that you were able to base the localization on your experience in the academic environment.

For 1, for some languages we specified the region, currently Dutch and Portuguese, because there is no "canonical" version of this language. Do you think it would be nice to do the same for Spanish? Maybe Español (México) or Español (América Latina)? Then the language code would be es-MX (Mexico) or es-419 (Latin America). It's up to you!

I'm happy that you found a good translation for Notebook and Cell!

One other point:
In French, Italian and German we worked on using gender-neutral language. The hope is to make scientific computing more accessible, to make people feel welcome and included. In #3333 and #3325 we ended up using "new" gender-inclusive language, like "Es-tu sûr·e" instead of "Es-tu sûr"/"Es-tu sûre" in French, or "Entwickler:innen" instead of "Entwickler"/"Entwicklerinnen" in German.

I spoke to some Spanish-speaking friends (from Nicaragua and Spain) and they told me about ending words with e. For example, to say "¿Estás segure de ...?" instead of "¿Estás seguro de ...?". What do you think about this, or do you have other experience with this topic? I'm curious what you think!

Thanks again!

[gruumsh1]

Hi again! Thank you for the thoughtful feedback. *1. Regarding Region (es-419):* I agree that specifying the region helps manage expectations regarding terminology (like "computadora" vs "ordenador"). I suggest using *es-419 (Latin American Spanish)*. This code is the industry standard for our region and fits the terminology I used, covering Mexico and most of South/Central America perfectly. *2. Gender-Neutral Language:* I really appreciate that you are considering inclusivity; it is an important topic. Regarding the use of the *"-e" ending* (e.g., *segure*): In Spanish, this form is currently associated with social activism and informal contexts. In formal academic and technical environments (like universities or official documentation), it is *not yet considered standard grammar* and might be confusing or seen as informal by some users. *My Proposal:* instead of using the morphological change ("-e" or "x"), the standard best practice for inclusive Spanish in professional software is *Neutral Rephrasing (Periphrasis)*. We can restructure sentences to avoid gendered adjectives entirely. - *Example 1:* Instead of *"¿Estás seguro?"* (Are you sure? - Male), we change it to an action verb: *"¿Deseas confirmar?"* (Do you wish to confirm?) or *"¿Confirmar acción?"*. - *Example 2:* Instead of *"Bienvenido"* (Welcome - Male), we use *"Te damos la bienvenida"* (We give you welcome). This approach makes the software *100% inclusive and gender-neutral* while maintaining the *formal and professional tone* expected in a scientific tool. If you agree with this approach, I can do a quick pass over the file to "neutralize" gendered words by rephrasing them! El lun, 1 dic 2025 a la(s) 7:18 a.m., Fons van der Plas ( ***@***.***) escribió:

…

*fonsp* left a comment (fonsp/Pluto.jl#3418) <#3418 (comment)> Hi @gruumsh1 <https://github.com/gruumsh1>, that sounds really good, thanks so much! I'm also happy to hear that you were able to base the localization on your experience in the academic environment. For 1, for some languages we specified the region, currently Dutch and Portuguese, because there is no "canonical" version of this language. Do you think it would be nice to do the same for Spanish? Maybe Español (México) or Español (América Latina)? Then the language code would be es-MX (Mexico) or es-419 (Latin America). It's up to you! I'm happy that you found a good translation for Notebook and Cell! One other point: In French, Italian and German we worked on using gender-neutral language. The hope is to make scientific computing more accessible, to make people feel welcome and included. In #3333 <#3333> and #3325 <#3325> we ended up using "new" gender-inclusive language, like "Es-tu sûr·e" instead of "Es-tu sûr"/"Es-tu sûre" in French, or "Entwickler:innen" instead of "Entwickler"/"Entwicklerinnen" in German. I spoke to some Spanish-speaking friends (from Nicaragua and Spain) and they told me about ending words with e. For example, to say "¿Estás segure de ...?" instead of "¿Estás seguro de ...?". What do you think about this, or do you have other experience with this topic? I'm curious what you think! Thanks again! — Reply to this email directly, view it on GitHub <#3418 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDEWCSVRO44BXDQZAR7VYT37Q53XAVCNFSM6AAAAACMLPDUJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKOJWGUYTENZRGA> . You are receiving this because you were mentioned.Message ID: <fonsp/Pluto .***@***.***>

[pankgeorg]

In French, Italian and German we worked on using gender-neutral language.

and Greek! We're also moving the professional bits on another language; we have Business English; which is a bit satirical but also not. We plan a Formal English. Should we do a Spanish and a formal spanish too? I think equality is higher than formality in our priority list 🤗

[fonsp]

Hey @gruumsh1!

Your last reply felt like it was written by Gemini 😅 I totally understand that it helps when working in another language, but maybe it's better to use Gemini to translate text (English - Spanish and Spanish - English), but not to generate text?

I am genuinely interested what you think about the last questions and what your experience is as a native Spanish speaker.

-fons

[gruumsh1]

Hi Fons! You caught me! 😅 You are right, I used Gemini to help me translate/polish because I am currently learning English and I get nervous about grammar mistakes. I will try to write this directly myself so you get my real thoughts. 1. Region: I still think es-419 (Latin America) is the best tag. It covers Mexico and the rest of the region well. 2. Gender Neutrality: First, please forgive me if my previous message sounded too harsh or strict about this! That was not my intention. To be honest, in my daily life at university (math department here in Mexico), we don't see the "-e" ending (like *segure*) very often yet; it is still mostly used in social contexts rather than technical ones. That is why I suggested rephrasing things. However, I admit I haven't seen how the wider Latin American tech community is handling this recently. If the Pluto community tends to use these inclusive words, I have absolutely no problem including them. I want people to feel welcome, so I trust your guidance on this. Let me know what you prefer! El lun, 1 dic 2025 a la(s) 9:40 a.m., Fons van der Plas ( ***@***.***) escribió:

…

*fonsp* left a comment (fonsp/Pluto.jl#3418) <#3418 (comment)> Hey @gruumsh1 <https://github.com/gruumsh1>! Your last reply felt like it was written by Gemini 😅 I totally understand that it helps when working in another language, but maybe it's better to use Gemini to translate text (English - Spanish and Spanish - English), but not to generate text? I am genuinely interested what you think about the last questions and what your experience is as a native Spanish speaker. -fons — Reply to this email directly, view it on GitHub <#3418 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDEWCX6DJ6UMJLZTR5BQU337ROQHAVCNFSM6AAAAACMLPDUJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKOJXGI3DIMZWGM> . You are receiving this because you were mentioned.Message ID: <fonsp/Pluto .***@***.***>

[fonsp]

No problem at all :)

Okay in that case, let's go with es-419 and "segure" (and the same for similar cases). 🌟 Do you want to update your PR?

[gruumsh1]

of course, I'm working on it El lun, 1 dic 2025 a la(s) 10:38 a.m., Fons van der Plas ( ***@***.***) escribió:

…

*fonsp* left a comment (fonsp/Pluto.jl#3418) <#3418 (comment)> No problem at all :) Okay in that case, let's go with es-419 and "segure" (and the same for similar cases). 🌟 Do you want to update your PR? — Reply to this email directly, view it on GitHub <#3418 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDEWCXFYNQTK7K7QK73ZLT37RVJHAVCNFSM6AAAAACMLPDUJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKOJXGU4TAOBQGY> . You are receiving this because you were mentioned.Message ID: <fonsp/Pluto .***@***.***>

[gruumsh1]

Hi @fonsp , I've sent the PR

[fonsp]

Thank so much!!

[gruumsh1]

If you need me to work on anything else, I'm more than ready for it. El mié, 3 dic 2025 a la(s) 4:33 a.m., Fons van der Plas ( ***@***.***) escribió:

…

*fonsp* left a comment (fonsp/Pluto.jl#3418) <#3418 (comment)> Thank so much!! <https://camo.githubusercontent.com/783bddcfc5f1ef0160b525a10420e5249e72df875365d43dbeb954bf33d3628c/68747470733a2f2f6d65646961312e67697068792e636f6d2f6d656469612f76312e59326c6b505463354d4749334e6a45786257466c4d3255336547353261444e34596d78735a3342686147646964484a756448423561584635616d3173635868755a6e63344d695a6c634431324d563970626e526c636d35686246396e61575a66596e6c666157516d593351395a772f7159794566564a6e305a6c665650454c6f762f67697068792e676966> — Reply to this email directly, view it on GitHub <#3418 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDEWCVXWONGVJCKMRRC2M337235XAVCNFSM6AAAAACMLPDUJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMBWGE3DCNJWGM> . You are receiving this because you were mentioned.Message ID: <fonsp/Pluto .***@***.***>