#dita — Public Fediverse posts

Allein #SVG und #MathML sind relevante Browser-basierte #XML-Technologien. #RSS / #Atom existieren ebenfalls.

#XSLT lebt auf dem Server weiter und hat in Version 3.0 (bald 4.0) primär für lokal angesiedelte Prozesse der Dokumentverarbeitung (#DITA, #DocBook, #TEI) eine ungebrochene Bedeutung. Zudem steht mit #SaxonJS eine Browser-Alternative zur Verfügung.

Pensionierte XMLer werden bestimmt ebenso gefragt sein wie im Fall von #COBOL.

Allein #SVG und #MathML sind relevante Browser-basierte #XML-Technologien. #RSS / #Atom existieren ebenfalls.

#XSLT lebt auf dem Server weiter und hat in Version 3.0 (bald 4.0) primär für lokal angesiedelte Prozesse der Dokumentverarbeitung (#DITA, #DocBook, #TEI) eine ungebrochene Bedeutung. Zudem steht mit #SaxonJS eine Browser-Alternative zur Verfügung.

Pensionierte XMLer werden bestimmt ebenso gefragt sein wie im Fall von #COBOL.

Allein #SVG und #MathML sind relevante Browser-basierte #XML-Technologien. #RSS / #Atom existieren ebenfalls.

#XSLT lebt auf dem Server weiter und hat in Version 3.0 (bald 4.0) primär für lokal angesiedelte Prozesse der Dokumentverarbeitung (#DITA, #DocBook, #TEI) eine ungebrochene Bedeutung. Zudem steht mit #SaxonJS eine Browser-Alternative zur Verfügung.

Pensionierte XMLer werden bestimmt ebenso gefragt sein wie im Fall von #COBOL.

Allein #SVG und #MathML sind relevante Browser-basierte #XML-Technologien. #RSS / #Atom existieren ebenfalls.

#XSLT lebt auf dem Server weiter und hat in Version 3.0 (bald 4.0) primär für lokal angesiedelte Prozesse der Dokumentverarbeitung (#DITA, #DocBook, #TEI) eine ungebrochene Bedeutung. Zudem steht mit #SaxonJS eine Browser-Alternative zur Verfügung.

Pensionierte XMLer werden bestimmt ebenso gefragt sein wie im Fall von #COBOL.

Allein #SVG und #MathML sind relevante Browser-basierte #XML-Technologien. #RSS / #Atom existieren ebenfalls.

#XSLT lebt auf dem Server weiter und hat in Version 3.0 (bald 4.0) primär für lokal angesiedelte Prozesse der Dokumentverarbeitung (#DITA, #DocBook, #TEI) eine ungebrochene Bedeutung. Zudem steht mit #SaxonJS eine Browser-Alternative zur Verfügung.

Pensionierte XMLer werden bestimmt ebenso gefragt sein wie im Fall von #COBOL.

https://www.europesays.com/it/425533/ Claudio Bisio commissario guascone in «Uno sbirro in Appennino», «ma non amo le divise» #amaranta #appennino #aprile #bisio #celotto #chiara #ChiaraCelotto #claudio #ClaudioBisio #commissario #dario #De #DeMaria #dita #divise #Entertainment #guascone #Intrattenimento #investigatore #IT #Italia #Italy #maria #nascita #nuova #NuovaSerie #paesino #personaggio #pur #Rai #renato #sbirro

so they ask me, shit you not, to "break the PDFs up into chunks" below the max input size of the #ai #llm model they're using.

"uh . no."

_Well, you're not being a team player_

"It's not that, it is an inefficient use of my time++. Give me a co-op or.. and this is much preferred.. I'll give the #dita source (or I can do #HTML or #Word or any other output that doesn't have an input limit) and the model can read that."

++unless your time is worth more than my time in which case: fuck you.

@divclassbutton Another vote here for Oxygen XML Editor. I haven’t worked much with DocBook, but I know #DITA well. That program is geared towards XML-based docs and development and makes life much easier.

So the time has come for me to write some proper documentation for xrust... does anyone have a recommendation for #docbook or #DITA editing? Not sure which to go with yet, my #XML knowledge is from the finance world. 😅

Would like to output some static files for hosting.

Trying to decide which feature I should next implement on DITA Langauge Server and I really don't want to tackle find keyrefs feature. Crawling all linked files is expensive, even with caching and using regexp. #dls #dita

Perde tre #dita per un #petardo, torna a ferirsi coi #fuochi

https://www.larampa.news/2026/01/perde-tre-dita-petardo-esce-ospedale-ferisce-nuovamente-napoli/

Фильтруй. Переиспользуй. Собирай. Почему DITA — идеальный формат для разработки сложной технической документации

Формат DITA позволяет полностью сосредоточиться на содержании документа и не думать о его оформлении. Кроме того, этот инструмент помогает легко и быстро вносить изменения и дополнения в уже написанные ранее документы. Если с DITA как следует разобраться, то потом написание сложных технических документов существенно упростится. В этой статье я расскажу об основных достоинствах DITA.

https://habr.com/ru/companies/bercut/articles/951260/

#dita #dita_open_toolkit #документация #технический_писатель #пользовательская_документация #xml #форматы_документов #docascode #техническая_документация #bercut

Seems legit... I've started to use it and it has been a great help when browsing a huge Git repository Vs doing the same over OxigenXML.

"DitaCraft is a lightweight extension that brings DITA support directly into VS Code, one of the most popular code editors. It provides:

- Syntax highlighting for .dita, .ditamap, and .bookmap files.
Real-time validation against DITA 1.3 standards.
- Seamless integration with DITA-OT for multi-format publishing (HTML5, PDF, EPUB, and more).
- Smart navigation, live preview, and 21 code snippets to generate bookmap, ditamap,topic templates.

Whether you’re a technical writer, developer, or student, DitaCraft helps you focus on learning DITA — without the complexity.
(...)
Who Is DitaCraft For?

- Beginners who want to learn DITA without the complexity of professional tools.

- Developers who need a lightweight DITA editor integrated into VS Code.

- Students exploring structured authoring and technical documentation.

- Technical writers who want a free, open-source alternative for quick edits and validation.

The Future of DitaCraft

DitaCraft is an ongoing project, and I welcome contributions from the community! Whether you’re a DITA expert or a beginner, your feedback and ideas can help shape the future of this tool.

Try DitaCraft today and simplify your DITA journey! 🔗 Install DitaCraft from the VS Code Marketplace"

https://medium.com/@jyjeanne/ditacraft-a-beginner-friendly-vs-code-extension-for-dita-authoring-and-publishing-13de279b69e5

#DITA #DITAXML #XML #VSCode #VisualStudioCode #StructuredWriting #TechnicalWriting #DitaCraft

Yep, DITA XML is still rocking in the technical communication world and technical writers need to have at least some familiarity with the topic.

https://learningdita.com/pluginfile.php/1/tool_certificate/issues/1762964073/6088999983MC.pdf

#DITA #DITAXML #TechnicalWriting #TechnicalCommunication #StructuredWriting

#TechnicalWriting #SoftwareDocumentation #Markdown #XML #DITA: "Think about how in Markdown you would ensure that “all our how-to guides must have an h1 title, followed by one or more paragraphs, followed by one or more steps to achieve the guide’s goal”, and then consider how easy it is in DITA.

This is just not really possible today, at least in any popular Markdown-based framework.

There is a path
Bridging the gap between Markdown and structured authoring will require building new tooling and standards. It’s unlikely that CommonMark or any other popular Markdown flavor would consider going in this direction, so we’ll have to create tools around Markdown.

We at Doctave have some ideas about how to achieve this, and have a roadmap on how to get there. At a high level there are a few things we would need:

✅ A parser and template system that is Markdown-aware
❌ A language for describing constraints and rules for your Markdown content
❌ An engine that enforces those rules on your content
We’re already part of the way there!"

https://www.doctave.com/blog/path-to-structured-markdown

#TechnicalWriting #DITA #XML #DITAXML #Documentation #InformationArchitecture #StructuredAuthoring: "DITA is defined in its specification as “an XML-based architecture for authoring, producing, and delivering topic-oriented, information-typed content that can be reused and single-sourced in a variety of ways”. Originally developed by IBM in the early 2000s, DITA stands for Darwin Information Typing Architecture. “Darwin” refers to the naturalist Charles Darwin and his theory of evolution, reflecting DITA’s principles of specialization, inheritance, and adaptation.

DITA topics are standalone, context-free blocks of content, with content types kept clearly separate. There are three main topic types in DITA, all of which are inherited from the base topic type <topic>:

<concept>: background information that users must know before using the product

<task>: step-by-step instructions that users need to perform a task

<reference>: product specifications, commands, or other reference material

You create a document by selecting which existing topics should be reused and referencing them in what’s called a DITA map (similar to a table of contents).

Being an open standard, DITA has no proprietary restrictions. But while you’re not forced to buy a specific tool to use it, commercial XML editors have many features, such as visual editing and validation, that make writing DITA content much easier."

https://mastertcloc.unistra.fr/2024/04/26/dita-xml-documentation-reasons/

Bon dia!
Benvingut abril

#educació #BuenosDías #educación #education #dita

@failedLyndonLaRouchite I use Beyond Compare for *source* comparison. As a #technicalwriter I author in #DITA which is an xml specialization; nice because I can use the same toolchains and repos as my dev teams.

And BC *can* diff PDFs almost as well as Acrobat (in some cases better), so long as you're ok with it having scraped all the text out of it to do so. Which may or may not be what you want, but in that case, y not just diff the source.

https://en.wikipedia.org/wiki/Standard_Generalized_Markup_Language#:~:text=SGML%20descended%20from%20IBM%27s,in%20%22The%20SGML%20Handbook%22.

As I possibly need to do soon something with #DITA.
DITA which is based on XML with some DTD is as like as HTML derived from SGML. In fact HTML is a simplified SGML.
I was aware that #SGML was developed at Boing. They invented it for Airplane documentation.

