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

Spanish translation #414

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

Spanish translation #414

wants to merge 22 commits into from

Conversation

ikks
Copy link

@ikks ikks commented Oct 6, 2024

Updated spanish translation

@ikks
Copy link
Author

ikks commented Oct 7, 2024

Community in spanish is aware of this effort and we will take to october the eleventh to review, if we have everything reviewed sooner I will let it know.

Most of the translation was updated and with high quality we will take a closer look to buiding tools to maintain the standards.

@ikks
Copy link
Author

ikks commented Oct 12, 2024

There are no reported issues from Spanish community. It can be merged if you agree.

@ikks ikks changed the title Spanish translation WIP Spanish translation Oct 12, 2024
@Undinath
Copy link

Undinath commented Jan 5, 2025

Hello! I was considering to contribute to Zig by translating the website into Spanish (from Spain) and found this translation. I had a deep look into it and I'm unfortunately not satisfied with it. Just to list a few things:

  • The audience is inconsistent. Sometimes verbs are conjugated as "", sometimes "usted", and sometimes appear in a reflexive or passive form.
  • Parentheses are not used correctly (I see a pattern where they do not respect the space before the opening one).
  • Some sentences are translated in a robotic, way-too-literal way and don't sound natural.
  • There are a few typos here and there.
  • Some parts of the text are not translated at all.

Spanish is a complicated language and what works in LATAM (Latin America) sounds off in Spain. Even language codes are a mess. You chose es-AR and I was expecting rioplatense but found something more neutral, which I like, but makes choosing it misleading. Apparently the "right" (?) code for LATAM Spanish is es-419 and that's awful. Sites like e.g. Apple use "la" for LATAM, which is also incorrect... Language codes aside, I had two questions in mind:

  • @ikks What is that community you are referring to? Maybe that'd be a better forum for me to make proposals and suggest adjustments to the current translation. Filling this PR with Spanish gibberish might not be good form, even if what we want is to have a high quality translation.

  • @kristoff-it How bad would it be to introduce a Language (Country) pattern for translations? I've seen it a lot for Canadian (English/French), or Chinese (Mandarin/Cantonese), while I can't say it's that popular for Spanish [Español (España/Latinoamérica)].

I don't know anyone that actually likes español neutro but in writing it's slightly easier to achieve.

@ikks
Copy link
Author

ikks commented Jan 5, 2025

Hi @Undinath the community in Spanish is here https://t.me/+TuqWR0w6W5o1MDAx .

We need critical eye to improve the translation, maybe through reviews on each file using suggestions batch per file would be a good approach.

If there is a preference to draft a document on translation style, it would be good too.

Feel free to start the path to improve the translation. I guess that having the translation synced with an improved one is a big step forward.

If you see that maybe is better to start a repo where we can contribute is better, that's an option too.

Maybe steping up in the Telegram group raising the issues and proposing and starting an action plan would be a good starting point.

Agree with you that we can do it way better.

@Undinath
Copy link

Undinath commented Jan 7, 2025

I scouted what other programming languages websites do language-wise and to my surprise only a few do translations, which means splitting the Spanish one into two variants makes no sense.

We only have 10 pages to translate so we can invest a little bit more energy into having a great, country-neutral translation, (which is easier said than done!). I'm happy with file-by-file reviews but let's have a small chat on how to proceed. I'll send you a message later tomorrow.

I'm happy to be able to work on this together with you.

@kristoff-it
Copy link
Member

Hi, I'm not sure how the discussion ended, is this PR ready to be merged or does it require more translation work?

From my perspective I wouldn't worry too much about being maximally formally correct with the language. I can't speak for a Spanish audience so I defer to you all in terms of what a Spanish speaker finds appropriate or not, but in general the Zig website doesn't have an overly formal tone except maybe for /news and /zsf where we talk about financial stuff.

If nobody has other changes to suggest I would ask you fix the merge conflicts and then I will merge the PR right away.

Thanks again for your work.

@ikks
Copy link
Author

ikks commented Jan 23, 2025

Hi there @kristoff-it there has been no work to update this PR recently, I synced the book and IntelliJ plugins and resolved the conflicts I found.

I haven't found traction to update the translation further, please feel free to merge as is.

Thank you. Great to include Spanish in the upcoming 0.14 release.

@Undinath
Copy link

Hello. I made a PR to @ikks a few days ago, it's just one file at the time of writing this comment, and will add a new file revision later today. Reviewing takes more time than doing it from scratch and I see no value in having competing translations. Discussing on ikks fork seems like a better place to discuss in Spanish rather than here.

I'd like to ask for some more time, but I find it fair to say that we could have a good text ready before next release.

@ikks
Copy link
Author

ikks commented Jan 23, 2025

@Undinath thank you for the care and improvements, just merged it. I missed that one, sorry about that. Cheers.

Sergi Lluy and others added 2 commits January 24, 2025 02:24
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