#xhtml

2025-12-14

APPEL à tous les développeurs qui veulent programmer en Rust dans l'intérêt général avec des technologies W3C entre autres sur des sujets passionnants !

N'hésitez pas à consulter la vitrine FOSS et n'hésitez pas à me contacter pour échanger sur les détails que j'ai envisionné sur chacun de ces sujets :

ethiciel.org/ideas/

@Framasoft @aprilorg

#dev #rust #asso #communaute #interetgeneral #contribution #xml #xsl #xhtml #atom #fs #email #securite #SansFuiteMemoire #ethiciel

@david_chisnall@infosec.exchange

I think, that the best reaction is to boycott and deprecate HTML software that lack of RSS and XSLT support.

#afs #atom #html #rdf #rss #xhtml #xml #xslt

Not to brag, but my website is XHTML 1.2 conformant.

#conformant #standards #HTML #XHTML #obsolete #HumbleBrag #NotToBrag #web #website

2025-11-19

Wenn man zum ersten Mal mit Jakarta Server Faces (JSF) arbeitet, wirkt vieles zunächst etwas „magisch“. Plötzlich erscheinen Daten im Browser, ohne dass man genau weiß, wie sie dorthin kommen. Doch wenn man einmal verstanden hat, wie JSF im Hintergrund arbeitet, wird schnell klar, dass es sich um ein mächtiges Framework handelt...

magicmarcy.de/eine-neue-alte-w

#JSF #JavaEE #xhtml #HTML #JakartaServerFaces #programming

Peter Rushforth 🇨🇦🇺🇦prushforth
2025-11-05

Attention!

Do not add a trailing slash '/' to "w3.org/1999/xhtml" !

That is all.

Jens Oliver Meiert 🇺🇳 🇵🇸j9t@mas.to
2025-10-13

From the archives:

Write HTML, the HTML Way (Not the XHTML Way):

meiert.com/blog/write-html/

#html #xhtml

GripNewsGripNews
2025-09-12

🌘 XFN:用超連結標註人際關係的 XHTML 友善網路
➤ 簡化人際關係標記,賦予超連結更深層次的語意
gmpg.org/xfn/
XHTML Friends Network (XFN) 是一個創新的標準,讓網頁作者能夠透過在超連結的 `rel` 屬性中加入特定值,以簡單、結構化的方式標註與連結對象之間的人際關係。這項技術特別適用於部落格的「朋友列表」(blogrolls),能讓搜尋引擎和應用程式更容易理解連結的語意,進而豐富網頁內容與互動性。XFN 提供了詳盡的說明文件、入門指南、元資料規範、設計理念、常見問題解答,以及各種輔助工具,旨在推廣其應用並鼓勵社羣參與。
+ 這個 XFN 聽起來很實用,尤其是對於經營部落格的人來說,可以更精確地表達和朋友的關係,而不是籠統的連結。
+ 很高興看到有這樣的標準出現,能讓機器更容易讀懂網頁上的關係,期待未來能看到更多應用。

Fiona :transbian: :autism: 🔜 39C3Fiona@blahaj.zone
2025-08-27

I love #HTML, but sometimes it can really be annoying… Take this:

<p>
	I still need to buy
	<ul style="display: inline; padding-left: 0;">
		<li style="display: inline">flour, </li>
		<li style="display: inline">eggs, </li>
		<li style="display: inline">and lentils</li>
	</ul>
	to make Lentils with Spätzle.
</p>

I will die on the hill that this
should work and display as just a regular sentence, though with semantic enhancement, but it doesn’t, for two stupid reasons:

1.
<p>-tags cannot contain flow-content, such as lists. I believe that that makes no semantic sense and furthermore creates rules about the semantic structure of the document based on the default stylesheet. To be clear: I am not saying that there should be exceptions based on the used style-sheet, I’m saying that this rule should not exist and that the semantic structure should be allowed to be whatever!

2. This is even more infuriating and where it actually breaks in practice: Some tags in HTML, such as
<p> and <li> “auto-close” under certain circumstances. This was meant to be removed with XHTML, but sadly the morons who were too lazy to maintain a proper semantic structure in their documents killed it and kinda forced everyone onto non-x html… 🤬

#webdev #xhtml

Stéphane Bortzmeyerbortzmeyer@mastodon.gougere.fr
2025-08-22

@adele I don't understand this error on my site "HTML parsing error at position 81 (line 2): Unexpected character 'h' in input state [BetweenDoctypePublicAndSystemIdentifiers]'

bortzmeyer.org/

#XHTML

2025-07-09

Next in my nostalgia series is the editor (eXe). Development of the eXe Editor was a NZ-funded project and the first time I met -advocate @mackiwg. Twenty years later, the custodians of this eXetremely easy-to-use editor are based at INTEF in Spain:
exelearning.net

Screenshot of the homepage of http://exelearning.org from 2006 (courtesy of the Internet Archive).Screenshot of the current homepage of http://exelearning.net.
2025-05-15

How to use FSFE's webpreview for translations

media.fsfe.org/w/2Hx5degpF8oKu

Ténno Seremél’tennoseremel@gts.skobk.in
2025-05-06

Когда‐то давно, но не очень давно, люди, работающие над HTML, всё‐таки решились и запилили элемент <details> для спойлеров. Но есть нюанс: в параграф, куда его очень часто и хотелось бы запихать, его не поместить — парсер выплюнет наружу. А вот в XHTML такой фигни с парсингом не было и нет 🤭

<p>Вот что я тебе скажу, птичка: <details>Спойлерный текст.</details></p>

превращается в:

<p>Вот что я тебе скажу, птичка: </p>
<details>Спойлерный текст.</details>
<p></p>

Так и живём.

А, и да. Текст по умолчанию (когда нет <summary>) не локализуется. Чтобы не расслаблялись 🤷

#lang_ru #html #xhtml

Jens Oliver Meiert 🇺🇳 🇵🇸j9t@mas.to
2025-04-11

If you’re in the mood for XHTML today, check out @frontenddogma’s XHTML archives! ❎

frontenddogma.com/topics/xhtml

#webdev #xhtml

Matěj Cepl 🇪🇺 🇨🇿 🇺🇦mcepl@en.osm.town
2025-02-16
2025-01-02

Your eyes haven’t bled from bad markup until they’ve glanced upon an ePUB exported from InDesign.

#ePub #markup #InDesign #XHTML #HTML

Screenshot of code starting with highlighted h4 tag: <h4 class="CHead"><em class="Emphasis">Mys</em><span class="NoBreak"><em class="Emphasis">tery</em></span><span class="NoBreak"><em class="Emphasis"> meat </em></span></h4><p class="BodyFirstParagraph">Every now and again, I come across an “alternative” navigation where a designer has decided they can subvert existing conventions and provide someone with a

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst