Interpret a single letter plus colon as drive specification followed by the
actual path instead of splitting it and considering the path the cover
type.
See https://github.com/Martchus/tageditor/issues/109
This is especially useful to check whether a file is complete, e.g. one might
use `tageditor info --validate --pedantic --files …` to check whether the
specified files are ok. (If they were truncated there's be an error about it
and the command would return a non-zero exit code. Without pedantic this would
just return in a non-zero exit code if the file couldn't be parsed at all.)
This is required since the parsed Ogg Vorbis comment's target is set to the
containing Ogg stream as it still makes sense not having to care about the
specific track in most cases.
On non-Windows platforms the internal representation used for paths is the
configured native (narrow) character set. Most of the time that's UTF-8 but
only on Windows UTF-8 is *always* used for the internal representation.
* Make error messages and dialogs more consistent
* Print the actual error message (which might actually contain something
useful when NativeFileStream is used)
The standard actually says that there might be different covers with only
different descriptions:
Description is a
short description of the picture, represented as a terminated
text string. There may be several pictures attached to one file, each
in their individual "APIC" frame, but only one with the same content
descriptor. There may only be one picture with the picture type
declared as picture type $01 and $02 respectively.
I assume "content descriptor" means combination of the type and
description.
This is in accordance with eyeD3.
See https://github.com/Martchus/tageditor/issues/64#issuecomment-833952940