Loading Profile...
Importing tasks from a CSV with international characters cuts the fields short.
When importing a CSV with international characters (such as à, ç, or õ), the tracker creates the tasks with the text cut, turning a phrase like "This phrase will stop here ç and this part will not appear" into "This phrase will stop here ".
I've created a small test project, and a sample csv which shows the problem ( available here ).
This creates some problems when importing data in my case, since most of the titles and descriptions include such characters.
UPDATE: Apparently, saving the file as an UTF-8 file can be used as a workaround. It is still an extra step to be taken whenever I need to edit a bunch of stories, and I think that the import should work a bit better.
If I may, I'd like to recomend Pivotal to look at how Mingle, from Thoughtworks, solves this particular issue (the export and import are based on a text field, and the use copy/pastes the data around)
I've created a small test project, and a sample csv which shows the problem ( available here ).
This creates some problems when importing data in my case, since most of the titles and descriptions include such characters.
UPDATE: Apparently, saving the file as an UTF-8 file can be used as a workaround. It is still an extra step to be taken whenever I need to edit a bunch of stories, and I think that the import should work a bit better.
If I may, I'd like to recomend Pivotal to look at how Mingle, from Thoughtworks, solves this particular issue (the export and import are based on a text field, and the use copy/pastes the data around)
I’m sad
1
person has 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.
The company marked this problem solved.
-
Inappropriate?Hi, thanks for reporting that. We'll get that fixed in an upcoming release.
-
Inappropriate?Hi Bruno
Could you tell us a little more about the computer you're using? Is it a Windows PC? What browser were you using?
Also, do you know what file encoding was used for the CSV you tried to import?
Thanks
Abhi1 Comment
Add a comment
This solves the problem
-
Hey,
I'm using Windows XP with SP3 and Office 2007 to work with the csv file.
Excel I believe outputs the file in ANSI, from what Notepad2 can tell me.
What I ended up doing is saving from excel as csv (which outputs the sheet with ; as separator character), loading it in emacs to turn the ; into , and placing "" around the values, and then loading that file in notepad2 to encode it in UTF-8.
I think the link got killed on the original report, so here it is again: http://dl.getdropbox.com/u/118385/int... . -
Inappropriate?Hi Bruno,
We finally got around to implementing your text field import idea. You can now import projects via file which assumes utf-8 encoding or past the contents into a text field. Check it out and let us know if you have any other problems/suggestions.
Thanks again for sharing your problem and solution,
Mark
EMPLOYEE
EMPLOYEE
EMPLOYEE
