Unfortunately doesn't work yet

[yurtpage]

For those who are looking, the GitHub won't automatically show a README in a user's browser language.
Also this is not specified anywhere. Different projects use different layout README.pr-BR.md (seems most reasonable), README-pr-BR.md, README-pr_BR.md or even README-PTBR.md.

[jonatasemidio]

Hi @yurtpage ,

Thanks for your contribution.
Could you give me more details why do you think that is this not working for you?
I'm asking this because the goal of this repo is to show an approach to have a multilanguage documentation using the markdown and not exactly the browser translator.

Basically, we add a link on the default README.md to the translated version... and the idea of using this naming pattern is to follow the IETF BCP 47 standard. These codes are commonly used in software localization, web development, and other contexts where language and regional variations are important.

Following this pattern, we can have a language-agnostic approach.

That's why I do not think that this is a real issue, considering that the focus is not being automatically translated for browsers.

PS: Using this IETF BCP 47 standard, maybe in the future, someone can create a tool or browser extension that works on top of it.
Maybe this could be a really cool contribution.

Just let me know what you think.

[yurtpage]

Sorry, I googled How to make GitHub to show README in a user's language and found you repo. At first I was thinking that it must work, I just have to switch language codes. But it didn't so I decided to leave the comment for those who may look too.

There is a GitHub discussion on this github/markup#899

[jonatasemidio]

Hey Bro, Don't be sorry, You did it right.

I was just checking if you got the idea behind this repo.
I totally agree with you, having something to auto-translate our docs, would be really useful (considering AI, I think we are basically there already).

And again, I think we can use this pattern to create a chrome extention... You can check the discussion in this pull request for more: #2

And just to confirm... Is it ok for you to close this issue? Or you want to discuss something more?