snowite Posted November 1, 2019 Share Posted November 1, 2019 Seems I am having a bit of issues this morning and it's only 8am. First, I was having trouble with fonts in Photo (also the latest version) but Walter says it might be might font set and offered some work arounds. Okay, I can live with a font not doing subscript. Now, the graphic I was working on in photo was intense in text and images. I exported the graphic to PDF = BEAUTIFUL! Totally crisp! no issues! See attached sample - Perfection! However, when I import that very same BEAUTIFUL file into publisher - I get a lot of noticeable garbage on the the text portions of the file. See attached sample. So I figured maybe something messed up and it was just maybe my pdf viewer - the one that comes with windows - so I closed publisher - opened again re-imported the file an still had the same issue. So I closeout everything and open the file in a separate SEDA PDF Viewer program after exporting a test from publisher - nope! So, I do know that it is a font issue or possibly an import/export issue for the font. The font however does reside inside my machine. The font is calibri regular. Not too way out there. I can type in the PDF document using the very same font with no ill effects. See attached sample testtyping.pdf exported from publisher. So assuming it's just a font issue, I went online and downloaded a random pdf. no issues. So I did some research and adobe says to make sure the font file is embedded. so I go back to the original photo file and I check all the PDF export options. Embed all fonts was selected- I even selected the embed advanced features since that was unchecked. I export, again a beautiful document, import to publisher - says all fonts are available upon loading- again garbage is what I see when opening the file. to ensure it was not just a cache of the page issue, I even renamed the file to another name - still got garbage. Sigh! I do love technology but sometimes I just want to kick it across the floor! testtyping font.pdf eco2.pdf FYI: Opens perfectly in Designer and Photo.! Link to comment Share on other sites More sharing options...
Wosven Posted November 1, 2019 Share Posted November 1, 2019 When you import your PDF, the app is unable to reconize ligatures. You can either disabe them before export (look at the paragraph style panel), or convert your text to curves when exporting (in the "more" options when exporting). Link to comment Share on other sites More sharing options...
snowite Posted November 2, 2019 Author Share Posted November 2, 2019 Wosven: When you import your PDF, the app is unable to reconize ligatures. You can either disabe them before export (look at the paragraph style panel), or convert your text to curves when exporting (in the "more" options when exporting). So I tried that. I went into the original document and had set all the text to curves on export. It did not solve the problem. I opened the file in Affinity Publisher and Designer (now it's a issue) - both have garbage on the import. The only one NOT showing the garbage is Photo but only on the original file. I only use Affinity products for designing. I don't even own Photoshop or any other design programs anymore. I would think there would not be problem between applications when they are from the same developer. Link to comment Share on other sites More sharing options...
Catshill Posted November 2, 2019 Share Posted November 2, 2019 Have you tried converting the pdf to a bitmap such as a png and then importing that? I have to do that when I import pdfs that use fonts that are not on my system as Affinity does not support pdf pass through. Link to comment Share on other sites More sharing options...
Wosven Posted November 2, 2019 Share Posted November 2, 2019 I don't have garbage if there's no ligatures or text is converted to curves when I place those PDF in a APub document The PDF exported and the one with those imported: Spill_textNormal.pdf Spill_noLigatures.pdf Spill_textAsCurves.pdf Spill_import.pdf Link to comment Share on other sites More sharing options...
Staff Patrick Connor Posted April 17, 2020 Staff Share Posted April 17, 2020 Sorry. Thank you for reporting a problem using 1.7.x . It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum. Report a Bug in Affinity Designer Report a Bug in Affinity Photo Report a Bug in Affinity Publisher Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem. This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the current 1.8.3 release build. Patrick Connor Serif Europe Ltd Latest V2 releases on each platform Help make our apps better by joining our beta program! "There is nothing noble in being superior to your fellow man. True nobility lies in being superior to your previous self." W. L. Sheldon Link to comment Share on other sites More sharing options...
Recommended Posts