Language codes made up off the top of someone's head are my peeve. If anyone else wanted to support Kansai dialect, they wouldn't necessarily (and probably shouldn't) make the same decision to pretend that it's a country with code KS.
It's not like the standards left them with anything to work with, but "ja-x-kansai" would have been quite acceptable.
At least it's not as bad as code I've seen that used "zh-SC" and "zh-TC" to represent Simplified vs. Traditional Chinese, because they either didn't know about "zh-Hans" vs. "zh-Hant", or didn't leave room for script codes in their database. (In my post I neglected to even mention Chinese, by far the largest example of a two-script language.) If you read the codes "zh-SC" and "zh-TC" literally, they're distinguishing whether it's "Chinese as used in Seychelles" or "Chinese as used in the Turks and Caicos Islands".
And it's not as bad as the OpenSubtitles language code "ze", which after some examination, I have to conclude means "this might be Chinese or might be English, we're not sure, we found it on a shoddily pirated DVD".
It's not like the standards left them with anything to work with, but "ja-x-kansai" would have been quite acceptable.
At least it's not as bad as code I've seen that used "zh-SC" and "zh-TC" to represent Simplified vs. Traditional Chinese, because they either didn't know about "zh-Hans" vs. "zh-Hant", or didn't leave room for script codes in their database. (In my post I neglected to even mention Chinese, by far the largest example of a two-script language.) If you read the codes "zh-SC" and "zh-TC" literally, they're distinguishing whether it's "Chinese as used in Seychelles" or "Chinese as used in the Turks and Caicos Islands".
And it's not as bad as the OpenSubtitles language code "ze", which after some examination, I have to conclude means "this might be Chinese or might be English, we're not sure, we found it on a shoddily pirated DVD".