The field contain all of these, some of which have multiple instances of, instead of what is valid.
GER
Japan
English
Sweden
eng
France
Taiwanese
ger
Français
Swedish, German
Russian, English
Ukrainian, English
Canada
Spanish
cze
Chinese
汉语
Tulu
engli
Greenlandic
Eng
Englis
English
japne
Italianit
Español
port
Engl
Burmese
engl
Spanish, aymara
None
Czech
Bahasa Indonesia
Portugal
Italia
fre
sinhala
普通话
Can't find a movie or TV show? Login to create it.
Want to rate or add this item to a list?
Not a member?
Reply by Adi
on June 7, 2018 at 12:02 PM
This does raise a bigger issue though. e.g. ISO_639-1 only relates to written languages, rather than spoken.
e.g. Chinese isn't a spoken language. You have Cantonese, Mandarin etc. which is what the film will be spoken in.
At the language company I used to work for, we tended to go for language and country. e.g. en-US, en-GB, zh-HK etc.
That said, it isn't ideal.
About the best I have found in terms of a list is: http://www.unicode.org/cldr/charts/latest/supplemental/territory_language_information.html
It has codes for things like Tulu, Taiwanese, Cantonese etc.
It is one of those things where there isn't really a perfect solution, but I think the issue that ISO 639-1 presents in terms of Cantonese/Mandarin is worth thinking about. All of the 639 variants have issues.
Reply by Adi
on June 7, 2018 at 2:28 PM
Renegade known entries are (No issue with the first two. Not sure about the second two):
There just seem wrong:
Reply by Adi
on July 6, 2018 at 7:26 PM
Created this a month ago, but I just want to check something.
@Travis
Is the validation of Release Dates ISO_639_1 working as intended?
Is it just a case where it was missing validation for a while? It is now correct and it just needs some rogue data sorted out?
The reason I ask, is because in all other areas where ISO_639_1 is a field, the field size is 2. e.g. although not ISO compliant, it is at least compliant with intended exceptions.
The only place it isn't compliant with intended exceptions, is under the new format for Release Dates.
Reply by Adi
on July 11, 2018 at 3:01 PM
Bumping this to raise awareness.
Reply by Travis Bell
on July 12, 2018 at 12:33 PM
Hey Adi,
There is no validation on the ISO-639-1 field of release dates. I'll have to get that added. I've created a ticket for it here and will see when I can find some time for it.
Reply by Adi
on July 12, 2018 at 12:39 PM
Cool. Just seemed odd that that was the only one of that field type to have the issue.