Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit dc059560e73e0b373a6e54e71b07e3af4b692cb4.
I changed my mind. There's no harm in leaving it deprecated for a
release cycle.
|
|
See ChangeLog for rationale for not deprecating it as originally
planned.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The PDF spec only allows UTF-16BE, but most readers seem to accept
UTF-16LE as well, so now qpdf does too.
|
|
This was unintended behavior that was added back for backward
compatibility. It is intentionally undocumented.
|
|
There are codepoints in PDFDoc that are not valid UTF-8 but map to
valid UTF-8. We were handling those correctly with bidirectional
mapping.
However, if those same code points appeared in UTF-8, where they have
no meaning, they were left as fixed points when converting to PDFDoc,
where they do have meaning. This change recognizes them as errors.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Don't surprise people with deprecation warnings
* Provide detailed instructions and support for the transition
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Use unique_ptr in place of shared_ptr in some cases
* unique_ptr for arrays does not require a custom deleter
* use std::make_unique (c++14) where possible
|
|
|