Been working on getting back on the art wagon, so here's some designs! I used to be really skittish about designing my own characters for whatever reason, but something about that's been starting to break recently, and I'm rather excited about it.

I don't know if I've ever fully explained what the whole Superkitty thing is here on the journal, but I ended up with two different anthro cats this year with head floof, namely Miranda and Prince, and started pondering ways I could group them. The Superkitties are a sorta-open species sorta-custom thing? Truth be told, it's just anthro cats with big hair, though with some fun pseudo-RPG perks thrown in that were inspired by a literature class I took in high school. The idea is that a race of mystical feral cats started breeding with one very advanced, scientifically-augmented cat sent into space by a world blowing itself up, and everything sorta spiraled from there.

The Superkitties have a WIP world on toyhou.se at the moment that I'd like to get punched up before Art Fight this year. I'm not participating, but Caby is, and I expect her two Superkitties will be listed on her profile, so I'd like stragglers to have some more context should they want that. Part of that involves giving people some more examples of what Superkitties look like, so here's a few designs! Each of these lads were designed to match a few specific "blessings" (those RPG perks I mentioned earlier), and my aim is to line and color them and use them to start decorating the Superkitty world.

I'll have some more finished art up soon. I spent all of today lining the cutest drawing of Caby and I, and I'm gonna color it up and get it up places soon. Man, being able to draw kicks ass. Big recommended.

---

I was gonna do up a long piece explaining the MySQL MoodMatch thing for my album reviews I've been putting together, but eh. It can wait a couple days. Here's something I doodled up for Caby! She's been going through it a little lately, and I figured good vibes are what's needed right now. I really love how this came out. I was even having issues drawing Cammy the other day, let alone Wren, so the fact that both came out real easy (after a nice Saturday morning drive through the countryside) makes me very happy.

This post ties this month with June 2023 (when I switched the journal over to HTMLy) for the most posts made in a single month, fun fact. Here's to a productive June 2025 as well, folks. Lots more to come from me!

---

This is a little old news now, but I haven't posted it anywhere yet, so let's fix that tonight. Lince! There's a certain old Cammy drawing with a big stuffed marf (you can see it on his original original 2019 ref) that we learned a few months ago dcb was mildly obsessed with for a time, so I decided to draw him a Lince version (featuring his real life plushie Timber!) as a present for completing this semester. Came really quick for how complicated the pose is, and he loves it! I'm proud of it too. Crazy to think of a time not that long ago when I used to have a lot of trouble drawing cats, and now they're like my favorite thing to draw, behind badgers.

I've got stuff a-brewin' again. Tomorrow or so, I'll give you guys another WIP project writeup for a certain MoodMatch search thing for my album reviews. Are you familiar with database normalization, chat?

---

If you head out to any flavor of mari.somnol now, you'll see a story! Potentially more, by the time you're reading this! If you caught the previous post I did on my DocBook story build system, you know that it's been kind of a gigantic process already. It took another gigantic process to get it over the finish line, but I'm happy to say that I've hit all the targets I wanted to: one script to build six different versions of each story from a single double-click. I then put the output into my nofi/lofi/hifi AutoSite projects, build the project, and upload. That's all I need to do to keep a single story in sync across all three sites.

Since I've legit worked on nothing but this for days, I'm a little tired of thinking about it, but I figure I should probably get it into the journal for posterity. Besides, I am hugely proud of it, and I know I'll be rereading this in pride in a couple days anyway.

Step three: splitting the stories up with xinclude

Where I left it last, I wasn't sure if I'd be able to meet my requirement of being able to build both individual story pages and the whole story on one page. Turns out, I can! One of the glorious parts about XML is that you don't need an <html></html> sorta wrapper around your markup, you just have the markup, and if you declare your namespaces right, the processor will still understand what you wrote. In my case, I have the individual pages as separate files with wraparounds, and then I xinclude all of them into a master DocBook.

xinclude literally puts the content of the included XML file into the master file, as if you copied and pasted it in there. xsltproc and DocBook both can work with xinclude, again, with the proper namespaces. This means I can run xsltproc on any individual chapter or the master file, getting what I want out of each. Kino.

Step four: building into my AutoSite projects

Before this, for testing and learning purposes, I had my XSLT stylesheets set up to build full webpages with a doctype and everything. If you know AutoSite, you know that it's actually a templating system, where it takes stripped-down input pages with only the page's content and some metadata, and then smushes them into a rich layout template (the rest of your site markup). That way, you only have to edit the template to fix any errors or add to, say, a navbar.

As AutoSite's #1 fan now and forever, I wanted to be able to make use of my existing templates and use XSLT to output Autosite input pages I could drop into my existing projects for nofi, lofi, and hifi. This was pretty simple stuff, since input pages are still just HTML pages (or Markdown, but that's not relevant to us right now), but there were still snags.

For one thing, dcb wrote AutoSite to rely on specific whitespace around the attributes at the start of each input page, which xsltproc wasn't outputting using its <xsl:comment> processing. So this worked:

<!-- attrib title: Kevin and Theo's Multiverse Misadventure -->

But this (what xsltproc produces) did not:

<!--attrib title: Kevin and Theo's Multiverse Misadventure-->

As a result, these attributes were getting AutoSite confused, and it was passing them through as page content, breaking a lot of things in my templates as a result.

I could've worked around this with literal HTML outputting using the <xsl:text> element, but the good part of using your friend's tools is that they'll usually happily bugfix stuff for you. dcb rewrote his regex for parsing those, fixing another long-standing bug in the process (!), and I had an updated AutoSite that could handle these valid-but-odd attributes within a few days. Good lad.

The other issue was that xsltproc was spewing out an HTML doctype and some namespace attribute spam on all the pages it put out with no way to disable that. Even if I could write a new version of xsltproc to fix this, since it is open-source, that's just a lot of fucking work for no real purpose except this one niche edge case. I had a much better way to fix it, which I'd handle next step.

Step five: wrangling all this shit into a shell script

This was the most aggravating part of the process, because it required me to play with Linux. At least, something that works like Linux.

Remember, I've been basing this whole setup on Cygwin, which is a set of tools and a terminal of sorts meant to give you Linux functionality on Windows. xsltproc, coming from the GNOME camp, is naturally a Linux tool. If I wanted to automate it, I'd be writing a shell script. No big deal, nothing I haven't done before, but something always fucks up tremendously when I have to dive into the gooey guts of anything Linux-related, and this time, it was find that put me through the wringer.

find is a program that can search for files with certain criteria and then do something with them, like pass those files onto an executable or run a shell command on them. This is naturally what you want if you're trying to automate running xsltproc on a whole directory of XML files. The big frustration was that I obviously needed to make output directories for each file, named the file name but without the extension (01, 02, full, etc), and find doesn't provide functionality to pass the base name of the file to the executable you're running from it. That's because Linux doesn't care or use file extensions. At its silliest, find would try to run xsltproc on the output directories as well (also named stuff like "full.xml", despite being directories) and obviously that wouldn't work.

If that's gibberish, that's okay. I've blocked most of this out of my long-term memory for my health. My ultimate solution was to have find and xsltproc make the output directories whatever they'd be called and then use mv later on to simply scrape the .xml off each of the directory names. Hey, if we're already scripting it, might as well take the caveman approach.

This is also where I'd take care of the doctype and namespace cruft, again running find, this time on all the output HTML files it can find in the output directory, and then using sed to delete the first line of the file (the doctype) and any namespace cruft it finds anywhere in the document.

Anyway, it works. I now had xsltproc building AutoSite input pages for me. All that's left is to translate it to the other two sites.

Step six: writing lofi and hifi XSLT stylesheets

This was as much working on the AutoSite templates and CSS stylesheets for each project as it was doing stuff with XSLT. Now that I had the build process working, I just needed it to take those same files and make lofi and hifi compatible versions as well. This is also where I dragged forward my preferred story fonts (New York and Los Angeles, because the classic Mac OS fixation never dies) and also the color-coded character dialogue styling from my old sites to the new ones.

All is said and done, this had to happen. There was no way I was gonna be able to put stories on all three sites and then manage potentially six different versions of each story, even just to fix a single typo in each. Bigger changes or rewrites, not happening. This is a huge step towards being able to publish what I'm writing to my sites again like I always wanted, and I'm very proud of how it came out. Even better is the ease of updates: if I write a new chapter and want to publish it, I just add it to the DocBook, rerun the script, rebuild the AutoSite projects, and reupload. New chapter added, can link it to everyone, we're all good to go. If I want to build DocBook to some other XML-based language in the future (eBooks, maybe?), I can add that pretty quickly to the build system.

If you're curious to see the beast in all its messy glory, I made a GitHub repo for all the XSLT sheets and such. I'm sure there's lots to be cleaned up in them, but I really don't care. No one's gonna see it but me and the morbidly curious.

Anyway, all this techie junk distracts from the important stuff! Seriously, I've realized this is so techie-wonky that, when I try to explain it to friends who are less technically inclined and then show them the end result, all they see is the story—which is how it should be anyway, huh? And of course, there's the really immortal, million dollar question, "when will there be more stories, Cammy?"

Watch out. You might get what you're after.

Oh, totally random aside—can you believe I've lost weight in the past two weeks? I'm at 144lbs. That's 6lbs lighter than my stretch goal from this time last year, and nearly 30lbs lighter than I was last time I saw Caby. It feels good! Not really interested in snacking or drinking, just banging out projects and playing Guitar Hero. Lots to do, lots of time to do it. Happy Summer vacation.

---

