Description: Hello. Event reported as problem during PDF/A-1b (ISO 19005) export in Writer. Steps to Reproduce: Create an archive in the PDF/A-1b format. Actual Results: Warning message produced: "PDF/A forbids transparency.". Probably not a generality because during PDF/A-2b/3b (ISO 19005) exports this warning message is not produced. $ file -b 0.pdf PDF document, version 1.4 Expected Results: Warning message produced accordingly, therefore "PDF/A-1b (ISO 19005) forbids transparency.". Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.5.2 (X86_64); Build ID: 50(Build:2); CPU threads: 4; OS: Linux 6.4; UI render: default; VCL: gtk3; Locale: fi-FI (fi_FI.UTF-8); UI: en-US; Calc: threaded
Created attachment 189098 [details] PDF/A-1b export
Do you get this message with a blank document or only some specific one? I don't get it with a blank document. I'm not sure what the request is with your report. Arch Linux 64-bit, X11 Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 899522378bfb754af757c1a4a0f6bce699ac8721 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 21 September 2023
Reading you, I know I should feel lucky that I'm not yet in that state of mind where I'd create an ODT document with the sole aim of leaving it as it is, without any changes, and finally save it, or else do exactly the action you're suggesting to me. Is it so challenging to think that we would not have the present report or even any report to be sent to Canonical if someone had had to act as-per your very suggestion. Strange that on this platform it's worth wondering once again who among us is a developer and a user who is also a non-developer. I, by simply reading and viewing the content of my attachment, without any fancy trick, could simply - see this sentence: "(...) A transparent object was painted opaque instead.", which does implicitly refer to a non-empty document. - deduce that this message can only be displayed in this same condition that was met when I reported, thus the document with a file extension supported by Writer must not be empty since it must contain the object that Writer identified. Should someone still need my guidance to get the trivial answer; No, you can't expect this message to be triggered with an empty document nor you'll ever get it. So, better to try it yourself if you feel you need it yet.
From what we know so far, there is nothing that constitutes a bug here. So please attach an example file. If you don't have transparent objects in your document, then I guess it could be a bug. If you have transparent objects, then there is no bug.
Correction; "From what I know so far ..." not "From what we know so far ..." as you wrote; you, alone. Talking about yourself in the first person plural is likely to sow confusion. Now, back to the subject. Transparent objects and layers (Optional Content Groups) are forbidden in PDF/A-1 (all variants) –allowed in PDF/A-2. Your sending request is beyond reasonnable. You cannot expect to receive confidential material that is not meant to be shared with Canonical. In this context, creating the condition to have such object inserted in an ODT document, must be left to your complete discretion, More importantly this is even a knowledge that a developer is expected to have for operating fluently. Though that's now for your convenience that i provide guidance; a snapshot taken in Linux might bring the desired transparency property. Otherwise as far as I managed to interpret you, you have ended up with an erroneous conclusion by stating that there would be no issue if a document (here mine) contains (with proof of it) a transparent object. That rather demonstrates something else though as what you say; your lack of ability to consider the whole report. Indeed, as you are taking account of PDF/A-1b separately, you are then missing to evaluate what causes this message to not be displayed when operating PDF/A-2b/3b exports. You are the developer here!
[Automated Action] NeedInfo-To-Unconfirmed
Ricky, no need to be quite so verbose. I understand the issue you describe is: The current warning says "PDF/A" when it should be more specific and say "PDF/A-1b", given that 2b and 3b exports do support transparent objects and don't show the warning. Is that correct? I can confirm that in: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 19e9fe7c8c89399753ac1730e1c76378b18418bc CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Hossein, an easyHack? Code pointer: https://opengrok.libreoffice.org/xref/core/filter/inc/strings.hrc?r=53fc5fa0&mo=5642&fi=70#70 Other strings around that one might need updating too.