Comments (37)
hey @mgeisler,
could you please create an issue for Farsi/Persian as well?
more than happy to contribute.
cheers
from comprehensive-rust.
Working on the Chinese Mandarin translation of the book, thanks for your prior instructions! Can you help create an issue for that?
from comprehensive-rust.
Working on the Chinese Mandarin translation of the book, thanks for your prior instructions! Can you help create an issue for that?
Thanks @hilbert-yaa for creating the issue, I've added it to the list above!
Hey π Letβs translate it in Russian. I can do that
Awesome @baltuky, I've created #326 for that.
from comprehensive-rust.
could I help with this issue in Spanish? I had not seen that the ticket for Spanish was open and I made progress with the translation.
from comprehensive-rust.
would be more than happy to give Japanese a try if not already being handled
from comprehensive-rust.
would be more than happy to give Japanese a try if not already being handled
Hi @CoinEZ-JPN, that would be amazing! Just follow the translation instructions and refer to #652 in your PRs.
You're encouraged to submit a PR with an almost-untranslated po/ja.po
file. That way you can check that the tooling works for you. (This applies to all languages: please ensure there is a po/xx.po
file for your language. That also makes it easier for others to help out!).
from comprehensive-rust.
Hey @mbpouri, there is now a #671 for you to work on! Thanks a lot for offering to help!
from comprehensive-rust.
Hi there! Just a heads up: I hope to land google/mdbook-i18n-helpers#46 in the next few days. After that, I will make a new release of mdbook-i18n-helpers
and normalize all our PO files.
The PR is the final bit needed for us to update mdbook-i18n-helpers
. The new version extracts text in a much more fine grained way. As you've all seen, we currently extract the text as-is, with indentation and newlines etc. The new version will extract text in a "logical" fashion: paragraphs are unwrapped, list items are extracted one-by-one, headers are extracted without leading "#". Even tables are extracted better: you now get a message per cell instead of a single message with the entire table.
I hope this will make your lives easier since you'll see much less Markdown syntax in your PO files!
from comprehensive-rust.
@henrif75, could you put refresh PRs for the translations that haven't been touched in, say, 2-3 months? Just to clean them up and incorporate the new content for anyone who wants to contribute.
from comprehensive-rust.
Hi all! I wanted to let you know about #1460. This is an update to mdbook-i18n-helpers which will remove ~6k lines from the PO files. It changes the way code blocks are processed: we now extract strings and comments directly.
If you have translated the comments of one or more code blocks, then please run mdbook-i18n-normalize
on your PO file to preserve the translations. You can do this before/after refreshing the translation. See #1461 for an example PR which shows the state after normalization.
I hope this further reduces the churn in the translations and makes it easier to work with the large code samples in this course.
from comprehensive-rust.
@henrif75 i will start working on it soon i can also help with code review as i am a developer too
from comprehensive-rust.
Is there a translation in French? If not i would like to do it.
from comprehensive-rust.
Is there a translation in French? If not i would like to do it.
Hey @dblackstar, nobody has signed up for that yet! It would be awesome to have a French translation too. Let me quickly create an issue for that.
from comprehensive-rust.
Hey π Letβs translate it in Russian. I can do that
from comprehensive-rust.
I've attached Cloud Translate versions of the messages.pot
to the new issues. Please let me know if you need me to update anything else. You can also generate those yourself via #291.
from comprehensive-rust.
I've done that on my side. Thanks!
from comprehensive-rust.
Hi all, if you haven't already, please take a look at the Rust Book translations: https://doc.rust-lang.org/book/appendix-06-translation.html. When possible, I suggest using the same terminology as they use.
from comprehensive-rust.
Hi @mgeisler, I could do a Polish translation.
from comprehensive-rust.
Hi @mgeisler, I could do a Polish translation.
Hi @pierd, thanks a lot, that would be super cool! If you create an issue for it, then I'll link it here!
from comprehensive-rust.
Created the issue for Polish translation: #399
from comprehensive-rust.
Do we generally translate source code snippets? IMHO it definitely makes sense for the comments and maybe string literals but not really for variable/function/etc names.
I was checking other translations for some examples. Brazilian Portuguese version translates some string literals and some comments but not all (modules, some exercise) while Korean version leaves the string literals as is but translates all comments (modules, the same exercise).
from comprehensive-rust.
Do we generally translate source code snippets? IMHO it definitely makes sense for the comments and maybe string literals but not really for variable/function/etc names.
I agree: I would definitely translate the comments and perhaps also strings.
Note that even if you want to reuse the English text for the translation, it pays off to copy it (most PO editors can do this easily). This is because it gives you one string less to care about when looking at the PO file.
@jiyongp, @jooyunghan, @rastringer, @hugojacob, did you discuss this too?
It would be great to update TRANSLATIONS.md
with guidance about this.
from comprehensive-rust.
No. I don't think we (Korean translators) have reached to a consensus on that. Even the Korean translation of the Rust book is inconsistent in its translations of comments.
I just wish we seldom use comments in code snippets.
from comprehensive-rust.
For production-ready translations, I'd translate comments and string literals as well (but not variables) in the code snippets. For this project, I put more focus on slide text and speaker notes than code snippets. In most cases, comments/literals were in simple/short English which I thought we could do it later when we have time.
from comprehensive-rust.
from comprehensive-rust.
Hey all, I've written up a bit about how I suggest approaching reviews of the many translation PRs. Basically, help the contributors and err on the side of accepting contributions over trying to make everything perfect in the first go.
from comprehensive-rust.
Just a heads up: I hope to land google/mdbook-i18n-helpers#46 in the next few days.
The PR to mdbook-i18n-helpers is merged. I will make a release tomorrow and put up a PR which normalizes the PO files. I will also apply the same normalization to all in-flight PRs β this should allow them to merge cleanly onto the normalized PO files.
from comprehensive-rust.
Hi all translators! The PRs are all merged, thanks @henrif75 for helping with that!
You are all invited to refresh the translations now. Afterwards, please go through the PO files and remove fuzzy markers.
from comprehensive-rust.
Hi again, I had another idea for how we can avoid churn in the PO files: google/mdbook-i18n-helpers#127. Put simply, we could round or remove the line numbers. We could also remove the source location completley.
Do people here use the source location to look up the surrounding English text when translating?
from comprehensive-rust.
Hi again, I had another idea for how we can avoid churn in the PO files: google/mdbook-i18n-helpers#127. Put simply, we could round or remove the line numbers. We could also remove the source location completley.
Do people here use the source location to look up the surrounding English text when translating?
I don't use the line numbers, but the source file yes.
from comprehensive-rust.
How would that interact with poedit? I have been using this tool when working on translations.
from comprehensive-rust.
I don't use the line numbers, but the source file yes.
Okay, so rounding line numbers to 10, 20, ... would not cause much problems for you.
How would that interact with poedit? I have been using this tool when working on translations.
I hope it will handle out of bounds line numbers gracefully, but I don't know π So if the message claims to be from foo.md:120
but there are only 128 lines in foo.md
, then Poedit ought to handle this in some reasonable way.
from comprehensive-rust.
I'd be happy to help with Brazilian Portuguese.
from comprehensive-rust.
I'd be happy to help with Brazilian Portuguese.
That would be great, @azevedoalice !
You can follow instructions above and start reviewing the outstanding PRs for pt-BR.
Welcome!
from comprehensive-rust.
is there a translation for Nigeria pidgin if not will love to do that
from comprehensive-rust.
Hi @martcpp we don't and that would be awesome. In the first post of this issue, there are information on how to get started.
It would very important too if you can find another pidgin speaker to help out with code reviews in the future too.
Thank you!
is there a translation for Nigeria pidgin if not will love to do that
from comprehensive-rust.
@henrif75 i will start working on it soon i can also help with code review as i am a developer too
Hi @martcpp we don't and that would be awesome. In the first post of this issue, there are information on how to get started. It would very important too if you can find another pidgin speaker to help out with code reviews in the future too. Thank you!
is there a translation for Nigeria pidgin if not will love to do that
from comprehensive-rust.
Related Issues (20)
- Timing information enters the translations HOT 2
- Mistake in Fibonacci Exercise HOT 5
- Inconsistent text in CR2 HOT 3
- Moving too quickly between pages on the popped-out "speaker notes" window resets to non-notes view HOT 1
- Do not text wrap links HOT 3
- Eliminate horizontal scrolling in rust code blocks HOT 14
- 404 page breaks translations
- Question about "Speaker Notes" in Destructuring page HOT 2
- Error-handling crates slide should be split HOT 1
- Spanish version HOT 1
- Update translation instructions on manipulating `.po` files
- Verify and prune CODEOWNERS list for translations HOT 2
- concurrency: Avoid `1..ROUND_NUMBER` loops HOT 1
- Cannot search for "`From` and `Into`"
- `From` and `Into` slide should emphasize losslessness and infallibility
- `let`...`else` example should demonstrate denesting HOT 1
- syntax: explain that rust pervasively allows separators to be used as terminators
- Call out `Neg` trait in speaker notes
- cortex-m-rt 0.7.4 has been yanked
- Possible clarification in chapter "6.2.1. for" HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from comprehensive-rust.