Closed LornaSIL closed 3 months ago
Is this an issue to upstream to langtags.json?
Is this an issue to upstream to langtags.json?
I don't know if langtags changed the default or not. Since it was updated recently it's possible the version in Keyman is out of date? Not sure.
Is this an issue to upstream to langtags.json?
I don't know if langtags changed the default or not. Since it was updated recently it's possible the version in Keyman is out of date? Not sure.
Turns out this is data in node v20. So it's coming from CLDR. @srl295, any thoughts?
$ node -e "console.log(new Intl.Locale('mww-Hmnp').minimize().toString())"
mww
$ node --version
v20.14.0
And Chrome 125.0.6422.142:
> console.log(new Intl.Locale('mww-Hmnp').minimize().toString())
'mww'
Is this an issue to upstream to langtags.json?
I don't know if langtags changed the default or not. Since it was updated recently it's possible the version in Keyman is out of date? Not sure.
Turns out this is data in node v20. So it's coming from CLDR. @srl295, any thoughts?
$ node -e "console.log(new Intl.Locale('mww-Hmnp').minimize().toString())" mww $ node --version v20.14.0
And Chrome 125.0.6422.142:
> console.log(new Intl.Locale('mww-Hmnp').minimize().toString()) 'mww'
That is the default upstream, yes, as there is a locale in that language and script
Although the message for the language tag
mww-Hmnp
says it should bemww
, it is incorrect.mww
is forLatn
.