QC will do a lot of stuff, but one of the things it won't do without massaging is get the contents of a text file. There are third-party plugins out there that'll do such things, but I like being able to export to a movie that'll play in Quicktime 7: from there those will render to honest-to-god video instead of remaining a collection of widgets executing graphical instructions in a proprietary environment.
XML files, as opposed to text files, are a different matter; .dae files are just big XML files and that annoying Mac screensaver that displays RSS feeds is parsing the same kind of thing. I know nearly nothing about XML, but it seems to me that the XML desired by QC is pretty damned dumb, and this works in an otherwise blank file:
<XML>
<words>
<data>goatse</data>
</words>
<words>
<data>pygmy goat</data>
</words>
</XML>From there it's not a problem to get QC to choose between the two items, because it can count the amount of "words" tags and get what's in the "data" tags (or whatever other tag you wanna specify at that third level) according to some number-choosing operation: which would you like?
The problem here is that some of these lists are long. Like this one:
There are about 7000 lines in that file, many of them varieties of zombie.
Fortunately, though, that screenshot is of wonderful Mac freebie TextWrangler, and it can do shit, like crazy grep replacements across multiple files. First I thought I could be a smarty-pants and write one grep for a whole file, but I'm not that good, so I broke it up. If you do a find for
"^.*$" and replace that result with "\t<words>\r\t\t\t<data>&</data>\r\t</words>" then every line in the file gets wrapped in the "words" and "data" tags and appropriately indented.
And, quite wonderfully, TextWrangler can save that search pattern in the little g-for-grep drop-down menu on the right and reapply it to anything you wanna deal with in future.
Then, since going to the start and end of a file and typing a few characters is backbreaking labour worthy only of the salt mines, you add saved find/replaces like so: find "
\A^" and replace with "<XML>\r&", then find "\Z$" and replace with "&\r</XML>" and voila, list to XML file in three steps.But wait! You say you are as unskilled as I am and EVEN LAZIER? Why then you use AppleScript, you lazy person, and you can use TextWrangler's capabilities to keep a script in the script menu, making it a one-step process. This last thing is a pain in the ass to get running in a satisfactory manner, thus this post for slugabeds everywhere. Who have Macs. And TextWrangler. And want to make word lists into XML files. Hello, possible person who may be me forgetting something! Remember to be less boring.
With a little bit of cribbing from this post and snippets of a script recorded within TextWrangler, I managed this very satisfying piece of work:
tell application "TextWrangler"activate
replace "^.*$" using "\\t<words>\\r\\t\\t\\t<data>&</data>\\r\\t</words>" searching in document 1 options {search mode:grep, starting at top:true, wrap around:false, backwards:false, case sensitive:false, match words:false, extend selection:false, showing results:no} saving no
replace "\\A^" using "<XML>\\r&" searching in document 1 options {search mode:grep, starting at top:true, wrap around:false, backwards:false, case sensitive:false, match words:false, extend selection:false, showing results:no} saving no
replace "\\Z$" using "&\\r</XML>" searching in document 1 options {search mode:grep, starting at top:true, wrap around:false, backwards:false, case sensitive:false, match words:false, extend selection:false, showing results:no} saving no
end tellAnd now that script (note the double-slashes in the AppleScript grep) lives in here in TextWrangler and works fine:
I might make it a drag-and-drop converter thing later if HEY IF I UPGRADE I GET PONIES.
