For all that concerns databases, I pretty much work with FileMaker Pro.
It can easily export data in XSLX or CSV formats.
When data are exported in XSLX format, multilines fields use 0D (CR) to go to the next line.
When data are exported in CSV format, lines fields use 0B (VT) to go to the next line.
In Affinity Publisher 2.0.3,
When data are imported from XSLX format, we loose the multilines fields because 0D (CR) is transformed to 20 (space).
When data are importe
Same here.
Now… considering how picky FM is when it comes to importing CSV: To import for example the CSV that I can export from my bank account into my self-programmed FM financial database – which does my project time tracking, invoicing, accountancy, taxes, you name it – I have to: 1) clean up the table in LibreOffice to remove redundant non-CSV rows, 2) save as CSV with semicolon in Windows Latin1 encoding, 3) convert the CSV encoding to UTF-8 via BBEdit oder TextBatchConv, 4) convert s