https://pjotrek-b.github.io/Knowledge/doxygen_omekas
Put a pre-rendered copy of a freshly generated #OmekaS source code documentation in HTML.
https://pjotrek-b.github.io/Knowledge/doxygen_omekas
Put a pre-rendered copy of a freshly generated #OmekaS source code documentation in HTML.
Is there any way to convince Doxygen to use properly structured HTML tags?
By default Doxygen:
- Uses <div class="title"> instead of <h1> (and <h1> instead of <h2> etc.)
- Images are weird: They are placed in <div class="image">, and a <div class="caption"> (HTML has <figure> and <figcaption for this!) is used for the caption.
- All images have alt="", and the Alt-Text from Markdown is used as a caption instead.
Recently, we talked about #libid3tag and our intent to make a new release. So far, we have a preview of some changes that have already been made in the latest main:
- Mojibake fixes for #UTF-16 (no BOM) encoded fields.
- Some code cleanups, including warning fixes.
- Compatibility with #CMake > 4.0 (we now require CMake 3.10+)
Meanwhile, we are also working on #Doxygen documentation to better document the library too, so quite a few things are going on for libid3tag right now.
@raiderrobert Using #Doxygen, set to estract all. Gives you a nice, clickable HTML version of the code, with inheritance and usage diagrams.
I'm working on a project which includes files written in both C and #Lisp; I'd like to have a common documentation generator for the whole project, to generate integrated documentation.
Has anyone made #Doxygen work with Lisp? Are there any recommendations for a documentation generator which can work for both (and also Markdown, which is what my specification docs are written in?
Having to deprecate a part of #poser's API for the first time, I added support for the #deprecated attribute supported by #GCC and #clang and then found #Doxygen couldn't automatically use it.
I didn't want to document deprecation *twice*, so I came up with a little hackery, see screenshots. 🙈
It's not perfect, requiring to type the message in plain text as a macro argument forbids the usage of a comma 😉 But hey, it works!
All new files my old `btrfs` filesystem creates are above 32-bit inode space:
$ touch a && stat '-c%i' a
11833717710
Very occasionally I build 32-bit `i686-linux` packages. Sometimes they fail to run against file with so large inodes.
Two casualties today:
- `doxygen`: https://github.com/doxygen/doxygen/pull/11518
- `graphviz`: https://gitlab.com/graphviz/graphviz/-/merge_requests/4269
🚀 New release for OpenYuusha! Mostly gruntwork... but LOOK MA, AN OPEN FILE WINDOW! And some pretty documentation for the underlying library... 🌺
https://gitlab.com/lenaing/open-yuusha/-/blob/main/CHANGELOG.md#010-alpha2---2024-12-07
#imgui #doxygen #reverseengineering #cppdev #meson #rpgmaker95 #rpgmaker
The @kde community has an ongoing effort to port its documentation from Doxygen to QDoc, and you can help with that.
Join us tomorrow (14/11) starting at 1PM (UTC) at: https://matrix.to/#/!KfwuSDyCBkcbRESeSA:kde.org?via=kde.org&via=matrix.org&via=private.coffee
More info:
https://blogs.kde.org/2024/11/13/api-documentation-porting-sprint/