3 ms·
I literally blog with raw SGML. Each post comes with a handful per post ENTITYs for that post's common abbreviations and links. Unlike inopinatus's comment, I
by rssoconnor 2y ago
I literally blog with raw SGML. Each post comes with a handful per post ENTITYs for that post's common abbreviations and links. Unlike inopinatus's comment, I do keep up with "modern" standards, which is why my posts conform to the "ISO/IEC 15445:2000//DTD HyperText Markup Language//EN" doctype, the latest HTML standard approved by the ISO.
Blog content is assembled via various SGML entities includes into a prehtml file of "-//ISO-HTML User's Guide//DTD ISO-HTML Preparation//EN" doctype per ISO 15445:2000 recommendations[0]. This is all processed with osgmlnorm through a somewhat simple Makefile to generate the resulting HTML files.
[0] https://rogerprice.org/15445/UG.html#DOCPREP https://rogerprice.org/15445/UG.html#DOCPREP
- AlienRobot 2y agoI don't know what kind of competition this is, but I'm waiting for someone to say they blog in XML with XSLT.
- layer8 2y agoThat’s less impressive than SGML.
- jasonkester 2y agoAs requested: http://www.blogabond.com/xsl/vistacular.xml http://www.blogabond.com/xsl/vistacular.xml The upside is that the entire html page is content. I defy google to not figure out what to index here: view-source:http://www.blogabond.com/xsl/vistacular.xml http://www.blogabond.com/xsl/vistacular.xml The downside is everything else about the experience.
- lylejantzi3rd 2y agoThis is blowing my mind. That's really cool.
- ttepasse 2y agoYou know, I am so happy that one other person on earth knows this HTML dialect.