To reproduce: 1) Create a document in Writer with headings using the letters Å, Ä and Ö. 2) Generate table of contents 2) Export the document to a PDF. In the PDF the letters will have disappeared from the table of contents and only empty spaces remain. The letters will remain in the actual headings and the rest of the text. Only the table of contents is effected
Hello, Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document. (Please note that the attachment will be public, remove any sensitive information before attaching it.) How can I eliminate confidential data from a sample document? https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F Thank you
Created attachment 124055 [details] The odt file where everything is as it should.
Created attachment 124056 [details] The exported PDF where ÅÄÖ is missing.
Created attachment 124061 [details] printscreen Hello, I can not confirm with Version: 5.2.0.0.alpha0+; win7. Even in your pdf file I see ÅÄÖ in table of contents (firefox inbuilt pdf viewer). Are you sure it's not a problem in your pdf viewer?
(In reply to raal from comment #4) > Created attachment 124061 [details] > printscreen > > Hello, I can not confirm with Version: 5.2.0.0.alpha0+; win7. Even in your > pdf file I see ÅÄÖ in table of contents (firefox inbuilt pdf viewer). Are > you sure it's not a problem in your pdf viewer? I initially though not since exporting the same document to a PDF with OpenOffice worked perfectly when viewed with my PDF viewer, Okular. However, viewing the LibreOffice exported document in Firefox worked better. But same as you the letter appear but seem to be in a separate font that the rest of the letters. So there seems to be something unusual with how LibreOffice export PDFs and viewers handle it differently. But neither Firefox or Okular handle it properly. Which side is a fault I don't know. Maybe both.
When viewing your file in adobe reader, I see missing letters. Needs to be tested in dev version 5.2, linux - works OK on windows 5.2, so either linux only bug or fixed in dev version
Created attachment 124104 [details] export from LO 5.2 Hello, export from Version: 5.2.0.0.alpha0+ Build ID: ef34535ceb60d7d63b8d8671e4c6e9e43ffbd17d CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-03-27_09:53:05 I see it correct in Evince. Please could you test with dev version? http://dev-builds.libreoffice.org/daily/master/ Thank you
(In reply to raal from comment #7) > Created attachment 124104 [details] > export from LO 5.2 > > Hello, export from Version: 5.2.0.0.alpha0+ > Build ID: ef34535ceb60d7d63b8d8671e4c6e9e43ffbd17d > CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; > TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: > 2016-03-27_09:53:05 > I see it correct in Evince. > Please could you test with dev version? > http://dev-builds.libreoffice.org/daily/master/ > Thank you I did not manage to install those builds on Arch Linux, it was problematic since it doesn't use rpm or deb. So I compiled it myself from the git repository. That should be fine, right? Even never if anything. The problem persists though, sadly. Your export is correct when I view it though, so the problem doesn't seem to be with my PDF viewers. Here's the info: Version: 5.2.0.0.alpha0+ Build ID: 3c36ba50f65d663f35264f2a11c99c0ff98674a2 CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: en-US (en_US.UTF-8)
Repro. Arch Linux 64-bit, KDE Plasma 5 Version: 5.2.0.0.alpha0+ Build ID: 9b0069c2833313ba9fab91f45edd354ba334f94b CPU Threads: 8; OS Version: Linux 4.4; UI Render: default; Locale: fi-FI (fi_FI.UTF-8) Built on April 8th 2016
*** This bug has been marked as a duplicate of bug 89246 ***
Hello labus93, Thank you for reporting the bug. This issue has previously been reported, so this bug will be resolved as a duplicate of the earlier report. You will automatically be added to the CC list of the other bug.