Jump to content
You must now use your email address to sign in [click for more info] ×

Recommended Posts

Help! Whenever I import a manuscript PDF created from Pages into Affinity Designer, the page numbers all have a ">" symbol next to them and sometimes illustrations do too. I can usually delete these symbols, but for a 200 page document, this is a pain.

Link to comment
Share on other sites

  • Staff

Hi Rabboks,

Any chance you can upload the PDF file here to our internal Dropbox account and i can look into this further.

I did a quick test with a 2 page PDF with page numbers and didn't get any ">" Symbols next to them but the page numbers didn't display correctly, so that's a different issue i'll have to log. 

Link to comment
Share on other sites

  • Staff

Hi Rabboks,

Thanks for the files, could you upload the PDF you published from Pages, before it's been imported into Affinity.  This will allow me to log the actual PDF file that's being imported along with the .afdesign file as well.  I keep getting mixed results in my testing, sometimes it works fine and other times i get the >. 

I think it's how Affinity is reading the formula Pages will be using for the page numbers, but i could be wrong.

 

Link to comment
Share on other sites

On 10/25/2018 at 3:47 AM, stokerg said:

I keep getting mixed results in my testing, sometimes it works fine and other times i get the >. 

First, I have to say I rarely if ever use the Pages app & barely understand how to use most of its features, so I could be doing this all wrong.

That said, I created a very simple one page Page number test.pages document & exported it from Pages as Page number test.pdf. The page number was inserted 3 times, once as text in the body & twice in the footer, with each of them in a different font. Importing the PDF into Affinity Designer resulted in Pages number test.afdesign.

I did a few other tests with 2 page versions & with the different PDF import text options in Affinity Designer, but in all of them the results were the same: the added characters vary consistently by font, so for example Arial adds the > character, Helvetica Regular adds a colon, & so on.

Also, the Layers panel looks very odd, as shown below.
632350487_Layerspanel.jpg.864e94391f1492eaabf17cf329a2c807.jpg

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

I've uploaded an un-exported version of the generic book template in a pages format. If I create a PDF from pages and open it in preview, it looks fine. The problem is the printer demands the PDFs be PDFX-1a:2001 or 2003 and that's what Affinity can do that Pages can't.

Link to comment
Share on other sites

@Rabboks, as a test have you tried changing the font used for inserted page numbers in your Pages document & seeing if that makes any difference in the PDF exported from Pages & imported into Affinity Designer?

In my simple test, the Arial font adds the extra > character to page numbers but other fonts add different characters.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

  • 2 weeks later...
On 10/25/2018 at 10:47 AM, stokerg said:

I think it's how Affinity is reading the formula Pages will be using for the page numbers, but i could be wrong.

 

hi,

i don't think you're wrong. i have the same problem with the greater than signs in the page number fields when the imported .pdf file is generated by pages (and the page numbers are generated automatically). in my case i used the font georgia.
in publisher i removed the page number text fields by hand. i thought the solution would be to make a master page with only a page number field and to apply i to all my pages, but that doesn't work.

regards,
jan van de ven

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.