Quantcast
Channel: YouTrackYouTrack (JT) - Bug and Issue Tracker
Viewing all articles
Browse latest Browse all 74845

JT-14117: "Issues in CSV" export: exported file does not open correctly in MS Excel on some regional settings

$
0
0
Reporter atx (atx) atx (atx)
Created May 8, 2012 4:44:42 PM
Updated Apr 26, 2013 6:35:16 PM
Priority Normal
Type Usability Problem
State Open
Assignee Alexander Buturlinov (alexander.buturlinov)
Subsystem Import
Fix versions No Fix versions
Fixed in builds No Fixed in build
Affected versions 3.2.2, 3.3
Browser Any Browser
OS Windows 7, Windows XP, Windows Vista
Verified in build Not verified
Verified by Nobody
Reviewed by No reviewed by
Severity Undefined
Steps to reproduce the problem
1. export list of issues to CSV file
2. open the file in MS Excel on Windows with e.g. Polish or German regional settings (or any other with system-wide "list separator" set to ";")

What is the expected result?
Excel opens the file and shows data in columns

What happens instead?
Excel opens the file but whole rows are in one column


Reason and solution:

The CSV file exported by YouTrack always uses comma as separator. This prevents opening the file correctly by Microsoft Excel on some locale settings.

Reason is: Microsoft Excel expects the separator in CSV file to be a system-wide separator as set in Control Panel (Region and Language -> Additional -> List Separator). On some localizations it's comma character, on some other (e.g. most of european) it's semicolon. Now, if the separator in CSV file does not match "list separator" as set in Windows, MS Excel will not open file correctly (see screenshot).

Solution: put the "forced separator" directive in exported CSV files. YouTrack should add this line on top of each exported CSV:
sep=,

This will force Excel to treat comma as separator no matter what are the Windows regional settings. The problem will then be solved for good.

Attachments:
  • original.csv - example file exported by YouTrack
  • original.png - screenshot of MS Excel (PL locale) opening the original.csv incorrectly
  • fixed.csv - original.csv with "sep=," fix applied
  • fixed.png - screenshot of MS Excel (PL locale) opening the fixed.csv correctly

See also here for similar problem:
http://superuser.com/questions/180964/how-to-open-semicolon-delimited-csv-files-in-us-version-of-excel

Viewing all articles
Browse latest Browse all 74845

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>