README.md with multi language support?

[jinliming2]

Sometimes I need to display documents in different languages for different people.
Maybe we can use README.en.md, README.zh.md, README.zh_hans.md, etc to markup language of the document, and determine the display language for users according to browser language.

[jagd]

is it solved?

[jinliming2]

May not.
I had a wrong operation.

[SlyAceZeta]

I'm surprised that this isn't available. Definitely adding my +1 for supporting this.

[Nightenom]

Someone got something new about this needed future?

[kesarion]

A workaround would be to put the links to other languages in your default README.md, like in this example.

[jinliming2]

@kesarion This is a method to solve this problem, but not the best.

[jinliming2]

@github

[pidupuis]

@github

[cubesky]

@github

[fnky]

I propose to name README using language culture name, e.g. README.zh-CN.md, README.es-ES.md as languages can have cultural differences—like en-US and en-GB.

[BMaxV]

Might not be a bad idea to use the iso standard.

[jinliming2]

I think using language culture name is not a good idea for Chinese because even in mainland China there are many language branches, such as Mandarin, Cantonese, Hakka, Xiang, etc. The vast majority of Chinese people are hard to understand more than one language. Just using zh-CN can not distinguish between these languages.
So I think we'd better use this rule: https://www.w3.org/International/articles/language-tags/, with the Language Subtag from IANA: https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry.
But many browsers do not support these language categories, so it is necessary to keep zh. So, for Chinese:
Use zh-Hans for General Simplified Chinese, use zh-Hant for General Traditional Chinese, use zh-cmn-Hans for Mandarin with simplified words, use zh-yue-Hant for Cantonese with traditional words, and so on.

[jonasgeiler]

@github

[djbrown]

Duplicate of #581 @kivikakk 👀

[alvarotrigo]

Interested in it too!

[0xtoorich]

Currently, I use README.md, README.zh-Hans.md, README.zh-Hant.md, README.fr.md, etc.

[Nadaabdulsalam]

.

[reggermont]

Would be very great @github

[filipecavalc]

still waiting, is something I would really like to see.

[rain1024]

Would be nice feature @github

[neontorrent]

I would like this feature as well

[ciricc]

And is it not added for now?

[NanoPish]

I would like this feature as well

[afourmeaux]

That would be a gread feature for the readme !

[PyvesB]

Indeed, READMEs with multi language support would be a very useful feature, hope to see it sometime soon!

In the meantime, I use a single README where each paragraph has its translations one under the other with slightly different styles, for instance one language in italic. A country flag is inserted at the start of each paragraph translation, which makes the README more visually appealing and easier to navigate through. It's not perfect, but it's a decent enough workaround for my purposes. You can see things in action in this repository.

[fnky]

@PyvesB An issue I can see with this is for people who use screen readers, which will read everything in all languages. Another is if you'd like to expand on supporting more languages it will result in a quite heavy README which makes it hard to find and understand the information.

With different README files based on language you can provide a README which doesn't conflict with other languages and make it easier for users (with screen readers too) to understand and parse the information.

[alvarotrigo]

With different README files based on language you can provide a README which doesn't conflict with other languages and make it easier for users (with screen readers too) to understand and parse the information.

Yeap, that's what I'm doing on my project.
Opted to use a lang folder where I place the different languages Readme or extra files.

And then I added a menu to choose the language on the top.

[fnky]

@alvarotrigo This reminds me what could be possible with the wiki.

Being able to provide a wiki in multiple languages using something like repo.wiki/lang (using the root wiki repo as a default and /lang for overriding different pages in other languages).

[LucasKuhn]

+1 for the example given here, it is easy to follow and the file to be served could be detected based on the location of the user

[reggermont]

The thread is closed to be 3 years old and not a single message from dev team :/

[Malavos]

+1 folks, where is it!

[qct]

+1

[CreatiCoding]

Hello, Is it possible that github repo recognizes browser's language and links to read file in that language❓

😄 I just wanna doing this process automatically.

[MicroDroid]

And now, it's time for:

🔒 This conversation has been locked to contributors only

[kivikakk]

This repository is for the github-markup gem, a library which GitHub.com uses to choose a markup processor based on the type of the input data. All questions not related specifically to this gem should go to our support team. (Put another way: if a PR to this repo can't fix it, it doesn't belong here.)

I understand this is something that people want, but opening an issue here won't make that happen. People who work on the code that pertains to your query do not, in general, watch this repository. (I do because I maintain this gem.) To get it in front of their eyes, you'll need to go contact support so they can triage and prioritise it along with other requests.

Thanks for your understanding.