+++ This bug was initially created as a clone of Bug #78807 +++ Version: 4.2.5.0.0+ Build ID: da739f729223908516deb1c2564d0713231abb5b Tested on WinXP Text not fitting on page, as well as in the box See Page 13, 16 http://www.bissell.com/assets/0/132/134/228/78366bd2-6286-4bf0-a2c1-0aa5491466e6.pdf Actual attachment 99192 [details] page_13_LO.PNG attachment 99194 [details] page_16_LO.PNG Expected attachment 99195 [details] page_16_FF.PNG attachment 99193 [details] page_13_FF.PNG
reproducible under Win7x64 using LibO 4.2.4.2 status NEW
Text in page 13 has LucidaSansStd font and in page 16 – FuturaStd, FuturaStdBook and FuturaStdMedium font. Please, check if all the fonts are installed correctly. It would be better to use LibreOffice 4.3 for testing because it has some improvements in pdfimport.
(In reply to comment #2) > Text in page 13 has LucidaSansStd font and in page 16 – FuturaStd, > FuturaStdBook and FuturaStdMedium font. Please, check if all the fonts are > installed correctly. It would be better to use LibreOffice 4.3 for testing > because it has some improvements in pdfimport. Tested on 4.3.2 nightly from 2014-09-06 this issue still exist On my system I see Lucida Sans Unicode and Lucida Console, is that sufficient for LucidaSansStd ? I don't see Futura at all. But question, then how Firefox pdf.js do it better on the same system? Anyway it OK if you want mark this as WONTFIX or Something for FUTURE. Or better, you can check with Firefox team to find how they resolved similar issues. If required fonts are not there, can't we automatically prompt for download of a generic font matching the required font from a centralized font repository?
Page 13 was ok, still the same problems on page 16. Setting to NEW and lowering severity to minor per https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg Win 7 64-bit Version: 4.5.0.0.alpha0+ Build ID: b144f0ac8695dd62a2053b4e88212d0b109c9a41 TinderBox: Win-x86@51-TDF, Branch:MASTER, Time: 2014-11-25_00:14:54
Hello, Biju I am sorry for late answer > On my system I see Lucida Sans Unicode and Lucida Console, > is that sufficient for LucidaSansStd ? > I don't see Futura at all. You can try font replacement using Tools -> Options -> LibreOffice -> Fonts > But question, then how Firefox pdf.js do it better on > the same system? PDF was created to show documents, not to edit. It allows to embed fonts, but usually only a subset (symbols that are really used in a document) is embedded, not a whole font. It is enough to show a document, but it could be difficult to import to editable format. Anyway it would be great if LibreOffice could import the fonts. I report it as bug 85295 that is not about specific document but about font import at whole. > If required fonts are not there, can't we > automatically prompt for download of a generic > font matching the required font from a centralized > font repository? If we want to avoid such problems as this this bug, we should substitute fonts with metric identical ones. For example, Times New Roman can be substituted with Liberation Serif. The autosubstitution in LibreOffice works for me in many cases. But not every font has free metric compatible analog. Good news: https://wiki.documentfoundation.org/ReleaseNotes/4.4#Included_fonts LibreOffice 4.4 adds the libre-licensed Caladea and Carlito fonts (Huerta Tipográfica). Caladea and Carlito have the same metrics and proportions as Microsoft’s Cambria and Calibri
Shifted phone number on page 16 is fixed here: https://gerrit.libreoffice.org/14098
Found more specific bug about phone number: Bug 79045
** 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.5 or 5.1.0) 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: 2016-02-21
Since the issue is attributed to the font substitution (comment #5) we continue the discussion better there. *** This bug has been marked as a duplicate of bug 85295 ***