Exported posts data is corrupted
-
Continuing the discussion from Warning: WTDWTF will be read-only soonish:
@RaceProUK said:Forgot you could export postsβ¦
-
Huh, so somebody actually used the export feature for something other than DDosing the site...
-
hmmm five will git you five pound ten and six that that particular post s something to do with unicode, and also that it's not the export that's corrupt but rather excell not handling it right.
What does that line like like in notepad++?
-
-
-
What does that line like like in notepad++?
[s]No idea; already deleted the export.[/s][s]Was only interested in finding my first post anyway
[/s]
It's the export
-
aaah.......
well i have to go to the bank to get some money... i seem to owe you five pound ten and six.
-
well i have to go to the bank to get some money... i seem to owe you five pound ten and six.
Maybe not - that byte sequence happens to map toU+2060 WORD JOINER. So actually, you're right insofar as Excel's not handling it right.However, if the export was actually marked as UTF-8 properly (or if it was UTF-16), Excel would have handled it fine.
So it's up to you: is TRWTF the export not being marked with the BOM, or Excel not auto-detecting UTF-8?
-
hmm...... :-D so i won, but only kinda (because of the missing BOM)
-
Let's assume the export-tool is not broken but this stuff is in the database that way... wouldn't that explain all the performance weaknesses and the occasional WSODs?
Filed Under: It's all because you guys used Unicode and something and something! #BlameTheUsers
-
This post is deleted!
-
I moved 4 posts to a new topic: Delete and undelete post hides edit button until the next refresh.
-
TRWTF is Windows-1252
Also, UTF-8 with BOM is pretty f'in ugly. It's impossible in the presence of other file headers (
#!...) and will screw up your copy-pastes unless everyone strips and re-adds it every time it exits the program boundaries.
Filed under: EF BF BE
