Patch #6287
closedcharacter corruption in exporting spent time
0%
Description
UTF-8 encoding is missed for a 'Total' literal at TimelogHelper#report_to_csv.
Character corruption occurs on my environment (Japanese setting).
Files
Related issues
Updated by Jean-Philippe Lang over 11 years ago
- Status changed from New to Needs feedback
Updated by Filou Centrinov over 11 years ago
No. I also just checked 2.3 (Revision 11698). CSV exports (issues or time entries) are always ANSI encoded, not UTF-8 encoded.
Ruby version 1.9.3 (i386-mingw32) RubyGems version 2.0.2 Rack version 1.4 Rails version 3.2.13 Active Record version 3.2.13 Action Pack version 3.2.13 Active Resource version 3.2.13 Action Mailer version 3.2.13 Active Support version 3.2.13
Updated by Filou Centrinov over 11 years ago
- File timelog_ru.csv timelog_ru.csv added
- File timelog_en.csv timelog_en.csv added
- File timelog_ja.csv timelog_ja.csv added
I don't know if we talk about the same thing. I was speeking about the data in the cvs file (column header, issue name, time log comments, ...), including the 'Total' literal in the header from the csv export of time report. Independing from which csv export (issues/ time log details/ time log report) the encoding for japanese language profil is not utf-8 encoded.
I notice that, if my profil language is english or japanese the csv-export is not utf-8 encoded, but if my profil language is russian I receive an utf-8 encoded csv export. See timelog upload.
Updated by Toshi MARUYAMA over 11 years ago
- Status changed from Needs feedback to Closed
Filou Centrinov wrote:
I notice that, if my profil language is english or japanese the csv-export is not utf-8 encoded, but if my profil language is russian I receive an utf-8 encoded csv export. See timelog upload.
ru: UTF-8
source:tags/2.3.0/config/locales/ru.yml#L394
en: ISO-8859-1
source:tags/2.3.0/config/locales/en.yml#L142
ja: CP932
source:tags/2.3.0/config/locales/ja.yml#L163