Esperanto translation

[psychoslave]

Hi everyone,

I would like to start working on a Esperanto translation of the 2018 edition of the book.
According to this other translation issue a fork is necessary to start a translation. So here is a fork focusing on translating the rust-lang book to Esperanto.

Any advice on priorities, or any further guidance is warmly welcome!

Cheers

[psychoslave]

[proposed Label] Enhancement
[proposed Label] Translations

[psychoslave]

Hi, I would especially apperciate feedback on any best practice regarding the workflow.

That is, should the forking project :

• keep the existing file untouched and put their corresponding translations in a separte directory or directly replace them?
• directly integrate changes in the masterbranch of the fork or create a second mainline where all translations should be isolated? (regradless of what individual translators select as as branching workfow before being integrated in the main branch used for the translation)

Cheers

[psychoslave]

Looking at the code base to translate the 2018 edition, I first inspected the 2018-edition directory, especially the 2018-edtion/src subdirectories. but all files seems to be limited to the following main text:

The 2018 edition of the book is no longer distributed with Rust's documentation.

If you came here via a link or web search, you may want to check out [the current
version of the book](../index.html) instead.

If you have an internet connection, you can [find a copy distributed with
Rust
1.30](https://doc.rust-lang.org/1.30.0/book/2018-edition/ch00-00-introduction.html).

So I wonder what is the text I should translate to put my efforts on the last edition. Is it the root ./src directory that should be translated to achieve that?

Cheers.

[psychoslave]

Ok, so it seems that indeed the 2018 edition have been moved to the repository root. I can now fearlessly start to translate the src directory.

I'm still waiting for guidance regarding best practices in branch and file hierarchy management. In a first time I'll keep everything on master and keep the name of chapter files, this is simpler and can always be tweaked later with some git manipulations later, I guess.

Cheers

[psychoslave]

For crossreference, I came here from https://internals.rust-lang.org/t/how-can-i-help-regarding-internationalisation-and-translation-of-documentation/8962/5

[psychoslave]

Hello, @carols10cents I would love to have feedback from your part, as you seem to be the most active person accross the issues related to translations. Cheers 😄

[carols10cents]

Hi @psychoslave! I haven't been involved directly in any translation efforts. I'd take a look at the other repos linked in the Translations appendix (I'm going to add yours in a minute) and see how they're managing their translation repos.

It's all a bit up in the air because mdbook doesn't have any built-in support for translations, but once it does, we'd like to do whatever is needed by that support.

So for now, it's up to each translation how to manage their repo, and we'll transition the translations when we know what to transition them to!

[psychoslave]

Thank you very much for your feedback @carols10cents

I will just keep going in the most straightforward way then, that is put everything in master, replacing current text with their translation. As you said, we can manage plumb it back to whatever target happen to pop out of the issue of mdbook support for translations.

I also welcome any suggestion, pull request, and so on from other Esperanto translations of course. If anyone is able and willing to help, but has some doubt or concerns on the contribution process, just let me know. Cheers

[psychoslave]

Hello everybody, I'm please to announce that slowly but surely the Esperanto translation is progressing, slowly but surely, with a first chapter completely translated chapter Kio estas proprigo? (What is ownership), and a English-Esperanto glossary containing already more than 60 technical term correspondences.

Of course it's just a first pass, and at this point a review by other people would be more than welcome. So if you speak Esperanto just read the previous documents and give feedback. Or if you know some people who speak Esperanto, please suggest them to do this review.

As a side note, it might look curious that the first chapter translated was not chapter 1. This chapter was selected as ownership is the most central specific feature of the language, and so the dedicated chapter surely provide a good point entry point relating to most tedious translation challenges. The idea was thus to resolve most translation difficulties right from the start to make the rest of the translation easier.

Now, that's not a complete "job done", but surely it's a milestone that give a good excuse to celebrate 🍾 (although on this regard, like in science, anything goes) !

[psychoslave]

Hi everybody. I just wanted to let you know that the translation is going on, with foreword, until chapter 01-03 included waiting for feedback. As previously, the glossary was augmented to harmonize terminology translation.

Cheers

[LukeMarlin]

Hi @psychoslave . I'm currently learning both Rust & Esperanto so I'm afraid I cannot help you in this endeavor. However, since you mentioned a glossary, I thought that maybe you don't know Komputeko which already holds a nice amount of IT related terms from EN, NL, FR to EO and vice versa. While some terms might really be Rust-specific, Komputeko might help you for the rest!

Anyway, it's great to see some fellow esperantists here! Keep it up :)

[psychoslave]

Thank you @LukeMarlin for the feedback. Actually I already knew Komputeko, that I use and complement with other online resources, like Majstro, and printed dictionaries.

[psychoslave]

Also note that my lake of activity on the translation is only due to my involvement to Wiki Loves Love until the end of the month, which let me less time for this translation project.

To give some news, I also created a branch kutimema, as I tend to make a lot of "neologisms" on the master branch. The idea behind this neologisms is to better connect related concepts preferring common lexical roots and power of Esperanto smart affixes to more traditional terms that don't make all this semantics connection straight forward in the lexical items.

I went with a branch for now, but actually I would be more satisfy with a solution that use some variable system where the vocabulary diverge. So I will have to look at what the markdow book system allow on this regards, and links are welcome.

[psychoslave]

Also, note that I in my translation I add comment in code sample of ideas how the code could be equally expressed with plain Esperanto words instead of using ideograms/symbols (+, = and so on).

This comments are not final, but are ideas I have as I try to translate the code to plain Esperanto. The idea would be to later work on integrating into the Rust compiler facilities to allow to use this kind of Rust dialects.

[psychoslave]

And an other idea that popped in my mind at some point was to import the whole book on Wikibook to benefit from the translation tools available in the Wikimedia projects, but for now I judged preferable to directly start translation rather than delay further the first steps adding burden to migrate the text into a Wikified version.