Closed kristian-clausal closed 4 days ago
More Greek language data are added in v0.2.11 release, but if you already have both language name and code then you don't need this library...
I was using the code -> Greek name as a way to check if the heading is correct, if the code and name match.
Seems unnecessary? In el edition, language code is the language template name or in template arg, and language name can be obtained from expanded template.
I think this issue could be considered resolved? Most languages in el edition should be added.
Yeah, it turned out to be unnecessary at the time.
No wait, I forgot why I posted this in the first place: It's weird that Yucatan Mayan gets the Swedish name "yukatansk maya", it's weird that other languages get Chinese names. This could be a little more consistent, the algorithm for picking what language to return seems weird.
code_to_name
could return language name in other language if it can't find the name in requested language. I think it is implemented in this way to mimic some Mediawiki Lua APIs. Usually it's not a problem in extractor code, especially if data extracted from an edition are added.
If it's emulating some precedent, I guess that's good.
This is some of my own debug print output:
So `code_to_name("tsd", "el") returns "tsakoniu".
I've left out anything with any kind of Greek language output, just the gaps.
Other occurrences, mostly less well-known languages that obviously just have gaps in the data:
Just putting these here because of the output names being in sometimes weird languages, like the random Chinese and "yukatansk maya" in Swedish.