You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is only tangentially related to the notify service, but I wanted to flag it for discussion.
When CSV files are opened by MS Excel, Excel assumes that the file is ASCII encoded - unless a Byte Order Mark is specified in the first 3 octets of the file to denote the encoding. Further details can be found here: https://stackoverflow.com/a/155176
The result of Excel assuming the incorrect encoding is that special characters are rendered incorrectly to the user.
Excel's behaviour here is quite different to other standard spreadsheet applications. Calc on Linux and Numbers on Mac do a pretty good job of automatically detecting the encoding of the file.
I believe that this issue is a good one to discuss now that the Notify service supports CSV file uploads/downloads fully with the addition of is_csv to prepare_upload.
A very simple idea that I have is to call this behaviour out in the client docs (there's a new section on CSV uploads) - in order to get ahead of this issue for developers that are looking to send CSVs from their apps.
Example Code: CSV which is badly rendered in Excel:
This issue is only tangentially related to the notify service, but I wanted to flag it for discussion.
When CSV files are opened by MS Excel, Excel assumes that the file is ASCII encoded - unless a Byte Order Mark is specified in the first 3 octets of the file to denote the encoding. Further details can be found here: https://stackoverflow.com/a/155176
The result of Excel assuming the incorrect encoding is that special characters are rendered incorrectly to the user.
Excel's behaviour here is quite different to other standard spreadsheet applications. Calc on Linux and Numbers on Mac do a pretty good job of automatically detecting the encoding of the file.
I believe that this issue is a good one to discuss now that the Notify service supports CSV file uploads/downloads fully with the addition of
is_csv
toprepare_upload
.A very simple idea that I have is to call this behaviour out in the client docs (there's a new section on CSV uploads) - in order to get ahead of this issue for developers that are looking to send CSVs from their apps.
Example Code: CSV which is badly rendered in Excel:
Example Code: CSV which is rendered correctly in Excel:
The text was updated successfully, but these errors were encountered: