yeah it uses this really neat semantic rendering programming language for serving structured documents across servers
It’s a bit tricky, but anyone with at least a Masters in CompSci should be able to parse some of it enough to get the gist. Bear in mind that the “source” is abbreviated to src, and “image” similarly. The rest is coding that gives the computer instructions, you’ll also need to replace FILENAME in the code with the actual filename. It goes like this
yeah it uses this really neat semantic rendering programming language for serving structured documents across servers
It’s a bit tricky, but anyone with at least a Masters in CompSci should be able to parse some of it enough to get the gist. Bear in mind that the “source” is abbreviated to src, and “image” similarly. The rest is coding that gives the computer instructions, you’ll also need to replace FILENAME in the code with the actual filename. It goes like this
<img src="FILENAME" />Let me know if I can explain it more clearly.
I feel like the level of snark in your reply is… High. It doesn’t make for a pleasant interaction, and it doesn’t help make lemmy a nice place to be.
So, if the image you want to put into your email is not hosted somewhere, what’s the best way to go about this, ensuring compatibility?
You can base64-encode the image file. It’s super-jank, but it works, even in Outlook.
Example: https://www.base64-image.de/tutorial