See http://www.computerwoche.de/archiv/pdf/2007/leseprobe_37.pdf PDFExchange Viewer isn't also able to copy and paste the text, so this is something harder than the usual text stuff.
While opening a PDF doc by LibreOffice 4.0.2.2 it opens but shows double images instead of a single, just like viewed by astigmatism. It is very difficult to read if not impossible. However, it showed as well that I am able to delete the one on top of each page and read normally. LibreOffice seems to open twice the same PDF doc on a single view of such document.
Created attachment 79523 [details] pdf missing text, images
When I open this pdf, I cannot even see the text. Other pdf's with images and text do not have the same issue. I wonder why this one is different. Version: 4.0.3.1 (Build ID: a67943cd4d125208f4ea7fa29439551825cfb39) Platform: Ubuntu 13.04 ------------------------------- LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists
heh, I started to analyze the file more and searched a bit in some forums and blogs. It turned out that this is a DRM protected file and thus the decoding doesn't work. Moreover I realized that PDF readers (doesn't matter which one, neither Adobe Reader nor other free ones) can actually copy texts out of this PDF document. The text which is copied is either"rubbish" or the white boxes with black border (as seen on Asian websites without having installed special fonts on older web browsers)... LibO should at least warn the user (that LibO can't handle some fonts / texts) if the user try to open/edit an DRM file.
Created attachment 104433 [details] incorrect text codification (Libo 4.4) How it looks with Version: 4.4.0.0.alpha0+ Build ID: 33fd0d8ae6a6b4e5226991e39fe755d84cb78280 TinderBox: Win-x86@51-TDF, Branch:MASTER, Time: 2014-07-14_10:10:0
I update the title as the images are displayed correctly, however the text isn't. It looks like a commit in b3f41543851e9985c6c7ba133c32753c9bc732c1..b1f7dd66b898b03cb4bd8d434b6370310ea95946 fixed the missing text problem but did not fix it completely and the text encoding is still wrong.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.0.5 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03
This issue is still present in Version: 5.0.1.2 Build ID: 81898c9f5c0d43f3473ba111d7b351050be20261 Locale: es-ES (es_ES) on Windows 7 (64-bit)
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
still repro Version: 5.2.1.2 (x64) Build-ID: 31dd62db80d4e60af04904455ec9c9219178d620 CPU-Threads: 4; BS-Version: Windows 6.19; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group @xisco: you changed the title of that bug, did you read my comment #4 (not text encoding problem, but drm!)
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170929
still repro with Version: 5.4.1.2 (x64) Build-ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527 CPU-Threads: 4; Betriebssystem:Windows 6.19; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group
The text is extracted fine, it's just encoded. You can simply replace the symbols with corresponding letters.
Could someone write what this bug is about, what's "expected"?
(In reply to Timur from comment #14) > Could someone write what this bug is about, what's "expected"? for example the biggest headline in the middle should display "IBM steigt bei OpenOffice ein" and not some "rubbish". As my analysis a few years ago showed that this is DRM stuff, I do not believe that we can resolve this...
Dear Dennis Roczek, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
No file to test.
archive.org copy: http://web.archive.org/web/20160304091821/https://www.computerwoche.de/archiv/pdf/2007/leseprobe_37.pdf
[Automated Action] NeedInfo-To-Unconfirmed
Status back to NEW as it was before comment 17.
Hi Khaled. Can you please see this bug of fileopen PDF. Opinions are different: DRM, encoding, toUnicode. I ask you because of seemingly related bug 66597. Thanks.