Starting with version 50 MKVToolNix has almost full support for BCP 47 language tags. It is expected that existing programs & devices will take quite some time before they support the new elements. Otherwise the only existing element is used. '…Language' exist at the same level, the new '…LanguageIETF' element must be used. The rules for using those new elements in Matroska are simple: if both a new '…LanguageIETF' element and the corresponding old plain Standardized and only have meaning to a select number of people. One can even use custom private extensions that aren't There are several more possible additions that describe rarer variants of languages. Language is written in a specific script (in this case: Serbian as spoken Serbia, written in Cyrillic instead of Latin) sr-Cyrl-RS - an ISO 15924 script code might be used as well for specifying that a.pt-BR - an ISO 3166 country code might be used, too, for specifying the language spoken in a specific region or country (in this case:.de - the simplest form consists solely of an ISO 639-1 or 639-2 language code (in this case: German).So how might those elements look? Here are a couple of examples: Knowledgeable people and that the same standard is widely used in other projects, protocols and products. The advantages of using an existing standard, especially a Best Common Practice, is that we can build on the work of a lot of very smart and Syntax laid out in the IETF's Best Common Practice 47 (referred to as 'BCP 47' in this article) which (for track headers), 'ChapLanguageIETF' (for chapter languages) and 'TagLanguageIETF' (for tag languages). In 2019 the IETF's CELLAR working group (which the Matroska project is a part of) has extended the format specifications with three newĮlements that allow storing a much more descriptive language tag for tracks, chapters and tags. The whole of MKVToolNix has never had support for those optional country codes, though.

por for Portuguese) with an optional country code following Languages in Matroska and MKVToolNix Backgroundįor a long time the Matroska file format has only supported track/chapter/tag languages in the form of ISO 639-2Ĭodes (e.g.

How to use mkvtoolnix gui