While looking at bug 1499475, I noticed that in the print preview dialog, the preview is not displayed anymore. The problem is that calOutlookCSVImportExport.js is ANSI encoded both in c-c and c-esr60 (haven't checked c-b, but I assume it is the same), but the module loader at  expects the script to be UTF-8 encoded. This breaks any code in import-export subdirectory.
This fixes the issue for me locally, though it's unformatunate that we have non-ascii characters in this file due to the hard coding of the csv headers. Can you please cross check that it also works for you? Is it possible to add a check task for the character encoding of the tree after landing patches siumilar to eslint? That might make some sense.
Attachment #9033878 - Attachment is obsolete: true
Attachment #9033878 - Flags: review?(philipp)
Attachment #9033878 - Flags: approval-calendar-esr?(philipp)
Attachment #9033878 - Flags: approval-calendar-beta?(philipp)
Attachment #9036161 - Flags: approval-calendar-esr+
Attachment #9036161 - Flags: approval-calendar-beta+
Comment on attachment 9036161 [details] [diff] [review] Fix - v2 Apparently we want v1 to land.
Comment on attachment 9033878 [details] [diff] [review] WrongEncodingOfCalOutlookCSVImportExport-V1.diff First version to change encoding from windows-1252 to UTF-8.
Target Milestone: 6.8 → 6.2.5
Status: ASSIGNED → RESOLVED
Last Resolved: 2 months ago
Resolution: --- → FIXED
Comment on attachment 9036161 [details] [diff] [review] Fix - v2 Removing this from my review queue since this bug is closed - please follow up in bug 1523196 and request again if you have an updated patch.
You need to log in before you can comment on or make changes to this bug.