Merge in remaining i18n work

locales/core.ftl

@@ -0,0 +1,31 @@
+-security-at-rust-lang-org-anchor =
+        <a href="mailto:[email protected]">[email protected]</a>
+-rust-security-team-key-href =
+        /static/keys/rust-security-team-key.gpg.ascii
+-rust-pgp-key-mit-keyserver-href =
+        https://pgp.mit.edu/pks/lookup?op=vindex&amp;search=0xEFB9860AE7520DAC"
+-wikipedia-rfpolicy-href =
+        https://en.wikipedia.org/wiki/RFPolicy
+
+## Security coordinator email addreses and links to their public keys
+-security-coordinator-email-anchor =
+        <a href="mailto:[email protected]">Steve Klabnik</a>
+-security-coordinator-public-key-href =
+        https://pgp.mit.edu/pks/lookup?op=vindex&amp;search=0xDAE717EFE9424541
+-backup-security-contact-email-anchor =
+        <a href="mailto:[email protected]">Alex Crichton</a>
+-backup-security-contact-public-key-href =
+        https://pgp.mit.edu/pks/lookup?op=vindex&amp;search=0x5D54B6F551FF5E33
+
+-internals-rust-lang-org-href =
+        https://internals.rust-lang.org/
+
+## Security mailing list links
+-rustlang-security-announcements-google-groups-forum-href =
+        https://groups.google.com/forum/#!forum/rustlang-security-announcements
+-rust-security-announcements-mailing-list-href =
+        https://groups.google.com/group/rustlang-security-announcements/subscribe
+-rustlang-security-announcements-subscribe-anchor =
+        <a href="mailto:[email protected]">[email protected]</a>
+-distros-openwall-email-anchor =
+        <a href="https://oss-security.openwall.org/wiki/mailing-lists/distros">distros@openwall</a>

locales/en-US/404.ftl

