Just wanted to just add a bit to what SmallBrother stated:
First of all, I straight out hate those {\an8} and similar alignment codes.
Why:
- First of all, it's just not compatible. It's an ASS/SSA code. It's a violation of the SRT file format. It may or may not work, depending on the player, but regardless, it's a syntax error. Period.
For heaven's sake, they are called SUBtitles, not supertitles.
For .srt format I totally agree.
The ASS/SSA format allows many more options in how subtitles are created and displayed, and can utilize various “design intents”, but which limitations in .srt format cannot.
Examples from various retail studio releases such as PSDH vob/sub (Universal) or AlphSub CC (WB), typically use positionally based subtitles.
In PSDH or placed captions, text is not fixed position {\an2} as is the majority of subtitles that we review that are submitted in .srt format. Instead, they float and track the characters’ speech. Certain typical guidelines as to lines and characters do not apply, due to the various X locales.
However, a heads up. Many users extract, edit, and modify source, then run though a conversion from ASS/SSA to .srt. This can introduce many errors depending on the method and/or software utilized. A few examples of potential issues:
Example 1: Multiple speaker ID/designations. Positional references track text dialogue to speaker with ASS/SSA, while .srt converted format may or may not carry over the AN tag. Additionally, even if recognized by the player as SmallBrother pointed out, the .srt format is still geographically limited.
The converted file if {\an2} justified, would then require additional post corrections, such as examples referred to in BBC Section 7 Speaker Identification.
Example 2: Space utilization and excessive lines. Positional references can also allow for simultaneous dialogue exchange within the same time reference.
However, a two character exchange with two (possibly three) lines each, could conceivably after a .srt conversion, result in a four to six line {\an2} justified subtitle, without any speaker designation/change. (Have seen this occur)
Then, we many times come across the detritus carry over from conversions such as place holders and whatnot, depending upon which software is utilized.
Just a heads up to our contributors when working with subtitles editing and converting. Whatever format that you prefer working in, just practice a bit of due diligence.
many modern streaming services now use those alignment codes. For me it is totally fine to block uploads containing positioning codes, but it is definitely *NOT* an indication of a machine translation. If anything, it's an indication of uploaders just blindly copying the 'standards' of Netflix & Bros, thinking it's good or normal.
