Document translation to Spanish

[rodalexanderson]

Not sure if it would be considered as a new feature, but translating documentation to Spanish would help adoption to millions of potential users

[Shinigami92]

Not sure if it would be considered as a new feature, but translating documentation to Spanish would help adoption to millions of potential users

The "issue" is that we extract 90% of our docs directly from the JSDoc from the source code.
So not sure if we can do so much about that, but did you tried already e.g. Chrome Website Translation?

[rodalexanderson]

I could actually do the translation as part of my contribution, I really like fakerjs.

The issue with Latin American countries is that English is viewed as a language hard to learn and I want to reduce that barrier.

[matthewmayer]

I think translating ALL the documentation would be overkill, after all the method names are always going to be in English, so telling you that faker.animal.cat gives you a gata might not be that helpful.

That said, I think a basic getting started guide which recaps basic installation and usage and key modules in other languages could be useful?

[rodalexanderson]

First of all, methods, variables, reference code, and other types of data and structures are never translated. Here you can see the Official React guide, where they do translate docs to 6 more languages https://react.dev/community/translations. Even though you won't understand the translation, you can get a good look of how tech documentation is actually translated.

I'm really surprised of the negativity of an open source project to get FREE translation of the documentation to get more adoption. I guess in this space, only contributions that benefit the actual product are welcomed.

[matthewmayer]

Sorry if it came off as negativity. I think we don't want you to underestimate the difficulty of maintaining docs for the entire project in another language especially given the way that JSDocs are used to embed the docs into the code and automatically generate the docs website.

But if we can find a way to make this easy to maintain I think everyone would be in favour. I'd still suggest starting with a more simple getting started guide which might attract more multilingual contributors to help with a docs translation project and build the toolkit we would need for multi language docs.