Comments (2)
The idea of translating has come up multiple times over the years but nobody has pitched specifically how this will work. The old guides changed very frequently, an previously translation efforts in the community were not able to keep up.
Versioned guides mitigate this problem somewhat – once a guide is published we leave its content in place – but open up a new problem: The entire set of guides would need to be re-translated every six weeks.
There are also the significant social issues around translations: identifying and vetting translators and their translations. Many effort at translations I've seen are performed by over-eager beginners in a new language or ESL with low English proficiency. As someone who isn't fluent in Japanese (as an example), who do I
We've never said "no" to the idea of translating the docs. In fact, the core team would love this. It would also be a great way for community member with the requisite languages skills to contribute significantly.
However, planning how this process works is significantly more effort than selecting a specific tool or service.
The call to action on this is: are you willing to investigate and write up a detailed proposal on how this would work so the core team can easily
from guides.
Closing this for now, as it's known desired feature, we just need a contributor to do the work or write up a plan of action.
from guides.
Related Issues (20)
- Add a section on promises to the JS primer HOT 1
- Give an example for controller usage HOT 1
- Make first paragraph of custom adapters more beginner friendly
- In ember tutorials: acceptance tests now fail after Mirage is added HOT 2
- Explain `.[]` before `.@each` in "Computed Properties and Aggregate Data" HOT 2
- [Tutorial] autocomplete component example documentation bug
- [Tutorial] this.on referent does not exist HOT 1
- [Tutorial] Tests Fail With 404 on /api/rentals after Ember Data step HOT 5
- [Tutorial] Integration test fails on triggerKeyEvent() HOT 1
- Link to lookup API HOT 2
- Brace expansion on non-nested properties? HOT 2
- Update core concepts diagram
- More clear polymorphism example code HOT 1
- Update the guides to remove usage of `.get`
- Document "Optional Features"
- Make it clearer where actions can be passed & used HOT 2
- creating records with relationships needs more detail HOT 2
- Document {{let}} helper as a built-in helper HOT 3
- Off by 1 error in object-model/computed-properties-and-aggregate-data/ HOT 3
- NOTICE - THIS REPOSITORY IS DEPRECATED
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 guides.