Jump to content

Recommended Posts

@Robert St-Pierre

@Rodi is asking you to attach your original Affinity file, along with the resulting pdf to your next reply.

Jeff


Win 10 Pro, i7 6700K, 32Gb RAM, AMD Radeon R7 360 and Intel HD530 Graphics

 

Long-time user of Serif products, chiefly PagePlus and PhotoPlus, but also WebPlus, CraftArtistProfessional and DrawPlus.  Delighted to be using Affinity Designer, Photo, and now Publisher.

Share this post


Link to post
Share on other sites

@Robert St-Pierre

Thank you for the files etc.

I am not a French speaker though I can just about read the language fully, but I'm going to assume examples of your misspelt words are (in a sample form the pdf) as shown below?

ScreenShot00567.jpg.205e41843ed29dc9c1a6551f7fc5b8b6.jpg

 

If so, I see exactly the same in your AFPub file:

ScreenShot00568.thumb.jpg.f839ba6466fcf441f9aa50f151a6fa9d.jpg

This looks rather like a font issue, but you need the help of more experienced users than me to help you resolve the problem.

Jeff


Win 10 Pro, i7 6700K, 32Gb RAM, AMD Radeon R7 360 and Intel HD530 Graphics

 

Long-time user of Serif products, chiefly PagePlus and PhotoPlus, but also WebPlus, CraftArtistProfessional and DrawPlus.  Delighted to be using Affinity Designer, Photo, and now Publisher.

Share this post


Link to post
Share on other sites
27 minutes ago, emmrecs01 said:

This looks rather like a font issue

It does rather, doesn’t it! It looks to me as though it’s the same ligatures issue that has been raised in other threads: each occurrence of Ë should be a ti ligature. It should be possible to correct the error by selecting the text and turning off the ‘Standard Ligatures’ feature and/or the ‘Discretionary Ligatures’ feature via the Typography panel.


Alfred online2long.gif
Affinity Designer/Photo/Publisher for Windows • Windows 10 Home (4th gen Core i3 CPU)
Affinity Photo for iPad 1.8.4.186 • Designer for iPad 1.8.4.4 • iPadOS 13.7 (iPad Air 2)

Share this post


Link to post
Share on other sites

Has the text been imported from another program like Word or any other. Or has this text been created on a Mac or Linux computer... it looks like an ascii code problem, all "ti" are displayed as "Ë" . Calibri font works very well in French. This is a font I use often if French without any problem.

If the problem is only with the "ti" a "Search and Replace" will fix it quickly.


-- Window 10 - 32 gb - Intel I7 - 8700 - NVIDIA GeForce GTX 1060
-- iPad 2020 - 12,9 - 256 gb - Apple Pencil 2 -- iPad 6th gen 128 gb - Apple Pencil 1

Share this post


Link to post
Share on other sites

Your right Jeff, I did not notice that. But still the accent and certain words our wrong. 

AlainP, Yes I do cut and paste from a Word document that could be it.

I use  Sherif Page plus X9  before and never had that problem.

Interesting I will need to do a few test. 

Thanks guys.

Share this post


Link to post
Share on other sites
20 hours ago, Alfred said:

It does rather, doesn’t it! It looks to me as though it’s the same ligatures issue that has been raised in other threads: each occurrence of Ë should be a ti ligature. It should be possible to correct the error by selecting the text and turning off the ‘Standard Ligatures’ feature and/or the ‘Discretionary Ligatures’ feature via the Typography panel.

The other threads about ligatures are about PDF import, (which is unsupported), not export. 
I'd humbly suggest that turning off all ligatures may not be desirable or viable in all circumstances.

Share this post


Link to post
Share on other sites
18 minutes ago, benwiggy said:

The other threads about ligatures are about PDF import, (which is unsupported), not export.

I'm not sure what you mean about PDF import being unsupported. It certainly is supported: you can either Open a PDF document or you can Place (import) it.


-- Walt

Windows 10 Home, version 2004 (19041.388),
   Desktop: 16GB memory, Intel Core i7-6700K @ 4.00GHz, GeForce GTX 970
   Laptop:  8GB memory, Intel Core i7-3625QM @ 2.30GHz, Intel HD Graphics 4000 or NVIDIA GeForce GT 630M
Affinity Photo 1.8.5.703 and 1.9.0.820 Beta   / Affinity Designer 1.8.5.703 and 1.9.0.820 Beta  / Affinity Publisher 1.8.5.703 and 1.9.0.822 Beta.

Share this post


Link to post
Share on other sites
On 6/30/2019 at 2:42 PM, walt.farrell said:

