![]() ![]() On the one hand "jap" is used in reality so supporting it is practical. how to auto-select reliably between simplified Chinese & traditional Chinese). I'll do some more tests anyway, and tell you guys if I find any possible problems/improvements related to auto track-selection in general (e.g. Therefore, recent changes may be removed in the future. In any case, the double option always works: "jap jpn". will only work for containers in which there is a language code. If, for some good reason that I don't know, BE doesn't want to support the standard code "jpn" supported by MPC-HC, I'll respect your choice. On the other hand, I've been multisubbing for about 20 years since before MKV was born, and in my experience, decent MKV files (perhaps > 90%) always have "jpn" for Japanese, at least in the anime fandom - partly because it was/is in the predefined list box of MMG/MKVToolnix GUI. You're right, I don't know the historical reasons behind this. "rus" or "jpn" instead of "und"), that gives us a simple way to detect the language, more reliable than parsing the track name (which might be something like "ASS" or "Styled"). If MKV is created properly, each track has a standard language code. I understand that supporting non-standard language codes is helpful. MPC-HC does support "jpn" in the same edit box and it can auto-select a "jpn" track from MKV, which seems more intuitive. Imho supporting both "jpn" and "jap" similarly/transparently would be more convenient for everyone, not complicating anything. In general, your proposal can only complicate everything, we will leave everything as it is. In many MKVs, the track language is recorded with a name, not a code. In external srt, mp3 files there is also no code for the language. ![]() There is no code for the track language in the AVI files, not at all. You do not seem to know the history of this option. Not to be picky, just so you know there could be potential problems. However, the official code for Japanese is jpn, and "jap" is generally considered as a racial slur in Japan for historical reasons, quite a few people feeling uncomfortable or offended to see it.Īlso practically, the first-three-letter scheme could be bad for example Malay vs. I know these examples are innocent, simply the first 3 letters of the language names, and they're practically fine and easier to understand for most people (so I guess it's fine they are supported). Speaking of which, I've always wanted to say, please support the standard ISO language codes, instead of "Example: eng jap swe". ![]() When I play a movie with a non english audio track listed as (01) it always plays this instead of the default i've set, i've tried both "eng" and "english", just doesnt work. Ive mentioned this before but there have been a few new version since but it still hasnt been fixed, or i'm doing something wrong. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |