Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-language support? #40

Open
joho opened this issue Oct 29, 2019 · 2 comments
Open

Multi-language support? #40

joho opened this issue Oct 29, 2019 · 2 comments

Comments

@joho
Copy link
Owner

joho commented Oct 29, 2019

Right now we've got two open PRs for non-english readers:

  • Spanish translation #39 adds a spanish translation of the readme including titles and descriptions but linking to the original english works
  • Portuguese Content #35 adds a section for podcasts in portuguese within the existing readme

I'll do a bit of research into what's "best practice" for multilingual awesome lists before merging or rejecting either of the PRs.

Absent any research i'm inclined to keep the main list in english, but maybe have alternative language files that link to language specific content (ie. readme.es.md is written in spanish and links to spanish language content) and possibly appoint per lang maintainers as I can't judge the quality of the content myself.

If anyone has alternative ideas please share them in this thread.

@ybiquitous
Copy link
Contributor

I think it's a very nice idea! I can be a Japanese maintainer if no one will. 😃

@mgreiler
Copy link
Contributor

Resources in different languages would be very valuable, as language can be a real barrier for non-native speakers. To keep the list clean and digestible, I also think that separated files make sense.
I read through the original awesome list contribution guides but could not find any information on how to handle different languages. Researching a few popular awesome lists also did not reveal how others are doing that - rather it seems they don't support different languages.
Assessing the content seems a problem, as you said. I like the solution with dedicated language maintainers, but what if there is no maintainer?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants