Am Ende der Sieger: Das Open Document Format ist der Standard

Das Open Document Format ist jetzt seit 20 Jahren ISO-Standard. Es steht für digitale Souveränität und Herstellerunabhängigkeit – und ist aktueller denn je.

https://www.heise.de/hintergrund/Am-Ende-der-Sieger-Das-Open-Document-Format-ist-der-Standard-11287440.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

#DigitaleSouveränität #IT #LibreOffice #MicrosoftOffice #Netzpolitik #ODF #OfficeSuite #OpenSource #Wirtschaft #XML #news

Random thought for the day.

How to drive an #AI #LLM into psychosis: ask it for a complete explanation of #XML namespaces.

«У нас было 230 тысяч строк легаси-кода». Как мы изменяли приложение «Настройки»

Привет, Хабр! Меня зовут Александр. В YADRO я разрабатываю приложения внутри оболочки kvadraOS: да, у нас есть своя оболочка на основе AOSP — в команде One UI, Color OS и MiUi прибыло. Сегодня расскажу о тайнах и тонкостях приложения «Системные настройки» — это наша реликвия, очень старое приложение с нагромождением костылей стилей и подходов. Когда наша команда взялась его перерабатывать, у нас было 230 000 строк legacy-кода на Java и около 300 активностей и фрагментов. Как вы понимаете, задача была не из легких. Через что нам пришлось пройти, чтобы улучшить приложение, и почему мы не убежали не переписали его с нуля, расскажу дальше. Спойлер: было жестко, но все закончилось хорошо. Теперь у нас есть все основания утверждать, что работа над «внутренностями» Android — это высшая лига.

https://habr.com/ru/companies/yadro/articles/1031314/

#android #kvadraos #операционные_системы #софт #разработка_мобильных_приложений #системные_настройки #планшеты #легасикод #xml #приложения_для_android

XML Resolver version 6.0.23. Closing in on 6.1, this release exercises the new build infrastructure, mitigates a couple of Microsoft CVEs in the C# resolver, and adds support for “new” HTTP status codes in the Java resolver. #XML #XMLResolver #Java #MarkupMonday

https://so.nwalsh.com/2026/05/04-xmlresolver

Fuck it! We'll do it live!

#owncast #streaming #twitter #xml #antifa

https://live.ianandjayspaceout.com

RSS, ATOM, and JSON feeds may be getting a much-needed update to the spec with the addition of Byline, which provides structured identity (AKA: author details) for syndication feeds.

The proposal was created by @tg, maker of the popular Current RSS reader.

https://coywolf.com/notes/adding-author-context-to-rss/

#RSS #XML #OpenWeb #WebStandards

So for some time now, I write most of the stuff I do in #HTML. In my own dialect of HTML, in fact <https://aartaka.me/pidgin.html>

And I keep noticing things that HTML editing can be. And that #Emacs—my editor of choice—does not allow (yet?) Here’s a bucket list of what I want to have in my HTML editor:

• Navigation between headings, sections, lists, and links. Quick opening of links.

• Section collapsing. Has to be smart, to handle both semantic <section>-s and raw paragraphs+headings documents.

• Table column alignment.

• Proper implied closing tags <https://html.spec.whatwg.org/#closing-elements-that-have-implied-end-tags> support. Emacs has some, but not all of them, which is annoying.

• Connected to the previous point: meaningful and configurable indentation.

• Inline styling of elements, whenever possible and meaningful. Maybe even input rendering? Emacs does some styling, but _not enough_, and it’s too restricted by proportional monospace paradigm to go all-out with styling.

• Templates. This is covered by snippet systems, like Emacs’ Yasnippet, but I’m yet to write the necessary templates for my particular workflows.

• Seamless #CSS and #JavaScript support. This is a problem for Emacs, because of its language = mode paradigm. There are three languages and only one mode.

• EDIT: And good keyboard support, with _everything_ accessible via keyboard. I forgot to include this point because I was privileged using Emacs for years now.

EDIT 2: Structural editing, with moving whole regions at once without invalidating the DOM.

Some of that is covered by #XML editors, some by Emacs, some by other editors (don’t even mention #VSCode—it sucks!) but none—by one editor.

I wrote a practical PHP guide: How to Parse Large XML Files in PHP Without Running Out of Memory
It focuses on large XML files, memory safety, XMLReader baseline, selected-node extraction, XML-to-array output.
https://dev.to/sbwerewolf/how-to-parse-large-xml-files-in-php-without-running-out-of-memory-234o

The pattern is intentionally boring: stream XML with XMLReader, match the records you need, convert them into plain PHP arrays, and keep application code away from cursor-level XML logic.
#PHP #XMLReader #ETL #XML #OpenSource