quote: Matt Smith

---

With partially dutch subtitles (Dutch subs when French is spoken)
MovieTitle_FTR-1_S-239_FR-nl_BE_51_2K_20170601_FRI_IOP_OV

With dutch subtitles (Dutch subs for both languages)
MovieTitle_FTR-1_S-239_FR-NL_BE_51_2K_20170601_FRI_IOP_OV

---

quote: Carsten Kurz

---

If your projectionists understand what is meant, mission accomplished.

---

quote: Jim Cassedy

---

It turns out the shipping info, the CPL info printed on the drive and even the CPL info on the drive itself when I ingested it was just plain WRONG.

---

If the movie came from an Italian facility, I'd say you were lucky it played out at all.
With very few exceptions, I believe the only English world that can effectively describe what we experience here every week is "sh*tshow". Local distributors are only looking for the cheapest encode, and that's the inevitable result.
 

---

Posted by Marcel Birgelen (Member # 6801) on 06-28-2017, 04:29 AM:
 
Can't your Belgians not just settle on one language and be done with it? All those exceptions make our software bulky and buggy.

Since the spoken Dutch is most likely Flemish and not "Standard Dutch", I'd say VLS would be better than NL as a language indicator. Afaik, there is no special distinction for the Walloon dialect (yet), so it's probably best to keep it at FR.

There is no territory code for Flanders (yet) and since the release seems to be targeted at the entire Belgian market, territory would probably be best represented with "BE".

So, that would yield the following:

Without subs:
VLSFR-XX_BE

With Flemish and Walloon subs:
VLSFR-VLSFR_BE

With only Flemish subs:
VLSFR-VLS_BE

I think if this would make the official DCP naming conventions, there sould be some kind of separator between the individual languages. The reason for this is to keep the filenames machine-parseable, so you want to avoid the possibility of ambiguity, which could occur since language indicators can contain 2 or 3 characters. Another possibility would be, to pad language codes with an extra letter like X, if they consist of only 2 characters.
 

---

Posted by Marcel Birgelen (Member # 6801) on 06-28-2017, 06:13 AM:
 
It seems I misread your initial post and the two subtitle files you have are both in Dutch/Flemish, where one is just the partial translation and the other the full translation. It was a long night.

There is indeed also nothing in the current naming convention to take care of those edge cases. My gut feeling would say you should encode this in the "Title", because that's the most free-form field in the current naming convention, but then again, the title is not supposed to be longer than 14 characters and given the long titles of many movies, is already a pretty cramped field.

I think I would opt for a solution as follows:

Without subs:
VLSFR-XX_BE

With Partial Flemish subs:
VLSFR-VLSPart_BE

With Full Flemish subs:
VLSFR-VLS_BE

At least this way, two of the three names would be closer to the naming convention. I don't think you would need a special modifier for "Full" subs, since subtitles are usually expected to cover the entire feature.

Also, to make it into the naming convention, you would need a way to separate the "modifier" part from the Language code, to keep it both Human Readable, but also easily machine parseable.

In any way you should obviously provide a note to explain the difference between the versions.
 

---