During a translation, it looks for patterns in millions of documents to help decide which words to choose and how to arrange them in the target language. Rather than translating languages directly, it first translates text to English and then pivots to the target language in most of the language combinations it posits in its grid, with a few exceptions including Catalan–Spanish. Launched in April 2006 as a statistical machine translation service, it used United Nations and European Parliament documents and transcripts to gather linguistic data. As of 2022, Google Translate supports 133 languages at various levels it claimed over 500 million total users as of April 2016, with more than 100 billion words translated daily, after the company stated in May 2013 that it served over 200 million people daily. It offers a website interface, a mobile app for Android and iOS, as well as an API that helps developers build browser extensions and software applications. Google Translate is a multilingual neural machine translation service developed by Google to translate text, documents and websites from one language into another. November 15, 2016 7 years ago ( ) (as neural machine translation) Perhaps try raising the idea on the contributors Gitter channel to see if anyone’s interested in helping with the internationalization (or if it’s been tried before).April 28, 2006 17 years ago ( ) (as statistical machine translation) cn and fork the repo without trying to keep the two codebases aligned. I don’t want to dissuade you from this idea, but be aware that it will be a very large project, and much of the work will be in internationalizing the existing codebase… Unless you do the same thing as freecodecamp. And that’s before thinking about date and number formats, pluralization, declension, conjugation, grammatical gender, and so on. Then, imagine this is in a repo with hundreds or thousands of files, many of which contain hundreds or thousands of lines of code, with many different file formats. If it’s the translator, let’s hope that they copy over all the code perfectly, and also that they don’t try to translate “sweetalert”, which looks syntactically identical to the translatable string (both are in func('str') format). Now, who’s responsible for updating the Russian version? If it’s the developers, this would just add a massive amount to their workload, especially with many languages. However, now the developers want to change the plain alert to a sweetalert, so the original file becomes: const swal = require('sweetalert') Translate the text directly inline (hoping that the translator fully understands things like escape sequences and markup…).In order to translate this file, we need to: As for why this is required…įile: helloworld.js alert('Hello, world!') None (or very little?) of the fCC codebase is internationalized, which is usually a required first step before translation. Similarly, APIs that are blocked in China are swapped out for ones that aren’t.Įven assuming you want to create more of a traditional, one-to-one translation, that still won’t be elementary. For example, there’s a “bullet screen” project, where you create a UI similar to some popular Chinese video sharing sites. It’s based on an older version of the curriculum, with some of the content swapped out or localized. cn isn’t just a translation - it’s a full-on fork of fCC. As far as I know, the only existing translation of fCC is the Chinese one, freecodecamp.cn, which has… semi-official status? (Maybe can confirm?)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |