Console View
|
|
|
|||
|
Albert Astals Cid
aacid@kde.org |
|
||
| poppler 24.12.0 | |||
|
Sune Vuorela
sune@vuorela.dk |
|
||
| Form: fclose file on signature error | |||
|
Albert Astals Cid
aacid@kde.org |
|
||
| Update (C) | |||
|
Sune Vuorela
sune@vuorela.dk |
|
||
|
Mark certificates that can do qualified signing Certain signatures can do qualified signing (legally binding). Ensure that they can be properly tagged in various UI's. |
|||
|
Lucas Baudin
lucas.baudin@ensae.fr |
|
||
| Generate appearance stream for annotation stamp when it is not available (i.e. was invalidated), taking into account the custom image case | |||
|
Sune Vuorela
sune@vuorela.dk |
|
||
| CryptoSign: Allow backends to support different signature types | |||
|
Albert Astals Cid
aacid@kde.org |
|
||
| Update (C) | |||
|
Sune Vuorela
sune@vuorela.dk |
|
||
|
pdfsig.1: Extend GPG backend documentation closes: #1535 |
|||
|
Nelson Benítez León
nbenitezl@gmail.com |
|
||
|
Parser.cc: remove superfluous condition inside 'if' getObj() checks recursionLimit and returns ObjError if reached, so in that case both obj2.isError() and "recursion + 1 >= recursionLimit" are true, but that also means that obj2.isError() is superfluous in the 'if' statement, because if "recursion + 1 >= recursionLimit" is true it means previous getObj() must have returned a objError (because they use the same recursion check). Brought up here[1] [1] https://gitlab.freedesktop.org/poppler/poppler/-/issues/1508#note_2651715 |
|||
|
Albert Astals Cid
aacid@kde.org |
|
||
| Update (C) | |||
|
Sune Vuorela
sune@vuorela.dk |
|
||
| Try verify public private headers | |||
|
Pablo Correa Gómez
pabloyoyoista@postmarketos.org |
|
||
|
README: update the location of the official poppler room And inform that it's bridged to matrix |
|||
|
Nicolas Fella
nicolas.fella@gmx.de |
|
||
|
Install CryptoSignBackend header It's used from other private but installed headers |
|||
|
Sune Vuorela
sune@vuorela.dk |
|
||
|
Debug feature for cryptographic signatures While debugging, it is nice to be able to extract both signatures and the data the signature is supposed to be over. |
|||
|
Sune Vuorela
sune@vuorela.dk |
|
||
|
Better signing error handling Just having a bool for many different failure modes is a bit hard to work with, so now we have an enum for the new API, so let's extend it with some of the error possibilities |
|||
|
Sune Vuorela
sune@vuorela.dk |
|
||
| createGfx: use unique pointer for creation | |||
|
Sune Vuorela
sune@vuorela.dk |
|
||
| Signature GpgME backend: Add Kyber to switch | |||
|
Sune Vuorela
sune@vuorela.dk |
|
||
| GfxFont: memory cleanup | |||
|
Albert Astals Cid
aacid@kde.org |
|
||
|
Simplify getting the Font dict We want to both get the Dict object and if it is a Ref, get its ref because we use it later. Previously we did lookup the Font Object from the dict without fetching (NF), and if it was a Ref, we had to fetch to get the actual Dict, and if it was a Dict then all was good. New code uses the "new" lookup function that returns the Ref as an output parameter, so we are doing exactly the same but the code is much simpler |
|||
|
Albert Astals Cid
aacid@kde.org |
|
||
| Update (C) | |||
|
Oliver Sander
oliver.sander@tu-dresden.de |
|
||
| GfxFontDict: Constify a pointer argument | |||
|
Oliver Sander
oliver.sander@tu-dresden.de |
|
||
| Gfx.cc: Reduce scope of local variable | |||
|
Oliver Sander
oliver.sander@tu-dresden.de |
|
||
| GfxResources: Store 'fonts' in a std::unique_ptr | |||
|
Nicolas Fella
nicolas.fella@kde.org |
|
||
|
Handle font size 0 in AnnotAppearanceBuilder::drawSignatureFieldText 0 means 'choose the size according to available space', like we do elsewhere |
|||
|
Nicolas Fella
nicolas.fella@kdab.com |
|
||
|
Set border on signature annotation before generating appearance The appearance depends on the border |
|||
|
Albert Astals Cid
aacid@kde.org |
|
||
| Update (C) | |||
|
G B
glen.browman@veeva.com |
|
||
| Override encoding for Zapf Dingbats | |||
|
Albert Astals Cid
aacid@kde.org |
|
||
| Fix build with in-tree build | |||
|
Albert Astals Cid
aacid@kde.org |
|
||
| Update (C) | |||
|
Albert Astals Cid
aacid@kde.org |
|
||
| export StructTreeRoot so we make it clear it is used/usable | |||
|
Albert Astals Cid
aacid@kde.org |
|
||
|
Install StructTreeRoot.h again I didn't realize it was usable without being exported |
|||
|
Albert Astals Cid
aacid@kde.org |
|
||
| Add a few exports more to classes that can be used from other exported classes | |||
|
Albert Astals Cid
aacid@kde.org |
|
||
|
Install SplashFont again I failed realizing it was usable |
|||
|
Albert Astals Cid
aacid@kde.org |
|
||
| Update (C) | |||
|
Albert Astals Cid
aacid@kde.org |
|
||
|
Add export to ViewerPreferences There's people sadly using this class on the wild so make it clear it's used otherwise we will make it not installed again in the future |
|||
|
Albert Astals Cid
aacid@kde.org |
|
||
|
Install ViewerPreferences again I failed realizing it was usable given it's all inline functions |
|||
|
Nelson Benítez León
nbenitezl@gmail.com |
|
||
|
cairo: Fix JPX transparency regression Commit 2dcfefb43c from https://bugs.freedesktop.org/93468 fixed images 2) and 3) of file[1] (which are jpeg images with transparency) from showing garbage to show fine but with a solid background instead of transparency. But this fix interferes with our previous commit where we are adding support to Cairo backend to correctly show transparency in jpeg files that have it. So we need to partially revert commit 2dcfefb43c but only for the Cairo backend, because the Splash backend still uses this fix to improve some jpeg transparent images by at least showing them with a solid background. So we added a new method JPXStream::setSupportJPXtransparency() so a JPXStream can be informed that the OutputDevice is capable of handling jpx transparency and so to not perform the downgrade fix to solid background. The OutputDevice itself can be marked as handling jpx transparency by new method OutputDev::supportJPXtransparency() which the Cairo backend implements as TRUE. So now file[1] does not regress in Cairo backend, although display changes from showing with solid background to show with proper transparency as CairoOutputDev now supports that. For the Splash backend no display regressions should happen at all, because any display changes are now guard by OutpuDev::supportJPXtransparency() which the Splash backend returns FALSE at this moment. [1] https://bugs.freedesktop.org/attachment.cgi?id=120624 Part of #1486 |
|||
|
Nelson Benítez León
nbenitezl@gmail.com |
|
||
|
cairo: Fix rendering of JPX images with transparency Handle transparent JPX images, they may contain RGBA data when no ColorSpace pdf dict is defined or when SMaskInData is non-zero. PDF files posted in below issues are fixed by this commit: https://gitlab.freedesktop.org/poppler/poppler/-/issues/1486 https://github.com/mozilla/pdf.js/issues/16782 https://github.com/mozilla/pdf.js/issues/11306 https://github.com/mozilla/pdf.js/issues/17416 Inspired by related fix in pdf.js: https://github.com/mozilla/pdf.js/pull/18204 While working on this commit we also succesfully addressed regressions that emerged for the following files: https://github.com/mozilla/pdf.js/issues/18896 https://bugs.freedesktop.org/attachment.cgi?id=49294 Issue #1486 |
|||
|
lbaudin1
lucas.baudin@ensae.fr |
|
||
| glib: Add free text annotations support | |||
|
Albert Astals Cid
aacid@kde.org |
|
||
| poppler 24.11.0 | |||