@@ -0,0 +1,7 @@
+### Translation file for the rust-lang.org 404 page.
+
+## 404 (templates/404.hbs)
+
+error404-page-title = 404
+error404-subtitle = Whoops, this page doesn’t exist :-(
+error404-img-alt = 404 not found image

locales/en-US/cli.ftl

@@ -8,8 +8,6 @@ cli-page-heading = Command-line apps
 
 ## templates/components/what/cli/pitch.hbs
 
-cli-pitch-heading = Why Rust?
-
 cli-pitch-solid-img-alt = Shield with a checkmark
 cli-pitch-solid-heading = Solid and quick
 cli-pitch-solid-description = Even if you’re just writing a short one-off
@@ -73,7 +71,6 @@ cli-maintainable-refactoring-link = Refactoring Rust
 
 ## templates/components/what/cli/example.hbs
 
-cli-example-heading = Get started!
 cli-example-description = Writing a command-line app is a great way to learn Rust.
 cli-example-inputs-heading = Define your inputs
 cli-example-main-heading = Write your tool
@@ -82,8 +79,6 @@ cli-example-link = Learn more with the CLI book
 
 ## templates/components/what/cli/production.hbs
 
-cli-production-heading = Production use
-
 cli-production-sentry-img-alt = sentry logo
 cli-production-sentry-quote =
         One of the reasons we liked Rust was the crates.io ecosystem. [...]

locales/en-US/code-of-conduct.ftl

@@ -0,0 +1,40 @@
+### Translation file for page: https://www.rust-lang.org/policies/code-of-conduct
+
+## templates/policies/code-of-conduct.hbs
+
+coc-page-heading = Code of conduct
+
+coc-conduct-heading = Conduct
+coc-conduct-description =
+        <ul>
+          <li>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.</li>
+          <li>Please avoid using overtly sexual aliases or other nicknames that might detract from a friendly, safe and welcoming environment for all.</li>
+          <li>Please be kind and courteous. There’s no need to be mean or rude.</li>
+          <li>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.</li>
+          <li>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.</li>
+          <li>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.</li>
+          <li>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 { $coc-rust-moderation-team-anchor } 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.</li>
+          <li>Likewise any spamming, trolling, flaming, baiting or other attention-stealing behavior is not welcome.</li>
+        </ul>
+coc-conduct-description-team-anchor-text = Rust moderation team
+coc-conduct-email-button = Email The Moderation Team
+
+coc-moderation-heading = Moderation
+coc-moderation-description =
+        <p>These are the policies for upholding our community’s standards of conduct. If you feel that a thread needs moderation, please contact the { $coc-rust-moderation-team-anchor }.</p>
+        <ol>
+          <li>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.)</li>
+          <li>Remarks that moderators find inappropriate, whether listed in the code of conduct or not, are also not allowed.</li>
+          <li>Moderators will first respond to such remarks with a warning.</li>
+          <li>If the warning is unheeded, the user will be “kicked,” i.e., kicked out of the communication channel to cool off.</li>
+          <li>If the user comes back and continues to make trouble, they will be banned, i.e., indefinitely excluded.</li>
+          <li>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.</li>
+          <li>If a moderator bans someone and you think it was unjustified, please take it up with that moderator, or with a different moderator, <strong>in private</strong>. Complaints about bans in-channel are not allowed.</li>
+          <li>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.</li>
+        </ol>
+        <p>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.</p>
+        <p>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.</p>
+        <p>The enforcement policies listed above apply to all official Rust venues; including Discord channels (https://discord.gg/rust-lang); 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.</p>
+        <p><i>Adapted from the <a href="http://blog.izs.me/post/30036893703/policy-on-trolling">Node.js Policy on Trolling</a> as well as the <a href="https://www.contributor-covenant.org/version/1/3/0/">Contributor Covenant v1.3.0</a>.</i></p>
+
+coc-moderation-description-team-anchor-text = Rust moderation team

locales/en-US/common.ftl

@@ -1,6 +1,13 @@
-# Translations that appear on most/all pages
+## Translations that appear on many pages
 
-# components/nav.hbs
+rust = Rust
+
+get-started-exclamation = Get started!
+getting-started = Getting started
+why-rust = Why Rust?
+production-use = Production use
+
+## components/nav.hbs
 
 nav-install = Install
 nav-learn = Learn
@@ -13,7 +20,8 @@ choose-language = Language
 
 nav-logo-alt = Rust Logo
 
-# components/footer.hbs
+## components/footer.hbs
+
 footer-doc = Documentation
 footer-ask = Ask a Question on the Users Forum
 footer-status = Check Website Status

locales/en-US/embedded.ftl

@@ -0,0 +1,104 @@
+### Translation file for https://www.rust-lang.org/what/embedded
+
+## templates/what/embedded.hbs
+
+# Page Title
+embedded-page-title = Embedded devices
+
+
+## Why Rust? (templates/components/what/pitch.hbs)
+
+embedded-pitch-analysis-alt = A microscope
+embedded-pitch-analysis-heading = Powerful static analysis
+embedded-pitch-analysis-description =
+        Enforce pin and peripheral configuration at compile time. Guarantee that resources won’t be used by unintended parts of your application.
+
+embedded-pitch-memory-alt = A RAM stick
+embedded-pitch-memory-heading = Flexible memory 
+embedded-pitch-memory-description =
+        Dynamic memory allocation is optional. Use a global allocator and dynamic data structures. Or leave out the heap altogether and statically allocate everything.
+
+embedded-pitch-concurrency-alt = Gears
+embedded-pitch-concurrency-heading = Fearless concurrency
+embedded-pitch-concurrency-description =
+        Rust makes it impossible to accidentally share state between threads. Use any concurrency approach you like, and you’ll still get Rust’s strong guarantees.
+
+embedded-pitch-interop-alt = Handshake
+embedded-pitch-interop-heading = Interoperability
+embedded-pitch-interop-description =
+        Integrate Rust into your existing C codebase or leverage an existing SDK to write a Rust application.
+
+embedded-pitch-portability-alt = Luggage trolley
+embedded-pitch-portability-heading = Portability
+embedded-pitch-portability-description =
+        Write a library or driver once, and use it with a variety of systems, ranging from very small microcontrollers to powerful SBCs.
+
+embedded-pitch-community-alt = Shield Logo
+embedded-pitch-community-heading = Community driven
+embedded-pitch-community-description =
+        As part of the Rust open source project, support for embedded systems is driven by a best-in-class open source community, with support from commercial partners.
+
+embedded-learn-more-link = Learn more
+
+
+## Showcase (templates/components/what/showcase.hbs)
+
+embedded-showcase-heading = Showcase
+
+embedded-showcase-quote =
+        “I was so excited when I came across Rust, from Mozilla. Rust is a new programming language, with the tag line ‘safe, fast, concurrent – pick three.’ It also has an assured future, with a powerful, committed user community.”
+embedded-showcase-quote-attribution =
+        – Jonathan Pallant, Senior Consultant, Cambridge Consultants
+embedded-showcase-see-more-link = See More
+
+embedded-showcase-video-description =
+        <a href="https://vimeo.com/224912526">Securing the future, with Rust</a> from <a href="https://vimeo.com/cambridgeconsultants">Cambridge Consultants</a> on <a href="https://vimeo.com">Vimeo</a>.
+
+
+## Get started! (templates/components/what/embedded/get-started.hbs)
+
+embedded-get-started-discovery-book-alt = DIP-6 package
+embedded-get-started-discovery-book-heading = The Discovery book
+embedded-get-started-discovery-book-description =
+        Learn embedded development from the ground up&mdash;using Rust!
+
+embedded-get-started-embedded-rust-book-alt = TFQP-16 package
+embedded-get-started-embedded-rust-book-heading = The Embedded Rust book
+embedded-get-started-embedded-rust-book-description =
+        Already familiar with Embedded development? Jump in with Rust and start reaping the benefits.
+
+embedded-get-started-embedonomicon-alt = BGA package
+embedded-get-started-embedonomicon-heading = The Embedonomicon
+embedded-get-started-embedonomicon-description =
+        Look under the hood of foundational embedded libraries.
+
+embedded-get-started-read-link = Read
+embedded-get-started-more-documentation-link = More Documentation
+
+
+## Production use (templates/components/what/embedded/testimonials.hbs)
+
+embedded-testimonials-sensirion-alt = Sensirion logo
+embedded-testimonials-sensirion-quote =
+        At Sensirion we recently used Rust to create an embedded demonstrator for Sensirion’s <a href="https://sensirion-automotive.com/products#PM2_5">Particulate Matter Sensor</a>. Due to the easy cross-compilation and the availability of many high quality crates on crates.io <b>we quickly ended up with a fast and robust demonstrator.</b>
+embedded-testimonials-sensirion-attribution =
+        &ndash; Raphael Nestler, Software Engineer, Sensirion
+
+embedded-testimonials-airborne-alt = Airborne Engineering Ltd logo
+embedded-testimonials-airborne-quote =
+        At Airborne Engineering Ltd. we recently used Rust to write an Ethernet bootloader, <a href="https://github.com/airborneengineering/blethrs">blethrs</a>, for our in-house data acquisition system. <b>Rust is a promising language and we’re excited to use it for our future projects, embedded and otherwise.</b>
+embedded-testimonials-airborne-attribution =
+        &ndash; Dr. Adam Greig, Instrumentation Engineer, Airborne Engineering Ltd.
+
+embedded-testimonials-49nord-alt = 49nord logo
+# "Fluent" requires a square bracket which is the first character of a line to be escaped like this: {"["} See https://projectfluent.org/fluent/guide/special.html
+embedded-testimonials-49nord-quote =
+        {"["}Rust] enables us to ship software faster and more correct than we thought possible. Thanks to Rust, we can take memory safety for granted, while other benefits of a zero-overhead language with a sophisticated type system help us develop maintainable software. <b>Rust makes our customers happy, as well as our engineers.</b>
+embedded-testimonials-49nord-attribution =
+        &ndash; Marc Brinkmann, CEO, 49nord
+
+embedded-testimonials-terminal-tech-alt = Terminal Technologies logo
+embedded-testimonials-terminal-tech-quote =
+        <b>We think it’s really cool that we can use a modern nice language in the embedded space</b> where usually there’s no alternative to C/C++
+embedded-testimonials-terminal-tech-attribution =
+        &ndash; Aleksei Arbuzov, Senior Software Engineer, Terminal Technologies

