Rich and Strange Aeons

Style change

2024-05-01T03:17:37Z

I finally poked around at different Dreamwidth styles. The key incitement was that my old one didn't render lists well in Markdown, insert a line break between a list bullet and the list item. Removing the break from the HTML version wasn't much fun.

Turns out that many modern(?) styles have the same bug. But the Abstractia family does what I want. Then it was a matter of hunting down a variant that wasn't dark on dark, tweaking the colors to have more contrast and also more conventional link colors, and seeing if I could get nice fonts back. Firefox is still a stickler about cross-domain loading, so I couldn't get Elegante to be loaded in it, though Safari did load it. I ended up going with Imperial Script direct from Google Fonts.

Ironically, because I have Firefox impose Garamond everywhere it can, I myself do not get the benefit of seeing my own fancy script. On the upside, I see Facebook and Twitter in Garamond.

I also poked at AO3 work skins today, and got my works to use serif with the least effort possible. Create a work skin containing

#workskin p {
  font-family: 'EB Garamond', GaramondNo8, Garamond, Georgia, serif;
}

use the skin for a work, and voila, it'll probably all be in Georgia, unless someone has a Garamond font loaded.

comments

Dreamwidth and HTML formatting

2024-03-12T18:56:54Z

So, my past two entries were composed and posted "AO3" style. I write locally in a Markdown text file, I convert it to HTML via pandoc, I check it locally in my browser, I post it in the HTML mode input box. This has worked great on AO3, but I didn't think to double-check my entries here until replying to comments this morning. And discovered my entries were ugly. Raw line breaks (not br codes, just text file breaks) in the HTML were preserved rather than being wrapped. The paratransit entry had huge gaps in the blockquotes. The blockquotes were italicized.

The first two problems are now fixed, by my checking [Disable Auto-Formatting] and re-saving the entries. The blockquote italics I assume are part of the ornate style I chose to use for this journal, and I guess I get to question that decision now.

Auto-Formatting isn't all bad. This entry was written the old way, as simple text typed directly into the HTML mode box (notice the asterisks) (Edit: never mind, see below.) Without Formatting it would be one big paragraph, rather than (so far) three. (Why don't I use Rich Text? I dunno, never liked it much.)

Anyway, if the Pyrrhic and Paratransit entries looked painful to read, they should be better now.

Edit: I noticed a Markdown option on comments, and then found text format documentation and the Beta page. With Beta Create Entries, I could compose Markdown right here! Huh. Plus an option for making up my own entry links? Fascinating.

Yeah, so if you leave Entry Link blank then your entry URL will be the (digits).html style, but if you enter anything, then it will be (year)/(month)/(day)/(text).html style. You can have human-readable post URLs!

And if you update an older post to the new link style, the old links will still work, I tested it. So you won't break old bookmarks.

comments

Dreamwidth activity pickup

2020-03-25T21:43:06Z

I hadn't been paying attention to post dates... I thought I'd been checking my reading page often enough, but apparently not, because a newly active friend got completely buried until she commented today, and I have to go look for her posts that I missed!

comments

style poll

2018-12-09T20:14:12Z

View Poll: #20874

I adopted it when first joining DW; it was the best intersection of stuff I wanted. I wasn't thrilled by it but at the time I figured DW was just a backup for my LJ and didn't to spend hours on styles.

I wonder how "anonymous" and "details results visible" will interact.

comments

Dreamwidth, free speech, and cat owners

2018-12-08T06:46:31Z

If Dreamwidth allows anything legal, what does that mean for "cat owners"?
denise chimes in.

comments