...it gives a bit of history and behind the scenes of something that is trivial to consume (book, website), but technical to produce.
My grandpa had his own printing company back in the day, and that was one of the the original broadcast technologies. Books, periodicals, businesses, menus, invitations, professional directories... they all filtered through one of the local printing presses.
Practically as well, you'd take a million individual letter pieces, arrange them into plates with pressure-fit clamps, then run 1000 (or more) copies of each page or whatever. https://en.wikipedia.org/wiki/Hot_metal_typesetting
For bigger runs, they'd "lock" the page into slugs (lines of text) or plates (full pages).
At the end of the job, they'd melt the plates back down, so the colophon could also be considered "hey, this is how you reproduce it for the second printing run... it was Garamond, not Baskerville, and 25% cotton paper, not bond."
In a way, the colophon contains the original spirit of open source, and "opening the HTML pages to see how it's done."
mananaysiempre 4 days ago [-]
Fun tidbit: all videos encoded by x264 (ETA: x264 not ffmpeg) contain the settings used by the encoder. The user can of course strip them after the fact or patch the code out of their build, but the upstream maintainers have insisted on leaving it in.
NoMoreNicksLeft 4 days ago [-]
What's the command to extract those flags? Was it always there and I just didn't notice?
mananaysiempre 4 days ago [-]
Sorry, I was misremembering on two counts: it’s x264 that does this, not ffmpeg (but you’re using x264 if you’re making H.264 with ffmpeg); and the info is the encoder’s actual settings, not the flags (so a preset like “veryslow” will get expanded). With those caveats, the information is displayed for example by mediainfo under “Encoding settings”.
tiffanyh 4 days ago [-]
> it gives a bit of history and behind the scenes of something that is trivial to consume (book, website), but technical to produce.
For a website, how does a Colophon page differ from an “About” page?
...it gives a bit of history and behind the scenes of something that is trivial to consume (book, website), but technical to produce.
My grandpa had his own printing company back in the day, and that was one of the the original broadcast technologies. Books, periodicals, businesses, menus, invitations, professional directories... they all filtered through one of the local printing presses.
Practically as well, you'd take a million individual letter pieces, arrange them into plates with pressure-fit clamps, then run 1000 (or more) copies of each page or whatever. https://en.wikipedia.org/wiki/Hot_metal_typesetting
For bigger runs, they'd "lock" the page into slugs (lines of text) or plates (full pages).
At the end of the job, they'd melt the plates back down, so the colophon could also be considered "hey, this is how you reproduce it for the second printing run... it was Garamond, not Baskerville, and 25% cotton paper, not bond."
In a way, the colophon contains the original spirit of open source, and "opening the HTML pages to see how it's done."
For a website, how does a Colophon page differ from an “About” page?
...the wiki link talks a little bit about "website colophons" as well.