|
Post by Daniel H on May 15, 2015 23:15:55 GMT
Kappa, I was posting my thing already, so it was not intended to answer your question. I’m doing that now.
|
|
|
Post by Leaf on May 15, 2015 23:18:02 GMT
I'm reasonably computery, but brain troubles.
Also: Windows. But I have Cygwin if that helps.
|
|
|
Post by Daniel H on May 15, 2015 23:28:56 GMT
I will assume that Kappa uses Linux or Mac and is at least somewhat comfortable with the terminal. I think this is true and am erring on the side of explaining to much for my belief about Kappa’s level of computer experience, but I cannot remember why I formed this opinion so it may be completely made up. If this is not true I can explain later, but most of this is necessary in any case. - Download either my attachment or Mother Starlights most recent code snippet and save it somewhere. The main difference between the two versions if you follow these instructions is that hers will put thread titles in bold and mine will put them in h1 tags
- Open a terminal in that somewhere, or open a terminal and type `cd path/to/conversation.py/directory` (without the backticks, and with the actual path to the directory containing conversation.py) and hit enter.
- Type `python conversation.py path/to/exported/csv > path/to/converted/conversations.bbcode` (again without the backticks and with the actual paths of the exported csv file and where you want to put the bbcode file). If you do see output and can’t figure out the problem yourself, post it here so we can help debug.
- Open the path/to/converted/conversations.bbcode as a text file and search for the title of the conversation you want. Copy everything from that to the next hr tag into the comment box in the new Backstage thread for PMs I’m about to create.
EDIT: Just saw your post. In that case you want to open a Cygwin terminal, and I expect you’ll have Python there.
|
|
|
Post by Leaf on May 15, 2015 23:30:07 GMT
I have used Linux in the past, but I am currently using Windows and am most comfortable there. I can cygwin with halfway decent competence, though.
|
|
|
Post by Daniel H on May 15, 2015 23:32:27 GMT
In which case, as per the edit, you should have little trouble following those instructions unless I’m worse than I expect at explaining things online.
Mother Starlight (since it seems a lot of people call you that even backstage now), is there some way to make it so people posting can see new comments from before they hit the submit button? I really like that feature at Alicornutopia, but I don’t know if ProBoards can do it.
|
|
|
Post by Leaf on May 15, 2015 23:44:43 GMT
Brains gonna brain, I'd better wait until after Aestrix's livestream to look at this.
In the meantime, feel free to export all the IC PM conversations you have access to!
|
|
|
Post by Leaf on May 16, 2015 0:08:39 GMT
Psst: I think you're missing a [/quote] in your exported PMs post.
|
|
|
Post by Mother Starlight on May 16, 2015 0:14:44 GMT
I'll look into the preview thing, but I suspect it won't be possible.
|
|
|
Post by Daniel H on May 16, 2015 0:16:41 GMT
Oops, fixed. It was between two conversations that weren’t next to each other in the exported file and I grabbed the wrong chunk.
|
|
|
Post by Leaf on May 16, 2015 14:59:45 GMT
...So, I successfully ran the script...
Now my problem is that when I open the .bbcode file in Notepad, it doesn't recognize the line breaks, and when I open it in vim, it chokes on the apostrophes. You know, "don’t". I donaetmt want to have to find/replace all that gibberish; I'd probably miss something.
Solutions?
|
|
|
Post by Daniel H on May 16, 2015 15:52:45 GMT
I thought Vim was smarter than that. According to Stack Overflow, just put `set fileencodings=ucs-bom,utf-8,latin1` in your vimrc (or just run it in Vim, although I don’t know if it needs to be run before the file is opened).
|
|
|
Post by Daniel H on May 16, 2015 15:59:51 GMT
Also, I apologize for the apostrophes. You had said you didn’t like smart quotes, and since them I haven’t used them when I PMed you. I forgot to extend the same courtesy when PMing your characters.
|
|
|
Post by Leaf on May 16, 2015 16:08:17 GMT
I donaetmt mind all that much. Hmm. The given vimrc line does not appear to have worked.
|
|
|
Post by Daniel H on May 16, 2015 16:35:05 GMT
I rarely use either Vim or Cygwin, so I could be wrong about where the problem is.
Cygwin probably installed the `file` utility. Could you tell me its output on the .bbcode file? Mine reads `UTF-8 Unicode text, with very long lines`. If yours does too, then the problem is Vim not opening the file as UTF-8 despite you telling it to; if it says something else, I’m curious what.
If the file is UTF-8, then maybe you can tell Vim another way. Try running that set command in Vim before opening the file. If Vim is part of Cygwin, try running `export LC_ALL="en_US.UTF-8"` before starting Vim. If neither of those work but the `file` utility still claims the file is UTF-8, then I don’t know what else to try Vim-wise.
|
|
|
Post by Leaf on May 16, 2015 17:02:37 GMT
"UTF-8 Unicode text, with very long lines": check.
Vim keeps stubbornly believing that the file must not be in utf-8: check.
Tried that line in cygwin: didn't help.
|
|