Apache OpenOffice (AOO) Bugzilla – Issue 67578
Documenting the new PDF Encryption feature
Last modified: 2007-05-25 09:16:49 UTC
As I said in a mail exchange (see ) I opened a documentation issue for the new PDF Encryption feature. I'm not a technical writer so the document I'm going to attach is surely not well suited to be included "as is" in a manual, guide or on-line help. But I think it's enough for a start. I set the version as m177 because this is the first available with this feature.
Created attachment 37895 [details] the first version od the documentation draft
Oops I forgot the link to the mail which triggered this, here it is: http://documentation.openoffice.org/servlets/BrowseList?list=dev&by=thread&from=1391066 The delay (almost two months) depends on the fact that the specification became stable on July, 7th.
Please let me know the thread of the dicussion. I have missed it.
Got it. Thanks but now have questions: 1. Do you mean public key as in a certificate? Or are we limited to say gpg keys. 2. How does this affect digital signing?
-> grsingleton. It seems I forgot to add the line numbering to the draft, i would have been better. So please turn it on on the draft document, thanks. > 1. Do you mean public key as in a certificate? Or are we limited to say gpg keys. I suppose you are referring to row 19 of the draft. There I meant the kind of the security that a PDF can support, but it is not supported here. Only the Security handler (row 18 and from row 28) is supported. > 2. How does this affect digital signing? If you are referring to export a digital signature to a PDF document (issue 47895 may be ?), it was not implemented in issue 12626 (the one I'm referring to, again I forgot to mention it at the very beginning, sorry...). As to digitally sign a PDF with an external application, for example Adobe Acrobat Professional, I think it will check the permission if signing is permitted.
I asked because I have a code-signing certificate and saw that its use might be useful. I will be getting m177 or later soonest and will experiment.
info will be added to file /shared/01/ref_pdf_export.xhp once the CWS hcshared01 is integrated. Must wait for this because the other new tab pages are explained there, too.
changed target
Question. Why change the target. I have been testing this feature and have documented it based on the original target. As near as I can tell it is still part of the devel snapshots as I have m180 working well. Is this change becasue of some new numbering scheme?
sorry, I've hijacked this "manual" issue to serve as an "online help" issue too. Nothing to be worried about. Change target back if you need to.
I would rather know about the numbering. Quite a jump from 2.0.4 to 2.1. If this is a new development from thje developers then why not jump directly to 2.5 so it matches Sun's numbering?
please verify in hcshared04. Open Writer doc, choose File - Export as PDF. Enter a file name and click Save. PDF dialog opens, click Security tab page. Press Shift+F1 and check all controls have Extended Help.
take it
found fixed on cws hcshared04
had to replace the source file by an older version due to some build problems in master. Fix is now part of CWS hcshared06.
was verified by QA in hcshared04, I can verify fix in hcshared06. Leave as "verified".
in addition to my latest comment : also in hcshared06 Frank
Re-opened because on OOF tree this does not work whilst SRC680_m209 is fine.
Uwe please check if it should go into 2.2.1and set target according to the decission.
Fix will be integrated to 2.3 automatically. There had been some resync problems with this file which delayed the timely merging to master. It is OK starting with master m203. See issue 58070
FYI, this feature has been included in the user guide, http://documentation.openoffice.org/manuals/OOo2.x/user_guide2_draft.pdf since 2006-07-31. Samples were provided at that time.
This is reported by fst to be verified in m209
found fixed in master m213 --> closing