Loading Profile...
CSV Exports and International Characters
Please add BOM to CSV Exports. The way it works now (sprint 26), you need to manually select the codepage while importing the file into excel so that it recognizes international characters.
I’m sad
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?BOM is not really needed in UTF-8 as this encoding doesn't depend on endianness. We hesitate to add BOM just for Excel as it might break other tools that parse CSV (custom made scripts etc).
I’m undecided
-
Inappropriate?Got it! Can you add this as a project option? (You probably already new this was coming :) ) There's no byte order mark at 8 bits, since it's comprised of a single byte... But at least this way Excel will (probably) know it's a UTF-8 file and not a 127 bits ASCII one. Making this a project option lets the user decide what's best for his/her needs. -
Inappropriate?We'll think about it, but on the other hand we don't want to introduce too many cryptic options, and "use BOM for CSV" sounds rather intimidating :)
Anyway thanks for your great feedback!
The company and 1 other person say
this solves the problem
1 Comment Add a comment
This solves the problem
-
Thanks!
