<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Narrow No-Break Space causes PDF Error by using Font Liberation Serif" href="https://bugs.documentfoundation.org/show_bug.cgi?id=112152#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Narrow No-Break Space causes PDF Error by using Font Liberation Serif" href="https://bugs.documentfoundation.org/show_bug.cgi?id=112152">bug 112152</a> from <a class="email" href="mailto:uwe@franke-auer.de" title="Uwe Auer <uwe@franke-auer.de>"> Uwe Auer</a> <pre>Due to a question at ask.libreoffice.org (see <a href="https://ask.libreoffice.org/en/question/190046/exported-pdf-gives-liberationserif-font-error-in-adobe-acrobat-reader/">https://ask.libreoffice.org/en/question/190046/exported-pdf-gives-liberationserif-font-error-in-adobe-acrobat-reader/</a>) I've made the following test. 1) Create one document containing a single U+202F code (Liberation Sans) 2) Create one document containing no U+202F code with almost the same text 3) Create an PDF Export for each .odt fikle using LibreOffice's PDF Export function 4) Open both using Adobe Acrobat Reader DC 2018.010.20099 on Windows 10 Pro 1809.17763.437 Result 1 - File containig U+202F Result is confirming reporter system. I do get the same message, when clicking onto the text in Acrobat Reader. Please note: Other ODF Readers may not report the error / warning, while using other creators like cups-pdf won't produce the error when opening the PDF with Adobe Reader. Result 2 - File *not* containig U+202F No error / warning in Acrobat Reader reported. PDF creation done with: Version: 6.2.2.2 Build ID: 2b840030fec2aae0fd2658d8d4f9548af4e3518d CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: kde5; Locale: en-GB (en_GB); UI-Language: en-US Calc: threaded</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>