I'm not sure what you mean about PDF import being unsupported. It certainly is supported: you can either Open a PDF document or you can Place (import) it.

No it isn't. Read this thread.  Currently, an imported PDF cannot be trusted to display any of the correct glyphs if it uses ligatures or OpenType variants. Some text elements can move, too.  The entire Affinity Suite cannot rasterize a PDF; import for editing; or place on a page correctly.

Share this post


Link to post
Share on other sites
34 minutes ago, benwiggy said:

No it isn't. Read this thread.  Currently, an imported PDF cannot be trusted to display any of the correct glyphs if it uses ligatures or OpenType variants. Some text elements can move, too.  The entire Affinity Suite cannot rasterize a PDF; import for editing; or place on a page correctly.

Technically, PDF import is supported, but there are aspects of that support that need to be improved. That is, it doesn't work as well as we (or Serif) might like.

But the ability to Open or Place PDF documents is implemented, and advertised. Therefore it is by (at least one) definition supported.

Regarding ligatures and OpenType variants: Other threads have pointed out, regarding ligatures, that if the PDF properly includes the ToUnicode table, the characters will be properly understood, for example for spell-checking. Or they will work in spell-checking if the user chooses to prefer editability over visual fidelity when importing. I suspect that the same would apply to the OpenType variants, but have not made any attempt to test that.

I have quite happily opened PDFs that have worked quite well or with only minor glitches. So I will object to statements that say flatly that it is not supported. It is supported, with caveats or nuances that may or may not matter for any particular PDF or to any particular user for that particular user's purposes.

I will strongly agree the existing support should be improved.


-- Walt

Windows 10 Home, version 2004 (19041.388),
   Desktop: 16GB memory, Intel Core i7-6700K @ 4.00GHz, GeForce GTX 970
   Laptop:  8GB memory, Intel Core i7-3625QM @ 2.30GHz, Intel HD Graphics 4000 or NVIDIA GeForce GT 630M
Affinity Photo 1.8.5.703 and 1.9.0.820 Beta   / Affinity Designer 1.8.5.703 and 1.9.0.820 Beta  / Affinity Publisher 1.8.5.703 and 1.9.0.822 Beta.

Share this post


Link to post
Share on other sites
1 hour ago, walt.farrell said:

Technically, PDF import is supported, but there are aspects of that support that need to be improved.

Did you read the other thread? A member of staff says the actual words "We don't currently support PDFs with embedded fonts". You can of course object and suggest that they support all aspects of PDF import except for that one, which just needs improvement, if you wish. But it's a pretty pointless distinction.

I've done the simplest of tests with PDFs from a range of creators, including Adobe, and they've come up a complete mess in Affinity. And only in Affinity. The characters may be understood, but the glyphs used in the PDF are not used. 

Currently any PDF with text cannot be relied upon to appear correctly in Affinity Suite. I eagerly await the day when this is no longer the case, but it needs stating now.

Share this post


Link to post
Share on other sites
2 hours ago, benwiggy said:

Did you read the other thread? A member of staff says the actual words "We don't currently support PDFs with embedded fonts".

Yes, that's what he said. And based on other statements, I interpreted that as "we do not use the embedded fonts in PDF files".

They have said that you must have the matching fonts installed. If you have them, the PDF works.

They are different ways of saying the same thing, and neither phrasing says what you said, and what I objected to, "PDF import is unsupported".

PDF import is supported.
Use of embedded fonts from an imported PDF is not.

That is important, perhaps very important, perhaps even a deal-breaker for some category of Publisher user or potential users. Apparently for you. Not so much for me.

It does need to be fixed.


-- Walt

Windows 10 Home, version 2004 (19041.388),
   Desktop: 16GB memory, Intel Core i7-6700K @ 4.00GHz, GeForce GTX 970
   Laptop:  8GB memory, Intel Core i7-3625QM @ 2.30GHz, Intel HD Graphics 4000 or NVIDIA GeForce GT 630M
Affinity Photo 1.8.5.703 and 1.9.0.820 Beta   / Affinity Designer 1.8.5.703 and 1.9.0.820 Beta  / Affinity Publisher 1.8.5.703 and 1.9.0.822 Beta.

Share this post


Link to post
Share on other sites
10 hours ago, walt.farrell said:

They have said that you must have the matching fonts installed. If you have them, the PDF works.

That doesn't work either. Even with the correct fonts installed, PDF imports don't use the correct ligatures and OpenType variants. Text objects also move. 

I'm going to offer you the compromise wording of "PDF import guaranteed for small minority of specially prepared PDFs!". 9_9 

Share this post


Link to post
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

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.