Markup Languages, by @j9t [@frontenddogma.com]:
Markup Languages, by @j9t [@frontenddogma.com]:
Not only that, the source is hand-edited XHTML https://github.com/standardebooks/jane-austen_pride-and-prejudice/blob/master/src/epub/text/chapter-1.xhtml
How quaint!
Your eyes haven’t bled from bad markup until they’ve glanced upon an ePUB exported from InDesign.
The weirdest CSS selector I've used today:
:root[*|xmlns*="facturaElectronica" i]:before
We should have some markup for Venn diagrams so we don't have to attach them as images when creating memes.
If you want to know at what junction our field stood at some point wrt the mobile Web, check out this particular gem from ZDNet, “Souping Up Wireless” (2001).
And yes—WML, HDML, CHTML, XHTML.
Fantastic.
(This relates to what I wrote about the other day, researching content for the 2000s and 2010s archives on @frontenddogma. Stay tuned!)
Here's an idea -- why not use declarative files to define program extensions instead of letting extensions run any code whatsoever?
I feel like the whole X/HT/ML era has been completely lost and app developers can't think in anything but code any more. Every problem is solved with JavaScript. Problems with #JS are solved with more JS. Security problems with executing 3rd party code are not solved by removing 3rd party code but trying to naively sandbox the 3rd party code like the halting problem isn't a thing.
Still think XHTML(5) is better than HTML(5)
Latest version of #HTML standard includes a warning that advises against using the #XML syntax (formerly known as #XHTML), stating that it's "essentially unmaintained" :
https://html.spec.whatwg.org/multipage/xhtml.html
Looks like a recent change, as there's no mention of this in the April 3 version of the spec:
https://web.archive.org/web/20240403210532/https://html.spec.whatwg.org/multipage/xhtml.html
Unless I'm misreading it, this seems like a big deal? E.g. XML syntax is mandatory in #EPUB 3 documents:
https://www.w3.org/TR/epub-33/#dfn-xhtml-content-document
Time to #wheelOutTheDigitalDarkAgeKlaxon ?
[Перевод] Доводы против самозакрывающихся тегов в HTML
Самозакрывающиеся теги - зло? Prettier не прав? Разбор с примерами острой темы в HTML, где все будет разложено по полочкам
ブログ書いた。
XHTML の終焉と XHTML 1.0 Transitional 時代の思い出
https://blog.w0s.jp/706
HTML Living Standard において XML 構文が非推奨であることが明記されるようになりました。しかし世の中のほとんどのサイトには影響ありません。XHTML 時代を回想しつつ、今回の記述追加に至った背景を探ります。
I guess the #fediverse is probably the best place to ask a #webdev #web functioning question of this nature:
I want to add either an #rss or #atom feed to my personal #website. I'm living like it's 2003 and remade it in #xslt, so I was wondering if there is a way of embedding either format directly inside a #xhtml document, #microdata style, or do I need a separate file and/or a more involved #webserver setup with #contenttype?
That would be swell since I could use the same #xml base file to generate links to posts in the #html document, as well as make it available as a #feed.
The alternative would be to pipe this through some build step that pre-generates both files for me, but I'd rather keep this fully #static "drop files into a web server".
The default Emacs mode for xhtml files seems to think a doctype is required in them. It is not (provided they are served as application/xhtml+xml).
Attention Gemini, Gopher, & Finger fans —
Adële ( @adele ) has something to show you:
Adële joins others who argue that — we shouldn't throw out all of the HTML "baby" with the broken-web "bath water" — but that instead —
We should use a restricted subset of HTML — and in particular XHTML.