By reading #153 and #1176, I seem to understand that all the non-English resources are supposed to go in separated lists, rather than being regrouped under the main theme list, even if they're not translations but really add to the list.
Can't we do better and be more inclusive to non-English speakers? For example, by adding a country flag in front of all resources, indicating the language of the resource?
Originally created by @ramnes on GitHub (Apr 30, 2018).
Original GitHub issue: https://github.com/sindresorhus/awesome/issues/1282
Please see this issue on Awesome MongoDB: https://github.com/ramnes/awesome-mongodb/issues/43
By reading #153 and #1176, I seem to understand that all the non-English resources are supposed to go in separated lists, rather than being regrouped under the main theme list, even if they're not translations but really add to the list.
Can't we do better and be more inclusive to non-English speakers? For example, by adding a country flag in front of all resources, indicating the language of the resource?
I don't think it makes sense to mix languages in the main readme. That just creates a messy experience for everyone.
Instead, make the main readme.md have only English content, then at the top of that readme, add links to other languages which can be in their own Markdown files.
For example:
readme.md
readme-jp.md
readme-no.md
When we've decided on a good format, we should document it here.
<!-- gh-comment-id:385362437 -->
@sindresorhus commented on GitHub (Apr 30, 2018):
I don't think it makes sense to mix languages in the main readme. That just creates a messy experience for everyone.
Instead, make the main readme.md have only English content, then at the top of that readme, add links to other languages which can be in their own Markdown files.
For example:
```
readme.md
readme-jp.md
readme-no.md
```
When we've decided on a good format, we should document it here.
The idea on below format makes sense for translating into multiple languages. But what we want to is to bring articles written natively by other languages instead of translation.
readme.md
readme-jp.md
readme-no.md
<!-- gh-comment-id:385378686 -->
@zhaoyi0113 commented on GitHub (Apr 30, 2018):
The idea on below format makes sense for translating into multiple languages. But what we want to is to bring articles written natively by other languages instead of translation.
```
readme.md
readme-jp.md
readme-no.md
```
I feel that the different README files structure would be interesting if there would be a lot of resources in the different languages. But most of the time that's just not the case. There's maybe 95% of the resources available in English, since English is still prominent in computer sciences, and 5% of very specific stuff not already covered by the 95% and written in some other other language.
In the age of evolved translators like DeepL, I don't see any reason to not add an article written in another language if it really adds to the list. Non-English articles could be enforced to have at least one translation, with a guideline on how to format translations.
For example, something in those lines would make sense to me:
Great resource - Description
巨大的资源 (🇨🇳 Some other great resource) - Description in English (translations: 🇬🇧)
I think such a format would also be very useful for local lists, non related to computer science, where the main language might be something else than English and with resources in different languages.
What do you think @sindresorhus?
<!-- gh-comment-id:385953544 -->
@ramnes commented on GitHub (May 2, 2018):
I feel that the different README files structure would be interesting if there would be a lot of resources in the different languages. But most of the time that's just not the case. There's maybe 95% of the resources available in English, since English is still prominent in computer sciences, and 5% of very specific stuff not already covered by the 95% and written in some other other language.
In the age of evolved translators like DeepL, I don't see any reason to not add an article written in another language if it really adds to the list. Non-English articles could be enforced to have at least one translation, with a guideline on how to format translations.
For example, something in those lines would make sense to me:
- Great resource - Description
- 巨大的资源 (:cn: Some other great resource) - Description in English (translations: :gb:)
I think such a format would also be very useful for local lists, non related to computer science, where the main language might be something else than English and with resources in different languages.
What do you think @sindresorhus?
In the age of evolved translators like DeepL, I don't see any reason to not add an article written in another language if it really adds to the list.
I have yet to see a technical paper in Chinese being readable after running it through Google Translate, but I don't see why not if it's still good after being translated.
巨大的资源 (🇨🇳 Some other great resource) - Description in English (translations: 🇬🇧)
Since the list is in English, the main link should point to the translated version. The original can be linked to in parens, like (Source).
<!-- gh-comment-id:389129238 -->
@sindresorhus commented on GitHub (May 15, 2018):
> In the age of evolved translators like DeepL, I don't see any reason to not add an article written in another language if it really adds to the list.
I have yet to see a technical paper in Chinese being readable after running it through Google Translate, but I don't see why not if it's still good after being translated.
> 巨大的资源 (🇨🇳 Some other great resource) - Description in English (translations: 🇬🇧)
Since the list is in English, the main link should point to the translated version. The original can be linked to in parens, like *([Source]())*.
Since the list is in English, the main link should point to the translated version. The original can be linked to in parens, like (Source).
Yep, and it has the advantage of forcing a proper translation in the list's main language as the main link. I definitely support that solution.
<!-- gh-comment-id:389169598 -->
@ramnes commented on GitHub (May 15, 2018):
> Since the list is in English, the main link should point to the translated version. The original can be linked to in parens, like (Source).
Yep, and it has the advantage of forcing a proper translation in the list's main language as the main link. I definitely support that solution.
Well that's the problem with other languages there is just not that much stuff into them
<!-- gh-comment-id:457126741 -->
@Kreijstal commented on GitHub (Jan 24, 2019):
Well that's the problem with other languages there is just not that much stuff into them
<!-- gh-comment-id:2700683364 -->
@Tester1234537 commented on GitHub (Mar 5, 2025):
What is the problen con the spanish
El mié, 5 mar 2025, 6:33 a. m., 偷熊计划 ***@***.***> escribió:
> 1
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/sindresorhus/awesome/issues/1282#issuecomment-2700636398>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A7TCOKL4HZNOGMOIQND4IVL2S3OHTAVCNFSM6AAAAABYL25TNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBQGYZTMMZZHA>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
> [image: touxiongjihua]*touxiongjihua* left a comment
> (sindresorhus/awesome#1282)
> <https://github.com/sindresorhus/awesome/issues/1282#issuecomment-2700636398>
>
> 1
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/sindresorhus/awesome/issues/1282#issuecomment-2700636398>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A7TCOKL4HZNOGMOIQND4IVL2S3OHTAVCNFSM6AAAAABYL25TNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDOMBQGYZTMMZZHA>
> .
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
@Angel-Mathew007 commented on GitHub (Sep 4, 2025):
Hi everyone,
I find this discussion about including non-English resources very interesting and important for making the lists more inclusive. I’d love to help contribute to improving how non-English resources are added or organized.
Could someone guide me on how to get started with this? Is there an existing guideline or format I should follow when adding such resources?
Thanks!
<!-- gh-comment-id:3252625847 -->
@Angel-Mathew007 commented on GitHub (Sep 4, 2025):
Hi everyone,
I find this discussion about including non-English resources very interesting and important for making the lists more inclusive. I’d love to help contribute to improving how non-English resources are added or organized.
Could someone guide me on how to get started with this? Is there an existing guideline or format I should follow when adding such resources?
Thanks!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ramnes on GitHub (Apr 30, 2018).
Original GitHub issue: https://github.com/sindresorhus/awesome/issues/1282
Please see this issue on Awesome MongoDB: https://github.com/ramnes/awesome-mongodb/issues/43
By reading #153 and #1176, I seem to understand that all the non-English resources are supposed to go in separated lists, rather than being regrouped under the main theme list, even if they're not translations but really add to the list.
Can't we do better and be more inclusive to non-English speakers? For example, by adding a country flag in front of all resources, indicating the language of the resource?
@sindresorhus commented on GitHub (Apr 30, 2018):
I don't think it makes sense to mix languages in the main readme. That just creates a messy experience for everyone.
Instead, make the main readme.md have only English content, then at the top of that readme, add links to other languages which can be in their own Markdown files.
For example:
When we've decided on a good format, we should document it here.
@zhaoyi0113 commented on GitHub (Apr 30, 2018):
The idea on below format makes sense for translating into multiple languages. But what we want to is to bring articles written natively by other languages instead of translation.
@sindresorhus commented on GitHub (May 1, 2018):
@zhaoyi0113 That's what I'm talking about too.
@ramnes commented on GitHub (May 2, 2018):
I feel that the different README files structure would be interesting if there would be a lot of resources in the different languages. But most of the time that's just not the case. There's maybe 95% of the resources available in English, since English is still prominent in computer sciences, and 5% of very specific stuff not already covered by the 95% and written in some other other language.
In the age of evolved translators like DeepL, I don't see any reason to not add an article written in another language if it really adds to the list. Non-English articles could be enforced to have at least one translation, with a guideline on how to format translations.
For example, something in those lines would make sense to me:
I think such a format would also be very useful for local lists, non related to computer science, where the main language might be something else than English and with resources in different languages.
What do you think @sindresorhus?
@sindresorhus commented on GitHub (May 15, 2018):
I have yet to see a technical paper in Chinese being readable after running it through Google Translate, but I don't see why not if it's still good after being translated.
Since the list is in English, the main link should point to the translated version. The original can be linked to in parens, like (Source).
@ramnes commented on GitHub (May 15, 2018):
Yep, and it has the advantage of forcing a proper translation in the list's main language as the main link. I definitely support that solution.
@Kreijstal commented on GitHub (Jan 24, 2019):
Well that's the problem with other languages there is just not that much stuff into them
@jirayutza1 commented on GitHub (Dec 3, 2019):
Duplicate of #1664
@touxiongjihua commented on GitHub (Mar 5, 2025):
1
@Tester1234537 commented on GitHub (Mar 5, 2025):
What is the problen con the spanish
El mié, 5 mar 2025, 6:33 a. m., 偷熊计划 @.***> escribió:
@Angel-Mathew007 commented on GitHub (Sep 4, 2025):
Hi everyone,
I find this discussion about including non-English resources very interesting and important for making the lists more inclusive. I’d love to help contribute to improving how non-English resources are added or organized.
Could someone guide me on how to get started with this? Is there an existing guideline or format I should follow when adding such resources?
Thanks!
@5npyrh9kvj-sms commented on GitHub (Apr 15, 2026):
@Ke639 commented on GitHub (May 7, 2026):
Line