The Movie Database Support
Support → General
My language doesn't exist on this site :s
posted by PJ_007STAFFMOD on September 25, 2012 at 9:37 AM
Hello,
When I browse and search for my native language, which is Vlaams (Flemish), I can't seem to find it... It's closely related to Dutch, but we have our own dubs for movies and sometimes other titles as well :p Flemish is related to Dutch as Walloon is related to French and yet Walloon exists on this site and Flemish doesn't :D Can someone add it as a language? Thanks in advance :D
Greets
Reply by Travis Bell
on September 29, 2012 at 2:43 PM
Hi there,
At this time our site adheres to the standards of the ISO 639-1 codes and Vlaams is currently associated with
nl. Adding a new language is something we could look at I'm not making any guarantees. I have however created a ticket for this which you can view here:http://tmdb.lighthouseapp.com/projects/83076-website/tickets/315-add-a-new-language-vlaams
Reply by roland684
on June 5, 2014 at 11:23 AM
The IETF language codes would support many more languages and dialects, can be used to extend the current database (the prefix of the IETF code is ISO 639-1), has nice fallbacks for unavailable languages built in, and is a mechanism used by the http protocol - the standard of the www.
In the language code 'nl' is a fallback for when 'nl-be' is not available. HTTP's accept_language header has even more fallbacks, e.g "en-au,nl;q=0.8,de;q=0.5"
You can even use it to determine the date/time format, use of the metric or imperial system, etc.
Why not incorporate that existing and proven standard for content localization? It is also odd (if not incorrect) for a REST API to have a language parameter in the payload while ignoring the accept_language property of the header.
Reply by Travis Bell
on June 5, 2014 at 11:39 AM
Eventually this will be how everything works but the db is not currently designed with these standards and it would be near impossible to implement without breaking v3 meaning, at some point should the work on a v4 start, these are the sorts of things we would make sure to implement properly.
Until then (which is to say a long ways a way, if ever) we have to deal with the current ISO-639-1 implementation.