Encode & Decode .CSV
Client tables ship with every cell written as Base64, which is unreadable the moment you open the file. Drop the .csv here and you get it back in plain text, edit it, drop it back and it goes out encoded again. The same job GRF Editor does on your desktop, without the install.
- 0files done
- 0rows read
- 0cells turned
- 0uploaded
Your files
Auto picks the direction from the filename, the way the desktop tool does: a plain .csv gets decoded, one that already says _decoded gets encoded again. Force it either way if you would rather decide yourself.
Nothing loaded yet. Anything you drop is listed here with what happened to it.
Results
Every row, in plain text
Change what you like. Nothing is written until you save, and saving encoded gives you the file the client wants.
Search finds every cell that contains what you typed. Click a result, or press Enter, and the table jumps to that row with the text selected. Inside the table, Enter moves down the column and Tab moves across. Edited cells stay marked until you save.
How it works
Exactly what the desktop version does, so a file you turn around here is the same file you would have got there.
Decoder
- Takes every .csv that does not already have
_decodedin its name. - Walks every cell and reads it back from Base64.
- Writes the file out again with
_decodedadded to the name.
Encoder
- Takes every .csv that does have
_decodedin its name. - Walks every cell and writes it as Base64.
- Writes the file out again with
_encodedadded to the name.
A cell that is not Base64 is left alone
Decoding a file that was never encoded would turn it into rubbish, so those cells are copied across untouched and counted for you.
Quotes and commas survive
Quoted fields keep their commas, quotes and line breaks. The separator is detected per file, or you can name it.
Korean text is handled
Decoded bytes are read as UTF-8, and as CP949 when they are not, which is what older client tables are written in.
Encoding writes UTF-8
Text goes back out as UTF-8 before it is encoded, which is what current clients and editors expect.
Keep a copy. Work on a copy of your client files, not the only one you have. This tool never writes to your disk on its own, but a bad edit in a table is still a bad edit.
Doing this on the desktop instead? GRF Editor has the same thing built in, and it can put the file straight back into your .grf.