For years, my site has been using Windows-1252 character encoding. Although it works, it isn’t considered HTML5 standard. I’d avoided the converting to UTF-8 in the past due to issues I kept running into. Today, I just made the switch and have been walking through pages and recent articles, fixing things. So far so good!
I do have some items still to fix. For all my custom code, I removed a troublesome module and that seemed to fix a lot of issues. I still need to dig deeper to see what, if anything, it may break. I did run all my changes through an HTML validator. So far so good.
Since I’m not going back to all 500+ articles on my site today, I will be slowly and updating them as I get to them. I doubt too many people will notice, but if they do I’ll jump on them sooner.
I realized today that my z80 Digital Rain program wasn’t playing correctly. The javascript I was calling expected an element on the page that wasn’t present. I removed the element and included the correct routines to allow the Chroma hardware to display properly. Understanding the code a bit better, I might try to do some future clean-up. For now, things are working again.
I’ve had the same turtle image on my main site since 2019 and it was time for a change. The geyser is from my recent trip to Yellow Stone.
Since listing a ZX81 program written in assembly isn’t all that interesting, I wrote a little routine to display the assembly code if available. This is a pretty simple routine, just dumping the file into a PRE.
I really need to completely redo the way I handle text on my blog. I ran into a bit of problem today where the CMS gladly converted two newlines (HTML BR) into paragraphs (HTML P blocks) within an HTML PRE block. This effectively adding extra lines spaces I didn’t want. The short term fix was to create a new BBC BR code that prints a line break after the earlier conversion. I still have to remove the extra space. Not ideal, but it will do for now.