mirror of https://github.com/mpv-player/mpv
8bbdecea83
several unicode characters can be encoded in two different ways, either in a precomposed (NFC) or decomposed (NFD) representation. everywhere besides on macOS, specifically HFS+, precomposed strings are being used. furthermore on macOS we can get either precomposed or decomposed strings, for example when not HFS+ formatted volumes are used. that can be the case for network mounted devices (SMB, NFS) or optical/removable devices (UDF). this can lead to an inequality of actual equal strings, which can happen when comparing strings from different sources, like the command line or filesystem. this makes it mainly a problem on macOS systems. one case that can potential break is the sub-auto option. to prevent that we convert the search string as well as the string we search in to the same normalised representation, specifically we use the decomposed form which is used anywhere else. this could potentially be a problem on other platforms too, though the potential of occurring is very minor. for those platforms we don't convert anything and just fallback to the input. Fixes #4016 |
||
|---|---|---|
| .. | ||
| bstr.c | ||
| bstr.h | ||
| charset_conv.c | ||
| charset_conv.h | ||
| ctype.h | ||
| dispatch.c | ||
| dispatch.h | ||
| json.c | ||
| json.h | ||
| node.c | ||
| node.h | ||
| rendezvous.c | ||
| rendezvous.h | ||
| ring.c | ||
| ring.h | ||