Bug Report: Exported CSV files have encoding issues with special characters

We've been experiencing a persistent issue with CSV exports. Whenever a ticket contains special characters, particularly accented characters like 'é', 'ü', or 'ñ', the exported CSV file corrupts them, displaying something like 'é' instead. This is causing significant problems for our data analysis team, who rely on these exports for reporting. We've tried opening the files in different programs (Excel, Google Sheets, Numbers) and the issue persists across all of them, which points to an encoding problem at the source. We are using the standard export functionality. To reproduce, simply create a ticket with the subject 'Testing éüñ' and then export the view as a CSV. The resulting file will show the corrupted characters. This is a major blocker for our reporting workflows.