# Invalid UTF-8 must RENDER, never panic. Two sources, both ordinary use:
# a file pane holds whatever bytes are on disk (latin-1, a truncated sequence,
# an ELF opened by mistake), and the byte-column hscroll cuts a multi-byte
# glyph in half by design. Undecodable bytes come out as U+FFFD, one per byte.
file bad.txt hello \xff\xfe world\nlatin-1 caf\xe9 tail\ntruncated \xe6\x97 here\nend\n
file wide.txt \xe6\x97\xa5\xe6\x9c\xac\xe8\xaa\x9e \xe6\x97\xa5\xe6\x9c\xac\xe8\xaa\x9e \xe6\x97\xa5\xe6\x9c\xac\xe8\xaa\x9e \xe6\x97\xa5\xe6\x9c\xac\xe8\xaa\x9e \xe6\x97\xa5\xe6\x9c\xac\xe8\xaa\x9e \xe6\x97\xa5\xe6\x9c\xac\xe8\xaa\x9e \xe6\x97\xa5\xe6\x9c\xac\xe8\xaa\x9e tail\nsecond line\n
start 30 100 bad.txt
wait 8000 Kill Newcol
stable 700 20000
snap badbytes
start 30 100 wide.txt
wait 8000 Kill Newcol
stable 700 20000
key $
stable 700 10000
snap hscroll-midglyph