locales/en-US/homepage.ftl

@@ -28,7 +28,6 @@ production-testimonial-yelp-alt = Yelp Logo
 
 
 # components/panels/language-values.hbs
-language-values-why-rust = Why Rust?
 
 language-values-performance = Performance
 language-values-performance-blurb = Rust is blazingly fast and memory-efficient: with no runtime or

locales/en-US/learn.ftl

@@ -64,7 +64,6 @@ learn-unstable-button = Read the unstable book
 
 ## learn/get-started.hbs
 
-learn-setup-heading = Getting started
 learn-setup = Quickly set up a Rust development environment and write a small app!
 
 learn-install-heading = Installing Rust

locales/en-US/licenses.ftl

@@ -0,0 +1,20 @@
+### Translation file for page: https://www.rust-lang.org/policies/licenses
+
+## templates/policies/licenses.hbs
+
+licenses-page-heading = Licenses
+
+licenses-license-heading = License
+licenses-license-general-description =
+        The Rust Programming Language and all other official projects, including this website, are generally dual-licensed:
+licenses-apache-v-2-0-link = Apache License, Version 2.0
+licenses-mit-link = MIT license
+licenses-license-specific-description =
+        <p>Specific licensing info for each project can be found in its GitHub Repository.</p>
+        <p>Third-party logos may be subject to third-party copyrights and trademarks, and are not available under the same license as the rest of the Rust website.</p>
+        <p>If you have a specific question or concern about how the Rust project or any of its associated projects are licensed, please contact the Rust Core Team.</p>
+licenses-license-email-link = Email The Core Team
+
+licenses-attribution-heading = Attribution
+licenses-attribution-description =
+        Icons made by <a href="http://www.freepik.com" title="Freepik">Freepik</a> from <a href="https://www.flaticon.com/" title="Flaticon">www.flaticon.com</a>, licensed by <a href="http://creativecommons.org/licenses/by/3.0/" title="Creative Commons BY 3.0">CC-3.0-BY</a>