Created attachment 126906 [details] pdf
Created attachment 126907 [details] Side by side
This is clearly a duplicate of bug 101220 -- in this case the embedded TimesNewRomanPS font family is not being extracted and used in the pdfimport filter. The fallback font selected on Linux does not match font metrics (Windows does a bit better)--while that fallback could be improved potentially, the correct way to resolve is the extract the embedded font(s) and render the document with better fidelity using the source fonts. @ekari, please stop making these duplicate bug submissions for PDF exhibiting poor fidelity on font substitution--they are all the same issue. *** This bug has been marked as a duplicate of bug 101220 ***
I was referring to the blue fluxogram that is bigger than the original and the red fluxogram has a strange image instead of a bell
The oversize bubble object is because on import the page is not being cropped and formatted as specified in the PDF. The sample document base page is 9.92" x 6.99", and crop values of "0.583 in" top and bottom, and "0.833 in" left, "0.819 in" right are applied to the document specifying an intended size of 8.26 inch x 5.82 inch. The LibreOffice pdfimport filter mishandles that. It only sees the 9.92" x 6.99" base page size, and then applies margins of 0.20" left & right and 0.39" top & bottom. The crop margins that should mask/resize the page are not handled and are lost. This is similar to issues of bug 86211 which is the general case that clipping is not implemented, but here it is more specific in that the import filter does not recognize the page cropping that should be applied. So the resulting page size of the document in LibreOffice is oversize to what is described in PDF and then additional margin space is added. Testing a recent master on Windows 10 Pro 64-bit en-US where upgrading to current poppler (ver 0.46) as done for bug 101460 is present does not affect this aspect of the import filter. Version: 5.3.0.0.alpha0+ (x64) Build ID: 932804559e845fb8ec6ac3a3b49308136a7e81e6 CPU Threads: 8; OS Version: Windows 6.19; UI Render: GL; TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2016-08-20_21:42:18 Locale: en-US (en_US); Calc: CL Restating the issue and to NEW. Otherwise, the Bell glyph (a PUA U+F041 symbol) is from the subset embedded MSOutlook symbol font that is bug 101220 as are the other font layout issues.
@ekari, thanks for reporting this valid issue. But please do not attach complete documents as examples. It does not help the QA process. It is much better to extract a page or two, and provide *annotated* screen clips--especially if unable to extract pages from the example PDF. And, *please* be mindful of copyright--the commercial documents you submit are clearly not covered by a Creative Commons license. Extracting a page or two meets "fair use" tests for copyright, attaching the whole document is questionable.
@V Stuart Foote What software do you recommend to use to extract a page without altering the contents? I tried GIMP and it removed the embedded fonts and other stuff..
I hold license for and use both iceni Infix PDF editor (v 6.50) and Adobe Acrobat (v 9.5.5) --both companies are moving to subscription based licensing for more current releases-- but either of which make unadulterated page extractions of content but tweak some of the meta data, but there are other choices. And on Linux a number of products will allow you to "extract" pages without structural changes to the content, but again some meta data tweaks. Master PDF Editor https://code-industry.net/masterpdfeditor/ PDF Studio http://www.qoppa.com/pdfstudio/
** 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-20170901
Issue of the pdfimport filter not correctly cropping PDF page remains in recent master/6.3.0alpha0+ build. Version: 6.3.0.0.alpha0+ Build ID: 5fe551931d49a64ca4ea793a5016c098e41e84cd CPU threads: 8; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: CL
Dear E.Mi, 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 https://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
Dear E.Mi, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
I'm working on a fix that happens to also fix this I think. Although your test file has been useful, since it's highlighting a bug in my fix, so I'll try and get that fixed first. In short there's very little clipping in the pdf code!
(In reply to Dave Gilbert from comment #12) > I'm working on a fix that happens to also fix this I think. > Although your test file has been useful, since it's highlighting a bug in my > fix, so I'll try and get that fixed first. > In short there's very little clipping in the pdf code! @Dave G. Thank you. As you proceed, perhaps check the see also bug 86211 when working up your patch for applicability there. And assign that issue to yourself as well. Then when you submit patches implementing clipping masks via git please just include both tdf#101611 *and* tdf#86211 in the first line of the patch.
Side note: The example pdf here uses JPX/Jpeg2000 embedded images; when we build our embedded libpoppler we don't enable that (since we don't have a JPEG2000 lib built?) so all the images on this document appear blank. It works fine when using Fedora/Debian's system libpoppler. This message has been brought to you to warn my future self not to lose another day on it.
Dr. David Alan Gilbert committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/b416c5b8e32632a63e1e791c34896e17d89f7982 tdf#101611, tdf#108813, tdf#86211, sdext,pdfimport: Clip fills It will be available in 25.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
The commit just pushed to master seems to fix this fine.