Files starting with bytes 50 C3 always open in built-in image viewer

Help & Support
1

I'm on v13.25. Every file that starts with the byte sequence 50 C3 opens using the built-in image viewer. This is a very annoying issue, as starting a plain text file with the norwegian word "På" (50 C3 A5) makes the file unable to open without having to do "Right click->Open With".

I have tried prepending the byte sequence to numerous files to test, and this always seems to be the case. I have attached a text file with only these two bytes. It should be reproducible by trying to open this file with Directory Opus anywhere.
2.txt (2 Bytes)

2

FWIW, your example file opens in my text editor on double click (as expected, since opening application is based on file extension, not file content, unless its extension is not recognized and Windows might try to guess based on file content).

3

If you add clp to Preferences / Miscellaneous / Advanced: [Image Formats] viewer_disable_internal it should stop it happening. We'll try to improve this misidentification in the future.

4

This did not fix the issue. However, after changing the setting and opening the .txt file, the viewer now shows the actual text in the file, instead of just the message "Unable to load picture".

5

Doesn't that mean the issue is fixed?

6

Oh, if you mean that it still opens in the Opus viewer rather than an external app, yes - you might have to use the File Types system to override this until the next beta is released.

7

Yeah, I meant that it still opens in the Opus viewer, when it should open in my text editor (as usually happens with other .txt files without those two bytes at the start). I'm not familiar with the file types system, so I'm a bit unsure about what to change there. The "Text Document" file type which seems to include .txt already points to my text editor (in Actions->open). I did try to add the clp format and point it to open with Windows notepad, but that didn't seem to work (although I might not have done that correctly).

Thank you for trying to help. In any case, it's not a huge issue if I don't get this fixed right now, it's just a little annoyance having to manually do "right click->open with" on the files it affects!