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 #661

Open
ghost opened this issue May 1, 2017 · 66 comments
Open

Spanish translation #661

ghost opened this issue May 1, 2017 · 66 comments
Labels
blocked upstream Blocked on a change that needs to happen in a different repo first Enhancement Translations
Milestone

Comments

@ghost
Copy link

ghost commented May 1, 2017

Hi guys and girls!

I'd like to help translating the second version of the book into spanish. I'll start working on the frozen chapters, it's that ok?

Thanks :)

@ghost ghost changed the title Spanish transaltion Spanish translation May 1, 2017
@carols10cents
Copy link
Member

Yes! That's great! Please send us a link to your translation (or a PR to the translations appendix) whenever you get it started so that people can find it! ❤️

@carols10cents carols10cents added Translations blocked upstream Blocked on a change that needs to happen in a different repo first Enhancement labels May 2, 2017
@ghost
Copy link
Author

ghost commented May 2, 2017

Thanks! I'm going to be working on this fork https://github.com/z1mvader/book

Should I rename it to something like rust-book-es?

@carols10cents
Copy link
Member

I have no opinion on what the repo is named, it's totally up to you. Sorry this has taken me so long, but I've added a link to your repo in the translations appendix! https://github.com/rust-lang/book/blob/master/second-edition/src/appendix-06-translation.md

@goyox86
Copy link

goyox86 commented Jun 13, 2017

@z1mvader Are you still working on this? @sebasmagri and I are interested and were thinking on opening the issue for the Spanish translation but I found this one :). We should join efforts! I did translated the first version and it's a lot of work ;)

@ghost
Copy link
Author

ghost commented Jun 13, 2017

yeah I've been a little bit busy but yeah. I can add you as collaborators if you want!

@thecodix
Copy link

thecodix commented Jul 6, 2017

Hello, is this work in progress @z1mvader? I imagine there is a lot to be done and I would like to give a hand as well

@ghost
Copy link
Author

ghost commented Jul 6, 2017

Sure i'll add you :)

@gilbertginsberg
Copy link

@z1mvader: Thanks for getting the Spanish translation going. Would you mind adding me as a collaborator to https://github.com/z1mvader/book as well?

@aplanas
Copy link

aplanas commented Jul 9, 2017

@z1mvader I want to help here too. Is there a way to organize the work? I do not see any es branch or any clear commit for es. Is there any table to see who is translating what, to avoid duplication?

Also thanks to taking initiative : ))

@thecodix
Copy link

thecodix commented Jul 9, 2017

I have created a project in same @z1mvader book, to quickly check who's in charge of chapters

Ideally all chapters could be reviewed by someone else. And ideally start picking a frozen one to avoid doing much rework :)

https://github.com/z1mvader/book/projects/1

@aplanas
Copy link

aplanas commented Jul 11, 2017

@thecodix very nice! Can you add me to the project? If not, can you create a card to reflect that I will take care of chapter 4?

@thecodix
Copy link

thecodix commented Jul 11, 2017

I think only @z1mvader can add you as I'm only collaborator and not owner. Anyway I made a card putting you as working on chapter 4. I saw you forked yhe project, I think you can safely edit directly on @z1mvader one since no one is touching that chapter

@goyox86
Copy link

goyox86 commented Jul 12, 2017

One of the key things we have to setup in order to be able to properly follow the mainstream EN version of the book is the infrastructure and tooling we are gonna use. When I translated the first version to Spanish I realised that after doing the initial translation following small updates was not the most agile and lean process on my side.

@aplanas
Copy link

aplanas commented Jul 12, 2017

@goyox86 You are right, also thanks for your work translating the first edition of the book. As a side note, we need to agree how to translate other terms like 'ownership', 'memory safety' etc. For now I am following your decisions for the first edition, but I am not sure if they can't be improved.

Going back to your point, I was thinking to move ES into a different branch and in each commit add in the commit message the hash for the HEAD that I used to translate, so when EN changes, I can use diff to see the changes on the text

@thecodix
Copy link

That's why it's interesting to start with the frozen ones. We should be able to switch to new frozen ones over time. Still, what is your opinion on tooling/infrastructure?

@goyox86
Copy link

goyox86 commented Jul 12, 2017

@aplanas As per agreeing in terms like 'ownership' we might open an issue as I'm not completely happy with my choices 😄 . I was thinking on opening and issue per chapter as well so we have a clear list of whats needs to be done and contributors will find it easy. For the infrastructure @thecodix I would have to check what's available now. We might want to open an issue to track everything there regarding tools et all.

@thecodix
Copy link

thecodix commented Jul 12, 2017