Today I learned that SGML is based on GML: "General Markup Language" from IBM.
But maybe simply "Golfarb, Mosher, Lorie": the #IBM engineers back in the 1960s.

Analysis: How #Czech #DITA 155mm #Howitzer Offers #Ukrainian Army New #Artillery Technology
https://www.armyrecognition.com/defense_news_march_2024_global_security_army_industry/analysis_how_czech_dita_155mm_howitzer_to_offer_ukrainian_army_new_artillery_technology.html @excaliburarmycz

#bot #miltodon
Original tweet: https://nitter.x86-64-unknown-linux-gnu.zip/ArmyRecognition/status/1767245020434780295

#TechnicalWriting #SoftwareDocumentation #DITA #CCMS: "Whether we are talking about technology, governments, business, culture, or the environment – we live in a world of constant change. In our field of work, many of us see changes impact our documentation on a weekly, if not daily, basis. To keep pace with these changes and maximize content reuse, it has become standard practice to employ some form of topic-based authoring tool.

However, when technical communication professionals consider their content authoring and management strategies, the best solution is not always clear. Does it require a component content management system (CCMS) based on the Darwin Information Type Architecture (DITA)? Or will a more general solution for topic-based authoring provide the necessary features?"

https://tcworld.info/e-magazine/intelligent-information/dita-vs-topic-based-authoring-systems-1301/

#TechnicalWriting #DITA #Markdown #SoftwareDocumentation: "Moving from DITA (Darwin Information Typing Architecture) to Markdown for technical documentation involves weighing several benefits and risks, which are pertinent to the specific needs and workflow of technical writers

While Markdown offers notable advantages in terms of productivity, collaboration, and alignment with modern development workflows, it also presents significant challenges in content structure, scalability, and feature richness.

Technical writers must be prepared to navigate the less-structured environment of Markdown and may need to employ additional tools and practices to compensate for the loss of certain key capabilities inherent in DITA’s more complex system.

The decision to transition should therefore be made with a thorough understanding of these trade-offs and an assessment of the specific needs of the documentation project.

Let’s dive in."

https://www.ihearttechnicalwriting.com/2024/01/08/what-are-benefits-of-adopting-markdown-v-dita-for-technical-documentation/

Neues Video: Kompakte Grundlagen zum Thema #DITA aus einer im Sommersemester 2021 online gehaltenen Vorlesung. https://vimeo.com/910787929

Öffnet man Dokumente in Formaten wie #DocBook und #DITA im <oXygen/> #XML Editor, wechselt dieser in den nicht unbedingt intuitiv nutzbaren Author-Modus. Das hat Studis in der gestrigen Übung irritiert: da kommt so eine komische Word-Oberfläche.

Direkt in den Text-Modus, also zum Code, wäre besser. Der Author-Modus bietet sich eher an, um mal individuelle Formatierungen oder Tabellen einzufügen, wobei ich lieber ein <emphasis role="bold">Text</emphasis> tippe als einen B-Button zu bedienen.

#Writerside bietet einen Single-Source-Publishing-Ansatz mit einem eigenen Vokabular. Dabei sind aus #DocBook bekannte Elemente wie <chapter>, <procedure> und <topic> analog zu #DITA. https://www.jetbrains.com/help/writerside/markup-reference.html

Wenn man etwas komplett neu dokumentieren möchte, vielleicht ein zielführender Ansatz. Geprägt durch die lange Erfahrung mit DocBook und DITA für mich aber auch eine Neuerfindung des Rades und eben neuer Einarbeitungsaufwand nötig.

https://www.jetbrains.com/writerside/

Looks interesting, but no #docbook? No #DITA? Bizarre.

We released DITA-OT 4.1.2 the other day. See https://www.dita-ot.org/4.1/release-notes/#v4.1.2 for details.

I fixed a bug that was likely already in 1.0, so it may have been an 18 year old bug 😳

#dita #ditaXml #ditaOt

New blog post: A Couple of Free Writing Tools. The ebook converter is something that I want to try out. If anyone has used it and has comments, please leave a reply.

https://coredump3.blogspot.com/2023/04/a-couple-of-free-writing-tools.html

#dita #techcomm #ebooks

Been learning DITA for work. For most of my career I've just used Word or Google Docs. It's igniting my imposter syndrome for sure. #DITA #techwriter

I might be a little late to this, seeing as I've been writing in DITA for a decade, but this morning I'm finally getting around to learning syntax diagrams.

#dita #technicalwriting

@colepeters @remotesynth

There are parallels here for tech writers too, with #FrameMaker, #DocBook, #AsciiDoc, #ReStructuredText or #DITA.

Each tool we learn teaches us something about the others.

Released Lightweight DITA plug-in 4.0 for DITA-OT https://github.com/jelovirt/org.lwdita/releases/tag/4.0.0 #Dita #LwDita #DitaOT

Buon Anno Nuovo a tutti con una raccomandazione: cerchiamo di non dare troppi snack ai volatili, ragazzi...

#vignetta #rapaci #umorismo #humor #capodanno #botti #petardi #mani #dita #pericolo #bastardidentro