SyncScriptEncoding UTF8 includes a preamble
ladenedge
Posts: 4
It says in Switches used in the command line that the default should result in a UTF-8 encoding without a BOM. However, when I omit this switch in Data Compare 9, I do indeed get a BOM. In addition, I tried explicitly setting the option in all of the following ways:
I feel pretty certain this option is broken, but perhaps I was missing something on my end?
- /SyncScriptEncoding:UTF8
- /SyncScriptEncoding:UTF8WithPreamble
- /SyncScriptEncoding:UTF8WithoutPreamble
I feel pretty certain this option is broken, but perhaps I was missing something on my end?
Comments
Regardless of whether you use UTF8 or UTF8WithPreamble, the preamble gets written to the file, contrary to the documentation. I had a look at the bytes of the sync script file, and with either option the file starts with xEFBBBF.