| Age | Commit message (Collapse) | Author |
|---|
|
Change-Id: I326ba676730268808f60e0593a5e7f813b503977
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/143097
Tested-by: Jenkins
Reviewed-by: Xisco Fauli <xiscofauli@libreoffice.org>
|
|
> [_RUN_____] testPDFAddVisibleSignatureLastPage::TestBody
[...]
> warn:sal.osl:2861871:2861910:sal/osl/unx/process.cxx:343: ChildStatusProc : starting '.../instdir/program/xpdfimport' failed
> warn:sal.osl:2861871:2861910:sal/osl/unx/process.cxx:344: Failed to launch child process, child reports ENOENT
> warn:sdext.pdfimport:2861871:2861871:sdext/source/pdfimport/wrapper/wrapper.cxx:1090: executeProcess of file:///.../instdir/program/xpdfimport failed with 4
when building CppunitTest_vcl_filter_ipdf from scratch
Change-Id: Id155ee09eb90b4bfb0416ffa458554a126db9747
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/132334
Tested-by: Jenkins
Reviewed-by: Stephan Bergmann <sbergman@redhat.com>
|
|
PDFDocument::Sign() had this hardcoded to always place the signature
widget on the first page, add a way so that xmlsecurity/ can tell the
pdf signing code to put it on an other page.
This way in case the user created the signature line shape on the Nth
page, it'll end up on the Nth page of the PDF result as well, as
expected.
Change-Id: I63decba98774151e9634ea924c2fed0f7814cb28
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/97045
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
Tested-by: Jenkins
|
