Generate documentation surrounding .csv editors' known export behavior

[hocksteindw]

Microsoft Excel for Mac does not play nice with BWF MetaEdit's import function in my experience, even when generating "compliant" UTF-8 .csv's. My solution has always been to create .csv files using another tool such as OpenOffice or LibreOffice, rather than trying to solve the mystery on my workstation. Maybe others have had success w/ Excel for Mac, would love to know. Windows users don't seem to have problems.

I'm not sure this is an issue worthy of modifications to BWF MetaEdit itself, but I wonder if it may be a good idea to solve this issue with a small amount of detective work that results in some documentation. Happy to contribute.

[g-maxime]

I've found multiple issues with a BWF MetaEdit CSV file imported into Microsoft Excel on Mac and then exported again:

• Exported file contains a byte order mark (BOM).

• Despite the export option being called UTF-8 CSV (comma separated), Excel uses a semicolon in most cases (seems related to locale settings).

• In the last screen of the import wizard, select all columns and set the type to "Text" to prevent Excel from changing the value formatting.

Snapshot: https://mediaarea.net/download/snapshots/binary/bwfmetaedit-gui/20250225-2/BWFMetaEdit_GUI_24.10.20250225_Mac.dmg