Using commas in description field messes up exported hours.csv

[Pohli]

When adding hours there's an entry field for optional descriptions at the bottom. If I use the comma character there (which I did alot) and then export hours to a csv file the commas will mess up the csv file cause commas are used as seperator character in the csv files.
If fix is not possible there should be at least a warning somewhere.

[olpeh]

Hey. I'm not actively maintaining this project, but yeah this project is a huge pile of 💩

Do you have any suggestions on how to fix this (properly)? One option I can think of is using semicolon as the separator when exporting to CSV. A better approach I guess would be to allow all kinds of special characters in the description field.

[Pohli]

I'm not a coder but I had a look at the Wikipedia entry about csv files. If you use semicolon as separator it could also make problems to view the files correctly. My exported call lists from my router are also in csv format with semicolon as separator indicated by the first line: sep=;
But the default app for csv files on SFOS, Documents, doesn't understand that and shows garbage.
I suggest to enclose the data (if there's any) from the description field with double quotes and replace all double quotes which are part of the data with two double quotes. Example:
"morning" shift, production
will be changed into
"""morning"" shift, production"
That way it will show correctly in the SFOS Documents app at least.