I guess that might work. I’ll have to try it on monday though it’s probably more effort this way compared to just doing it manually since the snippets I have to add currently are mostly single functions with less than 20 lines

Unfortunately not because the word document is meant to be the “master” document. We aren’t even supposed to export PDF versions because in the future people may see the PDF in the folder and use that as a reference instead of the main word document even though the word doc was updated and the PDF wasn’t. Also I tried pandoc md conversion to docx in the past for another document and it didn’t go very well. The formatting of the headers was all over the place which made it impossible to generate the Table of Contents in word

I’m not very well informed on the specifics of the DLNA standard or how it is differentiated from UPnP so take what I say here with a grain of salt. My understanding is that there are 3 device types in DLNA

• A server which provides media
• A client which can pull media from the server
• A renderer which can play back media from the client

I’m not sure if the server is necessary stricly speaking or if my device is using the underlying UPnP stuff but I can use Macast, which is a DLNA renderer, on my desktop computer and then select it as a playback device in Symfonium on my android phone where it shows up as a UPnP device.

That might work. I’ll have to check it out. Thanks

I’ve used macast in the past on my desktop where it worked perfectly. Unfortunately I could not find a fitting docker image for it. There is this one but it has literally no information and only 70 image pulls. Then there is a dockerfile in the Macast github repo but considering I don’t see a docker image mentioned anywhere in the documentation so I guess that one is only for building the application. I believe Macast is a GUI application anyway so I’m not sure how good it would work on a headless server.

I was under the impression that minidlna is exclusively a DLNA server and not a renderer. Is that wrong?

The code snippets are the worst part. God forbid I ever have to update them because I have to manually indent every line in them correctly

Oh yes definitely. I currently have to write the technical documentation for a project I am working on in MS Word because that’s the format my supervisor wants (since everyone in the organisation already has word installed by default and knows how to use it at least somewhat). Probably a quarter of the time I spend writing is lost to fighting the formatting in word. I managed to have stuff happen that my coworkers have never seen word do before like taking the content of all my textfields (which I use for pasting code snippets) and having it duplicated inside each textfield…

I wished I could use LaTeX for it but I understand the argument that some people after me may have to work on the project who don’t know LaTeX.

I’m gonna upvote the git + plain markdown solution simply because it is a very basic solution that does not depend on a lot of specific software in case you want to switch in the future. I had a look at obsidian in the past but discarded that idea because it required a license for commercial use back then which it seems they either changed or I misread the terms at the time.

Still I am a fan of going as low-tech as possible with note formats so that I can easily hand down my notes to whoever comes after me and they won’t need a special program to open anything.

Quarto looks nice and would be something I would look into if I did more data heavy work. As it is I only write technical notes and documentation for software for which plain markdown is perfectly suitable.

Not a valid option if you are looking specifically for lossless music