Closed bwbroersma closed 1 year ago
Would you please elaborate on the issue? Currently, no case-sensitive check is done and therefore no recommendation is given.
Conforms to RFC 5646 "At all times, language tags and their subtags, including private use and extensions, are to be treated as case insensitive: there exist conventions for the capitalization of some of the subtags, but these MUST NOT be taken to carry meaning."
We have seen the recommendation in the RFC, but it also seems to contradict itself (nl (1rd) is allowed but NL (3rd) is also allowed). Furthermore, it does not help with readability for a researcher or affect parsing. For now, our opinion is that it is maybe not 100% correct, but an out-of-scope warning for this parser/validator.
Add case recommendations of RFC 5646 - section 2.1.1 Formatting of Language Tags.
:warning: Warning:
:heavy_check_mark: Ok: