The focus of this release is the pdfcpu config dir.
This dir contains
config.yml which represents the current default configuration.
config.yml will be loaded on restarting pdfcpu either via the API or the CLI.
You can find out about the location of the config dir via
pdfcpu version -v
Since there seem to be usecases where it makes sense to bypass the config dir
you can pass the new flag
-config disable into any call executed on the cmd line
and in your Go backend you may call
api.DisableConfigDir() to achieve the same.
Just a friendly reminder that in such a scenario user fonts (possibly for stamping) are not available.
You can also pass a custom path to an existing directory like in
and pdfcpu will create a
pdfcpu config dir within. Like this you can manage multiple config dirs.
Just make sure you pass the corresponding config dir you'd like to use before your pdfcpu operation.
. ├── config.yml └── fonts ├── Geneva.gob ├── OldTypewriter.gob └── Roboto-Regular.gob
The config dir also contains a dir called
fonts which is the home for user fonts installed via eg.
pdfcpu fonts install abc.ttf
More about this in the next release which will be all about fonts.
Thank you all for reporting bugs and filing issues.
Stay tuned and happy coding 💚
67f0c34 Add low level test for collect
e77e4e4 Add low level test for split
4f10ad0 Fix #218
9328d3b Fix #220
7a20978 Fix #221
f5a85ae Fix #222
113adaf Fix #223
4c18535 Fix #224
6b2e3b4 Fix #231, #232, bump version
d8572c7 Fix attachment literal creations
218a002 Handle config dir & introduce config.yml