search

Josepeterparker / google-refine

Automatically exported from code.google.com/p/google-refine
Other
0 stars 0 forks source link

Character encoding not being set in new projects #486

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
The problems that Thad reported with reintepret here:

http://code.google.com/p/google-refine/issues/detail?id=237#c6

I think are due to the character encoding being set to "" in newly created 
projects.

It looks to me like if the user doesn't explicitly select a character encoding 
we are using "".

Original issue reported on code.google.com by tfmorris on 18 Nov 2011 at 7:42

GoogleCodeExporter commented 8 years ago 
It also looks like the character set encoding guessing is no longer being done.

David - was this removed intentionally or is it just an oversight?

Original comment by tfmorris on 18 Nov 2011 at 7:47

GoogleCodeExporter commented 8 years ago 
r2381 makes sure that the project encoding doesn't get set to "" (which is 
probably the state Thad's project is in), but more work is required

Original comment by tfmorris on 18 Nov 2011 at 8:57

GoogleCodeExporter commented 8 years ago 
Hi Tom, it was partially an oversight: I didn't connect the encoding guessing 
code back in the new UI framework, but then it didn't seem to cause any problem 
that I knew of, so I didn't think it was worth it. Also, when several files or 
an archive file get uploaded, it's not clear how to do the guessing.

Original comment by dfhu...@google.com on 21 Nov 2011 at 12:10

GoogleCodeExporter commented 8 years ago 
Bump all unfinished 2.5 Milestone tags to next release

Original comment by tfmorris on 12 Dec 2011 at 7:56