oood

> Great 👍 Not sure if it can be considered as the final solution, since a single color hand lacks inclusivity. that's why I prefer to use a simple text...

> Thank you for bringing up these points. I think 🟢, 🟡 and 🔴 are very intuitive for ~95% of people. So I think we should keep these in some...

So, I think we don't really need to care too much about the color of the circle, we just need to create a raw database, then maintain the database, and...

> I am happy to switch red to purple, if it increases readability for the last 5% of humans. It is also a nice purple and maybe even less of...

> Do you mean having separate files for each language Of course, each language needs to have separate files ( `README_ja-JP.md`, `README_it-IT.md`, `README_pt-BR.md` ), otherwise that would be messy.

> However, we needed determined contributors for each languages else the translations will be out of sync easily. When we start a new language, it is assumed that the first...

> We should also have lime an index file only having the langauges we provide. > > ``` > [ > "sp", > "it" > and so on > ]...

As this project grows, I'm not sure if a readme file can be as long as a dictionary. Maybe alphabetically? ```` abbreviations-in-code ├─── readme.md ├─── en-US | ├─── A.md |...

> I assure you that sorting them by abbr was a mess. > I just wanted to comment the same 🙂 OK, I get it. because words are unique, abbreviations...

> Maybe we should store the abbreviations in a yaml/json file like: Is it possible to create separate json for each language? Because, I think it will be complicated to...