mkvmerge: IETF BCP 47/RFC 5646 language tags: if present the "LanguageIETF" track header element will be reported as the language_ietf property in JSON identification mode.If the language tag contains a valid ISO 639-2 language code it will also set the legacy "Language" track header element to the included ISO 639-2 code. mkvmerge will always write "LanguageIETF" track header elements. mkvmerge: IETF BCP 47/RFC 5646 language tags: mkvmerge will now accept full BCP 47 language tags for all options taking a language.
I’ve written up a nice FAQ entry about the switch to using IETF BCP 47 language tags, how they interact with legacy language elements, how the programs actually behave and how to disable their use if necessary.Here are the NEWS since the previous release: New feature: IETF BCP 47 language tags The other Linux binaries are stil being built and will be available over the course of the next couple of hours. The Windows and macOS binaries as well as the Linux AppImage are available already. You can download the source code or one of the binaries. Important news for package managers is that the PCRE2 library is now required (only its UTF-8 variant). Finally you can express things such as “Portuguese as spoken in Brazil” or “Serbian in Cyrillic script as spoken in Serbia”.Īpart from that there are the usual enhancements & bug fixes. This one includes quite a high number of commits under the hood due to the prominent new feature I’ve implemented: support for the new IETF BCP 47 language elements. Another month, another MKVToolNix release.
0 kommentar(er)
