Tiziano

> - Use text to explain how recommended an abbreviation is, or other emojis 👍/👌/👎. Great 👍

> Thank you for bringing up these points. I think :green_circle:, :yellow_circle: and :red_circle: are very intuitive for ~95% of people. So I think we should keep these in some...

I agree with @kisvegabor using json generating the READMEs would be easier to maintain and in the same time we will fix the JSON problem to create the website.

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

> BTW, our sorting should be based on abbreviations rather than words themselves, because an abbreviation may correspond to many words, and putting them together is helpful for retrieval. Nop....

En README. ` • _word_ • _recommendation degree_ [_abbr_](link to discussion) { _context if context-sensitive_ }` Sorted by word. Any other lang README. ` • (translation) _word_ • _recommendation degree_...

Realized that we can also use ``` [ "sp", "it" and so on ] ``` to create an index README with the available langs. So if someone is searching for...

> ``` > # software > - issue: 123 > - translations > - zh: ... > - ja: ... > - abbreviations > - recommended: sw > - context...

I don't see it as yaml but text. JSON needs {}, [] and "" to be valid and after a bit your eyes go on vacation not considering the space...

Talking about script and conversions in which lang we should write scripts. We need a lang that run run locally to generate files. Previously the script was written in Perl...