Bei der #DocBook-Customization mal geschaut, ob sich etwas beim wichtigen result-Element innerhalb einer procedure getan hat. Leider noch immer nicht.

Aber das habe ich ja bereits gelöst. da gerade im Studi-Erklärkontext inakzeptabel.

I created #CSL #CitationStyleLanguage in the early 2000s, because what I was looking for didn't exist. In fact, I wrote the prototype #XSLT implementation to format my first book manuscript, using #DocBook!

Since then, it's been wildly successful, but the technology world has evolved a lot since, and CSL has accrued almost 20 years of technical debt.

So I've been experimenting lately with what an alternative, designed today, might look like.

I created #CSL/#CitationStyleLanguage in the early 2000s, because what I was looking for didn't exist. In fact, I wrote the prototype #XSLT implementation to format my first book manuscript, using #DocBook!

Since then, it's been wildly successful, but the technology world has evolved a lot since, and CSL has accrued almost 20 years of technical debt.

So I've been experimenting lately with what an alternative, designed today, might look like.

@AdamBishop If I compare it to the standard "out of the box" text editor that we have on macOS, it works extremely well with #XML files (finds errors, etc.) I use it all the time to check weird #TMX data for ex.

It's also not too bad at editing/authoring such XML files and so I used it to rewrite the #DocBook sources of OmegaT's manual for ex., for that, it comes with tag completion, syntax coloring, etc.

So, that's something I really could not do with that standard macOS text editor.

If I compare it with the defacto pro-editor on macOS (#BBEdit), it comes with less fun regex but everything I mentioned above stands.

But then, it comes with a really nice writing environment called "org-mode" (modes are basically #emacslisp applications within Emacs and do all sort of things that a bare bones text editor can't do). I use org-mode all the time to write. org-mode comes with something that "captures" notes so that you can just write down stuff that come to your mind and store that in a side "location" without losing your focus, and then you can reorganize all your stuff when you have time.

If you come from VI, you have a VI typing mode with all the VI shortcuts, if you come from Windows, you have something like that too.

Think of it as a lisp virtual machine that comes with an editor and a thousand applications that deal with textual data (but not only).

@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.

"#Antiword" is a command line program that can read the proprietary "doc" format (not docx) used by old MS Word versions. Pandoc and antiword can be combined via #DocBook XML; this offers a way to convert old doc files:

antiword -x db input.doc | pandoc -f docbook …

I think I've managed to (better) sort out media objects in #DocBook #xslTNG. Except now #XSpec crashes because there's no context node when the tests run. I'm going to leave that for another day.

@donwatkins
I also love #DocBook, even if I'm (still) struggling in setting up a proper toolchain in Windows WSL (not much a Linux expert anymore).

Referring to external media files from XML. Mapping from references in source XML to media locations on disk, and then generating HTML with the correct references to media on a web server is…a little tricky. #DocBook #XML

https://so.nwalsh.com/2023/01/26-media

DocBook xslTNG prerelease version 2.0.1 is out. I pushed this one to Maven as well, for my own convenience as much as anything else. I think I'm done with the major hacking and slashing, but I guess I should wait for the bug reports before I say that out loud.

#DocBook #xslTNG #XSLT

DocBook xslTNG stylesheets version 2.0.0 (experimental). Rewrote localization. ✔ Appears to support Chinese now. ✔ All tests pass. ✔ Wrote some new localization tests. ✔ Updated documentation. ✔ Published release. ✔ Still 2022. ✔ Win. ✔✔✔ https://so.nwalsh.com/2022/12/30-xslTNG-200

Reports from the field eagerly solicited. Open a bug if you have trouble. On the one hand, there are a lot of changes, on the other I expect relatively few people actually make localization changes, so...

#DocBook #xslTNG

Zero failing tests. Now I can go back to writing documentation so I know what to break next 😜 #xslTNG #DocBook

This morning, 106 failing tests. Now, 8 failing tests. Bonus: for some failing tests, the new output is in fact better than the old output. #xslTNG #DocBook

I didn't know that DocBook's <warning> tag could contain <title>. Turns out it's pretty neat.

#PostgreSQL #docbook

All the #DocBook #xslTNG tests pass. Now just have to see if/how customization layers can modify generated text, check all 74 non-English language localization files (as best I can), write the documentation, and check on a performance regression. Not going to finish this weekend.

I am officially not having fun anymore. "78 failing tests." #DocBook #xslTNG #L10N

On the minus side, fixing the mess I made of localizing generated text in #DocBook has turned into something larger and more difficult than I expected. On the plus side, I probably have something I can turn into a #Balisage paper submission for next year.

@samwilson @atomicpoet
I really like it. The basics are close enough to #Markdown in terms of simplicity (although sometimes slightly different, that can create confusion when you switch between the two), but being designed as a “lightweight #docbook” it's very complete.

#DocBook 5 にも微妙な顔になる点はあるにはあって、たとえば ooclass, ooexception, oointerface など互換性のために残されている、時代を感じさせる要素などがある

oointerface
https://tdg.docbook.org/tdg/5.2/oointerface.html

> oointerface — An interface in an object-oriented programming language.

screen
https://tdg.docbook.org/tdg/5.2/screen.html

あと #DocBook 5 には screen 要素というのがあって、たとえばこれはスクショ等以外にもコンソールのログを表現したりなどにも使える。デザインが圧倒的に “正しい”。
コンソールのログ自体は一般にコードでも何でもないのだから、本来 code block 用の仕組みを使うべきではないんだよな。