Like I said the other day, I've got a small pileup of books—mostly music books, but with a few oddball topics on there as well—that general lack of time and patience has kept me from digging into. Cold anything is a hard proposition, but especially cold reading. Just picking up a book and starting, I dunno, it's not something I normally find myself in the habit of. Desertbound on Kindle did get me going though, and I'm eager to keep it going.

I must've been in a Barnes and Noble last year with my mom around my birthday. Maybe I'm just deprived, but ending up in Wind Gap and going to check out even big box retailers up there is pretty fun. Books! Books I just said in the last paragraph I have trouble reading, but books! She'd plucked a Mudhoney biography from the shelves to get for me (can you believe I've still never owned anything Mudhoney, despite all the time I spent with Superfuzz Bigmuff in high school?), but this one caught my eye a little more, even: World Within a Song by Jeff Tweedy.

I've been slowly getting into Wilco courtesy of dcb, and Jeff is one of those kinds of legacy artists who's just as noteworthy for himself as he is for his music. Something about his hesitant, wary outlook and dry commentary, you really do get the sense he's kinda amazed anyone would want to listen to him, but we do! I wound up getting both books.

World Within a Song is an examination of the cross-section of life and music, the way that music colors the scenes of your life and the way that life colors the way you feel about songs, bands, and albums. That makes it sound really heady, but it's honestly pretty light reading. A lot of it is Jeff's storytelling and memorializing, and the rest of it is a peppering of outlook on the music business, some anecdotes about paying your dues at the crossroads of punk and country, and what music encourages us to do and feel and how it grows with us as much as it stands still, acting as a vantage point as we move through life.

Jeff picks out fifty songs (well, including every song by the Beatles, so slightly more than fifty) that take him through early childhood into his adult life touring with Uncle Tupelo and Wilco. That's the meat of the book, and thankfully, it's his strength. Lightly dissecting music, he's interesting. Telling these stories of his family terrorizing the neighbor's kid with ham radio gear, or the poor orderly at the rehab facility who, with pinpoint comedic timing, in the midst of Jeff's most horrific withdrawal symptoms, wanted to know if Wilco were still playing Coachella, or the Traumatic Toilet at CBGB's, he's quite funny. Not as funny when I retell them, but that's how it goes with these things.

Now for the less-than-positives. Jeff has a kinda bizarre writing style that I'm genuinely amazed his editors didn't clean up first. It becomes transparent fairly quickly, thankfully, but he has this wonderful habit starting sentences off with "and", "but", and "because", leading to what feel like fragments across the book. Apparently this isn't incorrect, as the AI slop articles and gleeful contrarian contrarians like to tell you, but my God, is it choppy. Perfect example, open the book, random page, page 64:

Is this song for everybody? No. It's not a song I would throw on at a BBQ. But it is special to me. Which is the point of this book.

Okay, it's not incorrect, sure, but is that elegant?

Truth be told, though, it's not like he can't write. In fact, I feel the urge to balance the previous example with another snippet I found interesting, about Carole King's "Will You Love Me Tomorrow", just so you guys don't think Jeff Tweedy is actually a caveman:

There was a period in my life, back in the early Wilco days, when singing this song as an encore—a ballad that I would often deliver lying on my back while being held aloft and passed by the outstretched arms of fans, crowd surfing in slow motion—felt like I was being as honest as I could ever be with an audience. Will you still love me tomorrow? All of you. Will you? Because this night is forever to me. I can feel you... I sense you mean it right now in this moment... I can allow myself to trust you. But you're going to move on, aren't you?

My only other complaint is that, by the time you get into the final ten songs, it does seem like he stops finding personal anecdotes and experiences to regale you with in the songs, and even he's a little lost as to how exactly to get them to fit in the lattice he's set up for himself. As he says exploring "I Love You" by Billie Eilish:

As the songs I'm excited to write about get closer and closer to the present moment, I'm finding them more difficult to write about.

Is that a bad thing? No, but given that the anecdotes and the way these songs personally shaped Jeff's life were such a driving force at the start, it does make things more diffuse as the book comes to a close. He still finds something interesting in them, though, so I suppose that justifies it. That said, that brings me to another holdup you might have: how much is someone not up on their Jeff Tweedy lore gonna get out of this? Plenty of it is universal enough, catching shows with your mom as a kid or finding shelter from the displeasure of the world in music that seems common only to you, but I dunno—did you know Jeff Tweedy collaborated with Mavis Staples (do you even know who Mavis Staples is?), and is that going to impact how you read her chapter?

Really, that's really the valley where World Within a Song dwells, a book that's deeply personal, and a book where the depth comes from examining what these little things mean to Jeff personally. He'll spend two pages telling you that it's okay if you just never get a song, that it's okay to dislike things as much as it is to like things, only to say "actually wait no, fuck Bon Jovi, you should not like Bon Jovi". He's human! Jeff's book, like his music, is interesting precisely because of how much light he finds in the shards of broken glass. It's imperfect and maybe a little wispy, but that suits it, I think. It's a good book to mail to dcb.

---