Right now the version stamps are a bit of a mess – when minting a new release we must manually update the version number in the source .md file, in the source .afpub file and in the typeset .pdf version. This is too easy to get wrong (as witnessed by mismatched version stamps in some of the releases).
As for the Markdown version, that’s trivially solved by using a version placeholder in the source and replacing it during the release process automatically. But can we do the same with the typeset PDF version? (PDFtk?)
Tried pdftk, the “uncompressed” version of the PDF is still a load of binary garbage, so sed doesn’t work. Tried qpdf, similar story. No plan B at the moment, maybe we’ll think of something later.
Right now the version stamps are a bit of a mess – when minting a new release we must manually update the version number in the source .md file, in the source .afpub file and in the typeset .pdf version. This is too easy to get wrong (as witnessed by mismatched version stamps in some of the releases).
As for the Markdown version, that’s trivially solved by using a version placeholder in the source and replacing it during the release process automatically. But can we do the same with the typeset PDF version? (PDFtk?)