I think the problem can be resolved if users can override general_csv_encoding setting in CSV export options window like the following picture. No one can get CSV file in UTF-8 without modifying source code of Redmine. But actually the encoding is fixed to CP932 for Japanese users ( source:tags/3.3.3/config/locales/ja.yml#L164) and gb18030 for Chinese users ( source:tags/3.3.3/config/locales/zh.yml#L147). If you want to export those issues to CSV, using UTF-8 as the CSV encoding is only solution to get readable (not garbled) CSV file. Suppose the situation that issues in a project are written in Japanese or Chinese (mixed language project some issue are written in Japanese and some issues are written Chinese). Sometimes it is problematic for teams using multiple languages. In the current implementation, the encoding of exported CSV is fixed for each language and users cannot change it.