Description: I have a bug where a document exported to PDF/A is not PDF/A conformant. The bug is similar to Bug 136805 (in overall result, but seems otherwise unrelated). Steps to Reproduce: We use the uno interface on a localhost socket with following filterparam filterParam.Name = "SelectPdfVersion"; filterParam.Value = Integer.valueOf(1); // 0 = PDF 1.4 (default selection). 1 = PDF/A-1 (ISO 19005-1:2005) filterParams.add(filterParam); , but the the behaviour is reproducible via GUI as well: 1. Open the attached PDF in LibreOffice 2. Choose File -> Export as PDF with PDF/A checked Actual Results: PDF is produced and metadata claim PDF/A conformance level/profile. In fact there is a problem: Specification: ISO 19005-1:2005, Clause: 6.1.12, Test number: 5 Maximum capacity of an array (in elements) is 8191 The problem can be reproduced by the VeraPDF CLI utility or using its online demo (https://demo.verapdf.org/) Expected Results: The PDF produced is really a PDF/A, passing validation checks. Note: The input file has problems of its own. It claims PDF/A conformance but it's not a PDF/A file. Never the less the output file Reproducible: Always User Profile Reset: No Additional Info: None
Created attachment 165721 [details] Input file
Created attachment 165723 [details] Export with LO 5.4.3.2
Created attachment 165724 [details] Export with LO 7.0.1
Created attachment 165725 [details] Export with PDFTron (for reference, it is PDF/A-1a compliant)
One useful information. When testing in newer version of LibreOffice (in my case 7.0.2.2) then with this setting filterParam.Name = "SelectPdfVersion"; filterParam.Value = Integer.valueOf(2); filterParams.add(filterParam); (note the change from 1 (PDF/A-1a) to 2 (PDF/A-2b) the exported PDF is really a PDF/A-2b. At least according to VeraPDF which is a good reference for start. It seems that the export problem can be constrained to case when trying to export to PDF/A-1a.
Hello, Please excuse my bad English but I am French. Looks like I have the same problem. When I try to macro export a report (base) to pdf. With "Selectpdfversion, 1", I have a pdf / A compliance error With "Selectpdfversion, 2" I have no error, but the value of form fields are not displayed. The macro I am using is as follows: Sub convertirPDF() Dim Adresse As String Dim props As Variant, propsFiltre As Variant propsFiltre = CreateProperties(Array("SelectPdfVersion",1 )) props = CreateProperties(Array("FilterName", "writer_pdf_Export", "FilterData", propsFiltre() )) Adresse = convertToURL("le chemin et le nom du fichier PDF avec l'extention") ThisComponent.storeToURL(Adresse, props()) End Sub Function CreateProperties(propList() As Variant) As Object Dim n as long, x as long n = UBound(propList) if n < 0 then CreateProperties = Array() else if (n and 1) = 0 then MsgBox("Erreur : nombre impair d'arguments", 16, "CreateProperties") else Dim p(n\2) As New com.sun.star.beans.PropertyValue for x = 0 to n\2 p(x).Name = propList(2*x) p(x).Value = propList(2*x +1) next CreateProperties = p() end if end if End Function
I confirm. Same result when selecting the A-1b profile manually from VeraPDF (LibreOffice doesn't have A-1a export profile). Arch Linux 64-bit Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 37613bffe4621c444e5a34678bafb2c3a875263d CPU threads: 8; OS: Linux 5.17; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Jumbo Built on 26 April 2022
Dear jan.prochaska, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug