I've been wishing for years that all of these codecs with hybrid lossless/lossy modes would just add a single l to their file extensions, purely for the annoyance of it.
replyLike, you can do this individually, but it's not the same thing as actually having it in the standard.
Does the L stand for lossy, or lossless? Or large, as in this case?
replyThe L in JPEG XL stands for "long-term"[1]!
replyBut people are definitely going to assume "eXtra Large". Lots of people. I guess a few will think "excel" (as in JPEG XL comes out ahead and is superior).
---
One L for Lossy, two for LossLess.
replyDoes the one at the end of .JXL count toward the total? Nobody knows what it stands for anyway.
See I would think lossless is the one you have to specify. (Also, it stops being "large" when you extend this gripe to similar formats like AVIF and WebP.)
replyAnd no, L isn't for large, we have W for that
reply(You know... for "Wumbo")
When writing GPU shaders it's not uncommon to use extensions like ".vert.glsl" = "vertex shader written in GLSL", ".frag.hlsl" = "fragment shader written in HLSL", etc.
replyMultiple extensions typically denote nested filetypes.
replyLike files.tar.xz may be decompressed with xz and then extracted with tar to get the directory "files".
I think in your case .md.fm would be a greater fit, as the front matter is read first. Or just .fmd