I'd forgotten about #XHTML and now I remember why

Also: I say this as someone who is very Pro Standards and who was a big proponent of #xhtml back in the day :p

But it feels like a lo of these are standards for the sake of standards, or standards to try to drive adoption of an idea rather than solve a problem… and none of them can be easily or incrementally implemented.

I can write a YAML parser in an afternoon. I haven't even wrapped my head around how to write a #JsonLD parser, but the value I get from JSON-LD is almost purely theoretical

Also seeing more creators investing time into thier platform agnostic spaces (e.g. personal websites, project websites). I know not all #furries wanna bother with managing websites (although there are plenty of #WYSIWYG/code-less methods and services) I'm a #furry #WebDesigner so I'm open to peeps reaching out if they need help.

#Wordpress #MySQL #LAMPStack #CMS #Templates #Drupal #ForumWebsite #CSS #XHTML

@jehansanspour

Tu as raison : l' #epub, c'est du #xhtml encapsulé. Autrement dit, avec un minimum de boulot, c'est assez facile à produire, mais faut vraiment arrêter d'écrire avec Word. Ce truc surcharge en balises dégueulasses, c'est de la merde à nettoyer.
Produisez du RTF si vraiment vous êtes des manches.
Sinon, utilisez un éditeur #LaTeX, mais pour faire simple, #MarkDown est le couteau suisse des rédacteurs.

@HydrePrever @ciredutempsEsme @scudery @Toniours

I never thaught I'd be saying this, but processing #XML from #C to turn #XHTML into #SSML with #libxml2 was an utterly *enjoyable* experience! I know right, in what universe is that possible? But props go to Daniel Veillard, Gnome, and contributors. It's fast, simple, and easy to understand, and everything just worked!

The “applet” element has been part of #HTML since HTML 3, but got removed in #XHTML 1.1 and HTML 5.

“nextid” was part of HTML in the beginning, until HTML 2.0.

The “s” element is a newer element—but was part of HTML 4.01.

The correct answer is “bdi”—it only arrived with HTML 5.

https://meiert.com/en/indices/html-elements/

@vanilla

Today's #HTML parser needs to account for a lot of shit it doesn't need to make exceptions for, including the knowledge of tags being "void". #XHTML all the way!

#XML is 25 years old.

The tech industry is still trying to extricate itself from that pile of shite. Still got PTSD symptoms from #XHTML and XSLTs

(fun fact: I was also caught in the hype and built my whole website with a homemade static generator that used #XSLTs and #ApacheAnt)

>mfw no #xhtml support on #caddyserver
Just finished setting up my cool hobby website, yay!

>mfw no #xhtml support on #caddyserver

RT @WebDesignMuseum
Happy 23rd Birthday XHTML 1.0!

On January 26, 2000, W3C issued official recommendations for the XHTML 1.0 specification.

https://webdesignmuseum.org/web-design-history/xhtml-1-0-2000

#XHTML #InternetHistory

I'm starting to scrap the bottom of the barrel when it comes to #XML parser conformance tests. Almost everything that remains require me to:

1- Support external DTDs
2- Validate DTDs

So the questions to consider:

1- Instead of validating DTDs, should I look at something like #XSD or #RelaxNG instead?

2- Is it acceptable practice to bundle popular DTDs like #XHTML with the project so we can minimize the network calls? I don't think that'd be a bad idea, so long as licensing allows it.

6. An Attempt at Outlining the Many Factors Influencing #DX: https://meiert.com/en/blog/dx-factors/

7. 0 of the Global Top 100 Websites Use Valid #HTML (in 2022): https://meiert.com/en/blog/valid-html-2022/

8. The #CSS Art Paradox: https://meiert.com/en/blog/the-css-art-paradox/

9. 2 Approaches to #Accessibility on the Web: https://meiert.com/en/blog/active-and-passive-accessibility/

10. Write HTML, the HTML Way (Not the #XHTML Way): https://meiert.com/en/blog/write-html/

Many thanks to everyone reading, supporting, and contributing to my work! 🙏

I never understood why people moved away from #XHTML.

Are web devs really not mentally awake enough to close their damn tags? Now we lost the entirety of XML operability and XML machine parseability, just because some... individuals couldn't stand typing <br /> instead of <br>. Simplified, of course.

XHTML is superior in every way except for feature richness, but that's owed to the fact it was practically abandoned after people already had left it.

#HTML sucks, revive the #SemanticWeb!!

Emacs thinks I need a doctype there. In fact, I don't, since browsers use doctype only to switch between quirks and standards modes, and XHTML do not get quirks mode at all from what I remember :)

#lang_en #emacs #xhtml

I have been remaking my website lately!

It is squarely situated within the retro web or indie web subculture. Only semantic XHTML and CSS, with link lists, blinkies, tons of gifs, playful designs, shrines, blog posts... Like on #Geocities in the far-gone past! Should be accessible too.

It still ought to be filled with content, but we're getting there.

Here you go:
https://libre.town

#xhtml #css #retroweb #indieweb #showcase #blog #internet #yesterweb #reclaimtheweb #oled #website

I never played with #xhtml before o.O https://htmx.org/

Is there a (X)HTML5-only¹ GUI browser, that is not dead. No CSS, no JS, but with an ability to customize font size and maximum width would be nice.

Just wondering, since Gemini doesn't really cover some things I'd like to have.

1. Personally I only need XHTML, but I doubt there exist a browser that supports only this dialect of HTML.

#lang_en #html #xhtml #browsers

New #libxml2 version 2.9.12 breaks validation with some incorrect DTDs, such as old #XHTML 1.0 DTDs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993638#50 — Are there other users likely to be affected when they upgrade to this version?

Giving the idea another shot, now with a blog post: “WebComponents with XSLT” (and then I'll rest, guess it is too niche) https://murb.nl/articles/356-webcomponents-with-xslt?utm_source=twitter&utm_medium=share_link&utm_campaign=social #xslt #xhtml