-
-
Notifications
You must be signed in to change notification settings - Fork 228
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
2020-12-16: Order of Languages in homepage #259
Comments
The order of languages on the homepage is not ever sorted. It is determined entirely by the order of the entries in I gather that the number of languages that exist in this project has grown fairly quickly. Before it gets out-of-hand, we should consider whether it makes sense to have a home page that lists all of the languages and their respective blurbs in some order, or:
|
I understand that, I'm suggesting to decide on a consistent order to manually change it (as it only needs to be done once) and make sure that new languages are added correctly. The problem seems to be non-Latin writing systems as it's not clear where to sort them. Of course if either of your suggested solutions are implemented this would be no longer relevant. They're both good ideas but I actually like the home page giving an overview of how many languages are supported as it is. |
Fixed in #260 |
Regarding the order of the entries (#254), the languages on the homepage may need to be changed for consistency (this is done manually as I understand it).
In PR #129 I added Japanese but it is under Portuguese by mistake (not sure if this was changed around the same time and merged awkwardly).
https://github.com/carpentries/glosario/blob/3ddacca7561222220af08c910b10b1a7981c1635/_config.yml#L114_L127
I wasn't sure whether to sort alphabetically by roman letters (e.g.
de, en, fr, it, ja, nl, pt
) or use romansied names 日本語(Nihongo) as discussed here or sort by language name in endonyms as done here with other alphabets, abjad, and CJK characters at the end:So either we sort Japanese as "ja", "nihongo", or put it at the end as a special character (in which case Arabic would be moved as well).
The text was updated successfully, but these errors were encountered: