Jump to content
Sign in to follow this  
TheOrienteer

[Fixed] PDF Text Import Bug

Recommended Posts

I have encountered a bug importing a PDF into Affinity Designer. I recently saved some excel charts as PDFs and when I import them into Affinity Designer, the chart title and axis title text is imported as multiple lines instead of a single line of text. It appears that Affinity Designer is replacing the spaces in the text with return characters (resulting in one word per line).

 

The pdf opens correctly in Preview and in the Affinity Designer pdf import page preview window. The only problem visually is when it has actually been imported into Affinity Designer. Also changing the "Favour editable text over fidelity" option does not change this behavior.

 

I have attached some screenshots as well as the pdf to this post.

 

 

 

System is running Affinity Designer 1.3.2 on Mac OS X 10.10.4.

 

 

 

Thanks!

post-14880-0-22903000-1437178888_thumb.png

post-14880-0-81431700-1437178889_thumb.png

post-14880-0-38111300-1437178891_thumb.png

20µm_PMOS.pdf

Share this post


Link to post
Share on other sites

Have a solution for that M$ file:

 

Just resave it with  Preview and open the new file in AD and delete the character "2” (with the replace tool next year).

 

 

PS: Converting PDFs is not really easy. Some micro-$oft-ware export crazy PDFs.

Share this post


Link to post
Share on other sites

Thanks for looking in to this issue :)

 

Oval - re-saving it in preview did seem to fix the multi-line return problem, but it introduced the problem of the 2's you mentioned as well as expanding the pdf size to a full page. Thanks, for this hint though, it might be a short term solution for now. Definitely not a long term solution though since I have to process large groups of these charts.

Share this post


Link to post
Share on other sites

I have to process large groups of these charts.

 

The best things come in threes:

 

1. change that M$ font calibri

 

2. try to open the Excel files in Numbers

 

3. Pssst: with cheeper software it works perfectly: Inkscape  :)

 

Good luck!

 

PS: If you asked lemkesoft you would have had the solution before.  ;)

Share this post


Link to post
Share on other sites

It seems a cmap was trying to map a character to one of a number of other characters, and we were interpreting as mapping to all of them. We have now resolved the problem and will make the fix available in the next release.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×