Hi Joe,

Browsing Language: Acts as a translation "only" filter to search/list as set by the API language parameter. If one sets this to blank/null all language translations are considered?

Are you referring to the use the language param on the API in this case? If so, yes, it is only for the actual translation of items. It acts as a filter. We do not fall back to any language. The title field is unique in that it will fallback to the original_title field. This is a leftover from the days before we had the original_language field. Since it's tied to the original_title field and without it before, there was no way to know what (if anything) was being returned. Obviously the introduction of the original language changed this but we haven't added original_language to search and discover results, nor made it a filter yet.

Movie Original Language The language in which the movie as produced/primarily released and as so would likely be, but not necessary, one of the spoken languages?

Correct. It would usually be, but not always the language of the original_title.

BTW, if I have the Browsing Language (and more than one available) set to English and try to set the Original Language to say French or some language other than English I get an error. So what does a movie's Original Language got to do with a browsing language?

It doesn't have anything to do with it as it is not currently a valid filter. We don't support filtering based on original_language right now, did you see this somewhere in the docs?

Spoken Languages: Those languages actually spoken in the movie and most likely one of these would be the Original Language?

Right.

Not Considered: Languages in which dubbing and/or sub titles are available.

Correct, we don't have any information about dubbing at all. There's a whole subset of features related to this like separate casts that we are not prepared to work on.

Hi Travis

Thanks for the reply!

Ok, so:

I understand that the API language parameter is the translation filter and only that.

Just to be sure - Can I assume that if I change the Original Language through the web forms to that of production or release it could affect your fallback for title in the future? Apart from how the API uses this item it has become key to my app for searching by language and may also by others wishing to filter in or out movies by various languages. I have not excluded spoken languages in my app's searches BTW but these do not agree yet with the original language in numerous API records. I have been working on this if you review my web changes to original languages over the past two days. I have only changed those movies where the original language is not ambiguous. I.e. The Original Language was "English" and the only Spoken language was "Spanish", the production/release was Spanish, and/or cast was clearly Spanish. I also verify by other sources (IMDB, Wiki, etc.) btw.

The "browsing Language" to which I refer is that which appears in the edit form(s) . It is definitely affecting changing the "Original Language" as I described above. An error appears on the web form when this happens. It looks as if the title/form validation is tied to the Original Language selection. I would think the latter would not be, regardless for the translation selection. I do understand that the original language should/could change to the translation language "script" if the translation selection changes (or does it? Haven't try this yet.) I don't know what "English" looks like in Arabic but it would likely involve some squiggles.

I have, since this post started, also found movies on the web edit interface which have duplicate translation languages in the combo box. In some cases the same language appears several times. Might this be because there are multiple translations for the same language or has an error has occurred? If you'd like I can post you a culprit next time I hit one.

As to the last item - Yah, who would wish to open that can of worms!!

New: I was attempting to fix a Original Language via the movie web edit form and found that the entry was likely wrong but has been "locked". Can I assume this can only be unlocked by the locking user or by admin? If so, how do we fix blatant errors or omissions? Tricky I know, but all the same I had 25 years in IT and know to do the research before possibly damaging a record. Of course most contributors would simply guess and likely guess wrong. Is there a hidden admin/supervisor level setting on web accounts which one may request to override these locks. Your thoughts and comments on this would be appreciated.

Much thx; Joe