I'm also concerned about Spanish differences between countries, I already moved some 'retornar' into 'devolver' or 'fallas' to 'errores' but I wouldn't like to be a tyrant imposing my country rules

What's your take on this people?

@goyox86
Copy link

goyox86 commented Jul 12, 2017

@thecodix Why we don't create an issue on https://github.com/z1mvader/book for agreeing on translation of key words and discuss there. Otherwise we will put to much noise here. What do you think people?

@thecodix
Copy link

Still no ownership on @z1mvader book so can't create new issues

@thecodix
Copy link

thecodix commented Jul 12, 2017

I forked repository from rust-lang/book so the content is now up to date, since @z1mvader hasn't been touched for months. Anyone of you @goyox86 @aplanas @gilbertginsberg can create issues or touch the project or do whatever, we can discuss as well best options for translation on some words and stuff

https://github.com/thecodix/book

@fagossa
Copy link

fagossa commented Nov 27, 2017

Hello people,
do you still need help on this?

@thecodix
Copy link

Yes, there's been not much movement for a long time, will be interesting to catch up

@aplanas
Copy link

aplanas commented Nov 27, 2017

Sure. I am still here, even if I did not advance too much in the work. More help is very welcome!

@fagossa
Copy link

fagossa commented Nov 27, 2017

Hello,

I would like to know in which repo you have been working on because z1mvader/book seems to be down.

I also found that the appendix points to the same non existing repository. I imagine it must be updated too.

@ConnorDarghaoui
Copy link

@silvestrevivo
Copy link

Hi @carols10cents I was trying to follow all the issues related with this. I don't know why this is not going further and what problems or issues are finding devs to translate this to Spanish. Anyhow, I am available with another Rust dev from Spain to make this possible as soon as possible.

I would appreciate if you can give me some guidance about how to proceed to make this successfully.

I am wondering if @ConnorDarghaoui is going to continue the job or instead me and the other dev we have to open a new PR or fork and start the job again.

Thanks!!!

@carols10cents
Copy link
Member

Hi @silvestrevivo, I'm not really sure what to tell you, I don't know any status other than what you can find in the various repos and by contacting the various people. Translate whatever isn't translated and let me know if I should change any links to translations!

@silvestrevivo
Copy link

@carols10cents thank so much for answering me. Principally my concern is how to proceed to make the translation. I don't see any language selector on the Book, and I was wondering if the Book is already translated to another languages. Thanks!

@carols10cents
Copy link
Member

hi @silvestrevivo, there isn't a great way to integrate translations into the main book at this time-- see rust-lang/mdBook#5. Right now, each translation manages their own repo, and the translation appendix links to each: https://github.com/rust-lang/book/blob/main/src/appendix-06-translation.md

@silvestrevivo
Copy link

@carols10cents but there is an oficial link for each translation? I mean, if we fork the repo and open a PR with the Spanish translation, automatically a new URL in the current website is created for that? I am not so sure how the switch between translations on the official website currently, since I don't see any toggle to solve or manage this. Thanks!

@carols10cents
Copy link
Member

No, there's no official translation for any language. Don't send a PR to this repo with the translation-- make your own repo and manage your own PRs, etc, and send this repo a PR to the translations appendix with a link to your repo. I'm fine replacing old links if the translations aren't as complete or up to date as yours, or just linking to multiple repos to give people alternatives. There is no toggle.

@silvestrevivo
Copy link

Thanks for the explanation @carols10cents A question, would be possible to publish the result in a web to have is online instead in a repo where devs need to generate it? Or that might be a conflict about rights? Thanks!

@carols10cents
Copy link
Member

Nope, it's MIT licensed, feel free to publish the result wherever you'd like!

@ConnorDarghaoui
Copy link

ConnorDarghaoui commented Jan 21, 2022

@carols10cents Hey doing the translation I have stumbled upon something, when you explain that the "&" operator is "Borrow", what do you mean? Could you explain me?. I think it's like pointers in C. In Spanish there is no similar word for "Borrow".

@carols10cents
Copy link
Member

@ConnorDarghaoui it's sort of like pointers in C, except that a & reference is guaranteed to always be valid so they're not called pointers in Rust to indicate that they're different.

Is there a word for when someone else owns a book, and they let you read it for a while, then you give it back? In English I would say I borrowed that book from the other person, and the meaning is similar in Rust.

@ConnorDarghaoui
Copy link

@ConnorDarghaoui it's sort of like pointers in C, except that a & reference is guaranteed to always be valid so they're not called pointers in Rust to indicate that they're different.

