The following issue has been fixed from macOS Ventura 13.4 (Monterey 12.6.8) and does not occur any longer.
On macOS Ventura 13.3, when you try to open a Gmail attachment file downloaded through Chrome, you may find that the file itself does not get opened but only the associated app runs.
It means that the filename stored on the device is in the NFC form and has failed to be forwarded to the app. Similar problems like this are being reported with other files created by some third-party apps.
The problem does not occur if the filenames is in the NFD or ASCII form. And since such a problem has never occurred on earlier versions than macOS 13.2.1, it is believed that the problem is due to a bug in the OS.
The Finder allows you to rename a file by selecting it and press the Return key. If you leave the filename untouched but press the same key again, the filename's for is converted to the NFD form.
Bandizip for macOS supports both NFC and NFD filenames, but it uses an NFC one by default when processing files, to secure compatibility with other OSes like Windows.
Due to the problem described above, however, you may find that you cannot open an archive created by Bandizip if the Archive Utility has been chosen to open the archive.
In this case, run Bandizip and go to Preferences > Advanced tab, and then check the "Use NFD filename" checkbox.
Still, if you frequently exchange files with Windows users, using an NFC filename whould be better in terms of compatibility. It is recommended to use an NFC filename if the bug in macOS get fixed by Apple someday.
Please visit the link below to learn more about the NFC and NFD filenames.
Help » How to change the Unicode normalization form used for filenames
