Replace the whole contents with the latest English edition

- Rename the old Japanese contents to "src-ord" directory.
- Delete old "docs" directory containing generated HTML files.
- Delete all other old stuff such as "Cargo.toml", "src/*.rs" and
  "node-modules".
- Update git submodule ".examples" to the latest revision. (This submodule
  is pointing to the English edition at rust-lang/rust-by-example)
- Copy all the English stuff including "src/*.md" and "book.toml".
- Change the build tool from gitbook to mdbook.
- Update the CircleCI config and a shell script.

Author: tatsuya6502

.circleci/config.yml

@@ -1,47 +1,19 @@
 version: 2
 
-# TODO: ENHANCEME: (tatsuya6502) Utilize Circle CI cache for the following items:
-# - The "update" tool (written in Rust) with Cargo's crates.io-index
-# - node_modules
-
 jobs:
   build:
     docker:
-      - image: quay.io/rust-lang-ja/circleci:rust-by-example
+      - image: hrektts/mdbook:0.3.5
     parallelism: 1
     steps:
       - checkout
       # Remove .gitconfig added by Circle CI as cargo doesn't support ssh authorization
       - run: rm -f ~/.gitconfig
-      - run: make clean all
-      - run:
-          name: Building book
-          command: |
-            source $NVM_DIR/nvm.sh
-            make book
-      - run:
-          name: Creating artifact
-          command: |
-            mkdir /tmp/rust-by-example
-            cp -rp ./stage/_book/* /tmp/rust-by-example/
-            cp -rp ./gitbook/* /tmp/rust-by-example/
-            # Fix fonts path
-            sed -i -e 's!.//fonts/!./fonts/!g' /tmp/rust-by-example/gitbook/style.css
-            # Change mode-rust.js path. An example of CircleCI artifact URI:
-            # "https://33-57046702-circle-artifacts.com/0/"
-            sed -i -e "s!/gitbook/plugins/gitbook-plugin-rust-playpen/mode-rust.js!/${CIRCLE_NODE_INDEX}/rust-by-example/gitbook/plugins/gitbook-plugin-rust-playpen/mode-rust.js!" /tmp/rust-by-example/gitbook/plugins/gitbook-plugin-rust-playpen/editor.js
-            cd /tmp
-            tar cJf rust-by-example-ja.txz rust-by-example
-      - run:
-          name: Running tests (allowing failures)
-          command: make test || true
-      - store_artifacts:
-          path: /tmp/rust-by-example
-          distination: rust-by-example
+      - run: rm -rf docs
+      - run: mdbook build
+      - run: mdbook test
       - store_artifacts:
-          path: /tmp/rust-by-example-ja.txz
-          distination: rust-by-example-ja.txz
-      - run: rm -rf /tmp rust-by-example
+          path: docs
       - deploy:
           name: If master branch, publish to GitHub Page
           command: |

.examples-en

@@ -0,0 +1,2 @@
+# Set the default behavior, in case people don't have core.autocrlf set.
+* text=auto eol=lf

.gitattributes

@@ -1,13 +1,2 @@
-*.swp
-Cargo.lock
-bin/*
-count_table
 docs/
-gh-pages
-node_modules/*
-!node_modules/gitbook-plugin-rust-playpen
-node_modules/gitbook-plugin-rust-playpen/book/ace
-node_modules/gitbook-plugin-rust-playpen/book/mode-rust.js
-rust-playgen
-stage/*
-target
+

.gitignore

@@ -0,0 +1,40 @@
+# The Rust Code of Conduct
+
+A version of this document [can be found online](https://www.rust-lang.org/conduct.html).
+
+## Conduct
+
+**Contact**: [[email protected]](mailto:[email protected])
+
+* We are committed to providing a friendly, safe and welcoming environment for all, regardless of level of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other similar characteristic.
+* On IRC, please avoid using overtly sexual nicknames or other nicknames that might detract from a friendly, safe and welcoming environment for all.
+* Please be kind and courteous. There's no need to be mean or rude.
+* Respect that people have differences of opinion and that every design or implementation choice carries a trade-off and numerous costs. There is seldom a right answer.
+* Please keep unstructured critique to a minimum. If you have solid ideas you want to experiment with, make a fork and see how it works.
+* We will exclude you from interaction if you insult, demean or harass anyone. That is not welcome behavior. We interpret the term "harassment" as including the definition in the <a href="http://citizencodeofconduct.org/">Citizen Code of Conduct</a>; if you have any lack of clarity about what might be included in that concept, please read their definition. In particular, we don't tolerate behavior that excludes people in socially marginalized groups.
+* Private harassment is also unacceptable. No matter who you are, if you feel you have been or are being harassed or made uncomfortable by a community member, please contact one of the channel ops or any of the [Rust moderation team][mod_team] immediately. Whether you're a regular contributor or a newcomer, we care about making this community a safe place for you and we've got your back.
+* Likewise any spamming, trolling, flaming, baiting or other attention-stealing behavior is not welcome.
+
+## Moderation
+
+
+These are the policies for upholding our community's standards of conduct. If you feel that a thread needs moderation, please contact the [Rust moderation team][mod_team].
+
+1. Remarks that violate the Rust standards of conduct, including hateful, hurtful, oppressive, or exclusionary remarks, are not allowed. (Cursing is allowed, but never targeting another user, and never in a hateful manner.)
+2. Remarks that moderators find inappropriate, whether listed in the code of conduct or not, are also not allowed.
+3. Moderators will first respond to such remarks with a warning.
+4. If the warning is unheeded, the user will be "kicked," i.e., kicked out of the communication channel to cool off.
+5. If the user comes back and continues to make trouble, they will be banned, i.e., indefinitely excluded.
+6. Moderators may choose at their discretion to un-ban the user if it was a first offense and they offer the offended party a genuine apology.
+7. If a moderator bans someone and you think it was unjustified, please take it up with that moderator, or with a different moderator, **in private**. Complaints about bans in-channel are not allowed.
+8. Moderators are held to a higher standard than other community members. If a moderator creates an inappropriate situation, they should expect less leeway than others.
+
+In the Rust community we strive to go the extra step to look out for each other. Don't just aim to be technically unimpeachable, try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they're off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely.
+
+And if someone takes issue with something you said or did, resist the urge to be defensive. Just stop doing what it was they complained about and apologize. Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could've communicated better — remember that it's your responsibility to make your fellow Rustaceans comfortable. Everyone wants to get along and we are all here first and foremost because we want to talk about cool technology. You will find that people will be eager to assume good intent and forgive as long as you earn their trust.
+
+The enforcement policies listed above apply to all official Rust venues; including official IRC channels (#rust, #rust-internals, #rust-tools, #rust-libs, #rustc, #rust-beginners, #rust-docs, #rust-community, #rust-lang, and #cargo); GitHub repositories under rust-lang, rust-lang-nursery, and rust-lang-deprecated; and all forums under rust-lang.org (users.rust-lang.org, internals.rust-lang.org). For other projects adopting the Rust Code of Conduct, please contact the maintainers of those projects for enforcement. If you wish to use this code of conduct for your own project, consider explicitly mentioning your moderation policy or making a copy with your own moderation policy so as to avoid confusion.
+
+*Adapted from the [Node.js Policy on Trolling](http://blog.izs.me/post/30036893703/policy-on-trolling) as well as the [Contributor Covenant v1.3.0](https://www.contributor-covenant.org/version/1/3/0/).*
+
+[mod_team]: https://www.rust-lang.org/team.html#Moderation-team

CODE_OF_CONDUCT.md

@@ -0,0 +1,70 @@
+# Rust by Example contribution guidelines
+
+Thank you for your interest in making Rust by Example (also known as RBE)
+better! We'd love to have your contribution. We expect all contributors to
+abide by the [Rust code of conduct], which you can find at that link or in the
+[`CODE_OF_CONDUCT.md`] file in this repository.
+
+[Rust code of conduct]: https://www.rust-lang.org/policies/code-of-conduct
+[`CODE_OF_CONDUCT.md`]: https://github.com/rust-lang/rust-by-example/blob/master/CODE_OF_CONDUCT.md
+
+## License
+
+RBE is dual licenced under the MIT and Apache 2.0 licenses, and so are all
+contributions. Please see the [`LICENSE-MIT`] and [`LICENSE-APACHE`] files in
+this directory for more details.
+
+[`LICENSE-MIT`]: https://github.com/rust-lang/rust-by-example/blob/master/LICENSE-MIT
+[`LICENSE-APACHE`]: https://github.com/rust-lang/rust-by-example/blob/master/LICENSE-APACHE
+
+## Pull Requests
+
+To make changes to RBE, please send in pull requests on GitHub to the `master`
+branch. We'll review them and either merge or request changes. Travis CI tests
+everything as well, so you may get feedback from it too.
+
+If you make additions or other changes to a pull request, feel free to either amend
+previous commits or only add new ones, however you prefer. We may ask you to squash
+your commits before merging, depending.
+
+
+## Issue Tracker
+
+You can find the issue tracker [on
+GitHub](https://github.com/rust-lang/rust-by-example/issues). If you've found a
+problem with RBE, please open an issue there.
+
+We use the following labels:
+
+* `enhancement`: This is for any request for new sections or functionality.
+* `bug`: This is for anything that's in RBE, but incorrect or not working.
+* `discussion`: A discussion about improving something in RBE; this may lead to new
+  enhancement or bug issues.
+* `E-mentor`: This issue has someone dedicated to helping a new contributor fix it!
+  Can apply to both enhancement or bug issues.
+
+## Development workflow
+
+To build RBE, [install Rust], and then:
+
+```bash
+$ git clone https://github.com/rust-lang/rust-by-example
+$ cd rust-by-example
+$ cargo install mdbook
+$ mdbook build
+```
+
+[install Rust]: http://rust-lang.org/install.html
+
+The files will be in the `book` directory at the top-level; `mdbook serve` will
+open the contents in your web browser.
+
+To run the tests:
+
+```bash
+$ mdbook test
+```
+
+If you're adding a new chapter, you'll need to edit `src\SUMMARY.md` to add it. If
+you're tweaking an existing example, you'll need to edit the corresponding file; check
+`src\SUMMARY.md` to see a mapping of where chapters go to files.