Created attachment 73151 [details] Screenshot showing different text of the same document Problem description: An additional character similar to | is displayed unexpectedly in some text. LibreOffice 3.6.4.3 shows the text correctly. LibreOffice 4.0.0.1 does not show the text properly. This is a software regression. Steps to reproduce: 1. The operating system used is Linux debian 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686 GNU/Linux. 2. The LibreOffice versions involved are: - LibreOffice Version 3.6.4.3 (Build ID: 2ef5aff) (LO3.6.4.3) - LibreOffice Version 4.0.0.1 (Build ID: 527dba6f6e0cfbbc71bd6e7b88a52699bb48799) (LO4.0.0.1) 3. The particular file is: https://github.com/tahajahangir/kernel-space-raymond-tree-mutual-exclusion/blob/master/report-public.odt?raw=true 4. File -> Open -> (that document) 5. File -> Export as PDF -> PDF/A-1a -> Export 6. Use DiffPDF to compare the PDF files of the same document. 7. On page one, an additional character similar to | is shown in the PDF file created by LO4.0.0.1 in Adobe Reader 9. Current behavior: An additional character similar to | is shown in LO4.0.0.1. Expected behavior: This character should not be shown in LO4.0.0.1. I am submitting the screenshots for comments. Regards, C. H. D. Operating System: Debian Version: 4.0.0.1 rc Last worked in: 3.6.4.3 release
Created attachment 73152 [details] Just page 1 of PDF created by LibreOffice 3.6.4.3
Created attachment 73153 [details] Just page 1 of PDF created by LibreOffice 4.0.0.1
I can't reproduce this behavior in 4.0.0.1; Seems fine in 3.6.4.3 and 4.0.0.1... Tested with Version 4.0.0.1 (Build id: 527dba6f6e0cfbbc71bd6e7b88a52699bb48799) TinderBox: MacOSX TDF Release, Branch:libreoffice-4-0, Time: 2013-01-09_10:49:53 and Version 4.0.0.1 (Build id: 527dba6f6e0cfbbc71bd6e7b88a52699bb48799) TinderBox: MacOSX TDF Release, Branch:libreoffice-4-0, Time: 2013-01-09_10:49:53
Also unable to reproduce. Tried using diffpdf and didn't see any differences either. Marking as WFM. @Reporter - please try one of two things (or both) a) reset your profile b) wait for rc2 and retest. If you still see this problem on rc2 please reopen the bug as UNCONFIRMED, maybe a commit fixed the issue between RC1 and last night when I last pulled.