Date: prev next · Thread: first prev next last
2025 Archives by date, by thread · List index


Hello,
Version: 24.8.6.2 (X86_64)Build ID: 480(Build:2)CPU threads: 8; OS: Linux 6.13; UI render: default; 
VCL: gtk3Locale: en-US (en_US.utf8); UI: en-USCalc: threaded
Something seems wrong in LibreOffice with exporting to PDF while using PDF password 
protection.Important in this context: I use asian fonts, in particular the Korean hangul font.   
   - LO exporting to PDF without password.   
In firefox, chrome, evince, and LO draw: PDF looks good.   
 
   - LO exporting to PDF without password, and then set a password with pdftk (pdftk-java version 
3.3.3).   
In firefox, chrome, and evince: password protected PDF looks good.   
In LO draw: "Version Incompatibility. Incorrect file version".   
 
   - LO exporting to PDF with password.   
In firefox, chrome, and evince: all Korean characters become 'blank spaces'.   
In LO draw: PDF looks good.
Does someone understand why LO behaves so strangely, when exporting to PDF with password 
protection? Is this a bug that needs to be fixed?
Thanks,-S.






-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/users/
Privacy Policy: https://www.documentfoundation.org/privacy

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.