[TC 11.00rc1] Unintended CRLF after BOM in 'descript.ion' (File comments) when using 'Unicode UTF8'

[pi.degroote]

When using 'Unicode UTF8' as the preferred type in 'File comments', the 'descript.ion' always starts with an unneeded empty line (CRLF) after the BOM (Byte-Order Mark).

Example of a 'descript.ion' file with 'Unicode UTF8' :

Code: Select all

<-- unneeded CRLF (empty first line here, after BOM)
iview462_x64_setup.exe IrfanView 4.62 (x64)
iview462_plugins_x64_setup.exe IrfanView 4.62 - Plugins (x64)

Tested with Total Commander 11.00 RC1 (x64) on Windows 10 22H2 x64.

[petermad]

Confirmed - it does not happen with "Unicode UTF16" or "Plain text+UTF8"

[ghisler(Author)]

This is intentional for backwards compatibility: This way, older TC versions and other programs which do not support UTF-8 can still copy the comments of files with English names because they see the first line with the BOM as a separate line and ignore it. If the BOM were on the same line as the first name, that file comment would not be copied.