Importing a UTF-8 file without BOM (using dopusrt /col /import ...) results only in the lines without unicode characters being added to the collection.
Manually adding a BOM of 0xEF 0xBB 0xBF at the beginning of the input file fixes that behavior and every file is added properly.
The windows console (%comspec%) does not append a BOM when piping cli application output so this becomes an inconvenience requiring another step of adding a useless 3-byte header using a third-party application. The encoding switches work only for export and not for import.
This could be easily resolved if the dopus parser would either:
- assume that any file is unicode utf-8 by default and decode respectively without requiring an exclusive byte-order-mark
- allow specifying encoding switches for /col import such as /utf8 and /utf8bom
Opus version: 10.0.3.1.4402.x64