... | ... | @@ -121,4 +121,33 @@ Matroska file that contains them. Here's how to do that: |
|
|
* For MKVToolNix GUI's header editor you can simply select each "Language (IETF BCP 47)" element and check the "remove element" checkbox if
|
|
|
the element is currently present in the file.
|
|
|
|
|
|
|
|
|
## The old user interface is not coming back
|
|
|
|
|
|
Compared to the old user interface the new one requires a two more mouse clicks to change the language tag (opening the dialog & clicking
|
|
|
"OK"). A small number of users object to this change. While I truly understand that only two clicks can amount to a lot of extra work when
|
|
|
handling large number of files, the old interface is not coming back. Other wishes such as "simply have show the old language combo box with
|
|
|
the new edit button" don't have much merit considering what the new interface achieves. Here are the requirements I had beofre I implemented
|
|
|
the new UI:
|
|
|
|
|
|
1. The user should be able to use the full feature-set that BCP 47 language tags offer.
|
|
|
2. For users not familiar with BCP 47: the language tag should be easy to construct with a lot of help from the program.
|
|
|
3. Users intimately familiar with BCP 47 should be able to quickly input a valid BCP 47 language tag without having to hunt through multiple
|
|
|
combo boxes.
|
|
|
4. The displayed language tag should be human-readable (e.g. "English" instead of "en").
|
|
|
5. The displayed language tag should still offer the full information about all of its components.
|
|
|
6. The new controls should ideally fit into the same space the existing controls were occupying, if at all possible without making the
|
|
|
dialog any wider.
|
|
|
7. After swapping out the old for the new controls the interface should not be much more confusing than it was before.
|
|
|
8. The number of mouse clicks required for the most-often executed operation (changing solely the language code) should ideally not
|
|
|
increase, or if it has to increase, as little a possible.
|
|
|
9. The new controls should be usable solely with the keyboard.
|
|
|
10. The user interface should not accept invalid language tags.
|
|
|
|
|
|
Of course several of those requirements conflict with each other.
|
|
|
|
|
|
Having the combo box outside would be much more confusing in the presence of other components of a BCP 47 language tag. It would also pose
|
|
|
real problems wrt. handling invalid language tags. Overall that change wouldn't be an improvement due to the number of drawbacks it would
|
|
|
come with.
|
|
|
|
|
|
The current UI the result of finding a compromise that implements as many of the requirements as possible. It's not perfect & I'm definitely
|
|
|
willing to improve upon it. |