Comments (5)
I think that the first issue that comes to mind is: We need to consider that there are several definitions which are very specific and we might not want to translate. For example, lets consider pull request
, the translation (literally is: solicitud de extracción
) in Spanish really doesn't make any sense, because the meaning of a PR is tied to the context of Git, which is completely in English, and by translating such definitions, I feel that they loose that relationship. Also in normal conversation, even when speaking in Spanish, this definitions aren't translated, you say: "Podes revisar mi PR?" o "El PR para arreglar los problemas con el registro esta listo".
Also we need to understand the target audience of the translated docs. The audience is Spanish speaking developers, we want them to understand what they are reading, and learn what they don't know. If somebody doesn't know what a PR is, that person won't be able to find what solicitud de extracción
means, cause in Spanish this is not used in any context that is remotely related to Git.
TL;DR: We should consider that not every word or definition will have a proper translation in Spanish, and that using the English version will be ok.
from angular-es.
Yes, you are 100% right. I will compile a list of words that we wouldn't translate.
As a coordinator between all translations, I will see which words can be translated in what languages.
Components and directives are some easy to translate in spanish, but stuff like data-binding is not.
from angular-es.
I agree. May I suggest, in order to create a proper style guide we might want to translate a few pages or partials and from those changes create the style guild and go on into translating bigger part of the website like the docs.
from angular-es.
I'm almost done with the 5 min quickstart and we can use it as reference.
from angular-es.
from angular-es.
Related Issues (20)
- Docs TS: Routing & Navigation
- Docs TS: Security HOT 1
- Docs TS: Structural directives HOT 1
- Docs TS: Typescript Configuration HOT 1
- Docs TS: Upgrading from 1.x
- Docs TS: Webpack
- Docs TS: Cookbooks overview HOT 2
- Docs TS: Angular 1 to 2 Quick Ref HOT 1
- Docs TS: Component Interaction HOT 2
- Docs TS: Component relative paths HOT 5
- Docs TS: Dependency Injection (Cookbook) HOT 3
- Docs TS: Dynamic Forms HOT 2
- Docs TS: Set the document title HOT 1
- Docs TS: TypeScript to JavaScript HOT 1
- Docs TS: Visual Studio 2015 QuickStart HOT 3
- Hide/Show English button doesn't work with <code>
- Features
- Footer
- Doc TS: RC4 to RC5
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 angular-es.