Nick Hanley

4abbe33 introduced this issue.

Unfortunately adding `omitempty` will prevent moving a channel to the top (position 0). Related #808.

The issue appears to be that OBS creates v3 signatures[^1][^2] but pacman requires v4[^3]. I've confirmed this is the case for the OBS build of ungoogled_chromium. ``` $ wget https://download.opensuse.org/repositories/home:/ungoogled_chromium/Arch/x86_64/ungoogled-chromium-97.0.4692.71-2-x86_64.pkg.tar.zst{,.sig}...

> it should still be able to verify it though. I'm not sure what "it" you're referring to. Regardless, #12065 appears to work on my development instance. Thanks! FYI pacman...

This undocumented test is part of a larger issue: the stated goal, written tasks, hints, and tests all seem to disagree on what we're trying to accomplish. If the purpose...

The issue isn't that vis should interpret or remove BOMs; it's that a ZWNBSP at the start of a file (a BOM) is currently rendered differently from a ZWNBSP elsewhere...

The same behavior can be seen with other zero width characters such as zero-width space (ZWSP) and word joiner (WJ). [zwsp-start.txt](https://github.com/martanne/vis/files/11413477/zwsp-start.txt) vs [zwsp-middle.txt](https://github.com/martanne/vis/files/11413476/zwsp-middle.txt) [wj-start.txt](https://github.com/martanne/vis/files/11413475/wj-start.txt) vs [wj-middle.txt](https://github.com/martanne/vis/files/11413474/wj-middle.txt)