Is there a word for when someone else owns a book, and they let you read it for a while, then you give it back? In English I would say I borrowed that book from the other person, and the meaning is similar in Rust.

@carols10cents, Oh I get it, there's a word for that in Spanish. Thank you. In Spanish it would be "prestar", "Te voy a prestar este libro".

Interesting how rust works.

@pepoviola
Copy link

Hi all, there is an in progress translation to contribute? or there is a completed translation to share?
Thx!

@lorena1974
Copy link

Hello, @ConnorDarghaoui are you translate to Spanish version? it is completed? thanks

@lorena1974
Copy link

where can I find the last version translated into spanish? thanks

@ConnorDarghaoui
Copy link

ConnorDarghaoui commented Mar 17, 2022

The translation is not yet complete. @lorena1974.

@ConnorDarghaoui
Copy link

Hi all, there is an in progress translation to contribute? or there is a completed translation to share? Thx!

I have been translucent https://github.com/ConnorDarghaoui/Rust_bookEs

@categulario
Copy link

categulario commented Oct 31, 2022

A summary for newcomers

Projects, past and present

Maintained

Abandoned

Discussion

  • We need to agree on some terms to use that are not specific to one country or another. Perhaps to have a glossary would be useful.
  • Basic CI infrastructure would help a lot so that there's material that people can see, not just a repository.
  • At this point it is not clear how to contribute. Let's make it clear somehow (for instance by focusing on one repository).
  • seems like a good idea to focus on the second edition and probably drop from the repository any additional noise.
  • we should think about diverging from the original work. English and Spanish are different languages and keeping a close relationship between these two books might be hard and undesirable. Why not starting with a decent translation but diverging when necessary? Let's have a book written in spanish instead of a book translated from english. This includes probably not having a fork but a source.
  • Eventually we should think about rustonomicon and other material.

Moving forward

What do ye think? @ConnorDarghaoui what's your status of involvement in this? @silvestrevivo are you still interested? What about the rest?

@mgeisler
Copy link

mgeisler commented Apr 4, 2023

Hi all! I'm maintaining Comprehensive Rust 🦀 and the Spanish translation has just been started: google/comprehensive-rust#284. If someone here wants to help out, then please get in touch on the PR.

We're using https://github.com/google/mdbook-i18n-helpers to synchronize the translation with the source.

@lorena1974
Copy link

lorena1974 commented Apr 5, 2023 via email

@mgeisler
Copy link

mgeisler commented Apr 6, 2023

Thanks for contact me. I will help with translations.

That is great, thank you! Let's talk more on google/comprehensive-rust#284 😄

@Phosphorus-M
Copy link

My friend @CrawKatt is helping me translate the book, but I have a question: will the idea be to merge the translation and the original book eventually?

@categulario
Copy link

categulario commented May 23, 2023

My friend @CrawKatt is helping me translate the book, but I have a question: will the idea be to merge the translation and the original book eventually?

It is unlikely @Phosphorus-M . It will probably just live by itself.

I just realized your translation is already listed above in my comment. Good luck! I might try to contribute

@CrawKatt
Copy link

Hello, I am helping @Phosphorus-M with the translation of the book as an exercise to improve my English. For now I have focused on avoiding translating "programming jargon" Since from my point of view, it makes the coherence in the comprehension of the book a little lost.

For example: "String Slice" in Spanish would be something like "rebanadas de hilo" which does not sound good and makes it even more difficult to understand the odd chapter.

@ivanlynch
Copy link

ivanlynch commented Sep 21, 2023

Hi @Phosphorus-M, can i help with the translation? If yes, can you add me as a collaborator in the project? Thanks 😊!

@Phosphorus-M
Copy link

Hi @ivanlynch, yes, don't worry, we are working actively on the translation and other things.
We started a community to unify many communities about rust that speak Spanish.
I'm going to leave you some links.
https://rustlanges.github.io
https://discord.gg/4ng5HgmaMg

We move the book translation to this repository:
https://github.com/RustLangES/rust-book-es
https://rustlanges.github.io/rust-book-es/

@ThomasMiz
Copy link

Hello! How is the translation for Spanish going? Do you need any more translators?

@Phosphorus-M
Copy link

Hello! How is the translation for Spanish going? Do you need any more translators?

Sorry for the delay, we translated all the book to the Spanish, however you can improve the translation in case of find a misspell or something like that.
Besides we are doing a PR to add the new book as a reference. #3745

Caution

We move the book translation to this repository:
https://github.com/RustLangES/rust-book-es
https://rustlanges.github.io/rust-book-es/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked upstream Blocked on a change that needs to happen in a different repo first Enhancement Translations
Projects
None yet
Development

No branches or pull requests