UTF-8 BOM marker @iniread failure

[Stefano Piccardi]

I have a UTF-8 encoded file.ini with the following contents where *BOM* represents the 2-byte unicode marker:

*BOM*[Section]
Target=..\file.ext

@iniread[".\file.ini",Section,Target] always returns the null string instead of the Target field value. After re-encoding file.ini to remove the BOM marker @iniread works correctly, so I'm thinking that @iniread get's confused by the BOM marker.
Versions: TCC 12.60, Windows XP 32.

 

[rconn]

I have a UTF-8 encoded file.ini with the following contents where *BOM* represents the 2-byte unicode marker:

*BOM*[Section]
Target=..\file.ext

@iniread[".\file.ini",Section,Target] always returns the null string instead of the Target field value. After re-encoding file.ini to remove the BOM marker @iniread works correctly, so I'm thinking that @iniread get's confused by the BOM marker.

@INIREAD (like most things in TCC and Windows, and everything in CMD) does not support UTF-8. Use UTF-16.

 

[Stefano Piccardi]

@INIREAD (like most things in TCC and Windows, and everything in CMD) does not support UTF-8. Use UTF-16.

Thanks, UTF-16 isn't an option as I receive these files from others. I'll work around it.

 

[Charles Dye]

Insert a newline before the first section header?

 

[rconn]

Thanks, UTF-16 isn't an option as I receive these files from others. I'll work around it.

You receive UTF-8 Windows .INI files from others?? Since Windows cannot handle them, I don't understand the purpose.

 

[Stefano Piccardi]

Insert a newline before the first section header?

Tried that before, didn't make any difference.

 

[Stefano Piccardi]

You receive UTF-8 Windows .INI files from others?? Since Windows cannot handle them, I don't understand the purpose.

A special program can/does handle them. I can't tell you more, I don't have access to the program source file.