quadrifoglio / rust-book-fr Goto Github PK
View Code? Open in Web Editor NEWThis project forked from rust-lang/book
[Inactive] French translation of the Rust Programming Language Book
Home Page: https://doc.rust-lang.org/book/
License: Other
This project forked from rust-lang/book
[Inactive] French translation of the Rust Programming Language Book
Home Page: https://doc.rust-lang.org/book/
License: Other
Should we have to translate all the codes ("listing" in English book) in French ?
Example (randomly) :
pub fn search<'a>(query: &str, contents: &'a str) -> Vec<&'a str> { let mut results = Vec::new(); for line in contents.lines() { if line.contains(query) { results.push(line); } } results }Listing 12-19: Storing the lines that match so we can return them
Or keeping English names are OK for our readers ? (i'm thinking that)
What is your point of view about it ?
Hi !
Since we're currently reviewing chapters by chapters, I'm opening this issue as a place to start discussion on the harmonization of the translation of keywords, so that we stay consistent throughout the Book. If you have any idea of a better place to keep such a list, don't hesitate to mention it, since I'm not sure an issue is the best place for that (maybe a wiki page?).
Here are some words I'm struggling with giving them an "obvious" translation :
How would you translate them?
Hi everyone,
The git history of this french translation repository is a bit of a mess.
Although our translation commits happen on a dedicated branch, one for each chapter, the current strategy is that eventually those branches get merged into master after their review.
This results in our work being diluted with the original writers' work, in the master branch.
I was thinking that maybe it would be better to create a branch dedicated to our translation work, called something like "french". The idea is that we merge our translation commits into that branch via the usual PR process, therefore keeping our work separate from the original team's work.
I would periodically rebase that "french" branch on the English repository's master branch in order to keep the original chapters' source up to date, and our translation commits would be easily distinguishable as they would come first in the git history.
What do you think of that idea ? Do you see any benefits or drawbacks ?
Thanks, and have a nice evening !
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.