The trouble with patterns...

Somebody wise once said, "No good deed goes unpunished."  It was a quote that resounded enough with people to get incorporated into a song from "Wicked," which I have a tendency to belt out unsolicited at random points in my life anyway.  Musicals aside, I get reminded of that old dictum plenty in my daily life, but today I encountered a--well, not glaring, but moderately annoying--reminder in my knitting life.  In the process, I think I may have broken the Blogger platform.  Just a teeny tiny bit.  Temporarily.

I tried to post a pattern to my blog.  Not just any pattern, but a lace scarf complete with really big charts that had to be converted from spreadsheet to image to PDF before it could be uploaded into the bowels of Ravelry.  I then proceeded to try to make it available to the Ravelry-averse, aka me up until 3 months ago.  Um...no.

So, the problem with including a link to a pattern in Ravelry is it deletes/inactivates your uploaded PDF.  Oops.

The problem with Blogger is it doesn't like reams of spreadsheet charts.  Or PDFs.  Yeah.

Basically, I spent the afternoon wondering why nobody could download my pattern on Ravelry and why I couldn't simply delete my blog link and reactivate the PDF.  Somebody computer-savvy understands why this is the case.  I, on the other hand, who had to type up said pattern and painstakingly convert my hand-charted lace into an acceptable spreadsheet equivalent, then input all the steps involved in submitting it to Ravelry, and all for the reward of zero dollars every time somebody uses my pattern, had a few choice words with my computer.

Alas, the result is that in order to access "Let It Go" (pictured to the right), you will have to follow this link.  That is, until Blogger gives me the ability to import knitting charts and PDFs.  Anybody want to work on that?  It's a good deed that won't go punished, at least not by me.