big smile

(...)

That is indeed interesting!

As I suspected, there’s no É glyph: there’s only E and Ë. The font seems to be squarely aimed at users of Eastern European, Cyrillic, and Hebrew alphabets.

The font is Rubik from Google fonts: https://fonts.google.com/specimen/Rubik
I have tried using Helvetica, and the accents on that output fine when exported to PDF via Publisher. 
I can export from accented characters from Affinity Photo with this font just fine, so I am not sure why Publisher is misbehaving. 
 

It looks as though the acute accent is being added separately to the E (and incorrectly positioned on top of it) instead of an É glyph being used.
What font is it? Do you get the same result with other fonts?

My problem was coming from the hardware acceleration option. Disabling it solve it.
It's good that you found the solution
 

I like the Affinity Photo user interface and would not be in favor of an overhaul.

Ads I did, you just need to group this, duplicate and rasterise it, hide the original group, and export to grey PDF.

The 1.9 beta now shows that information in the context toolbar for embedded/linked documents
Can't do a screenshot at the moment (watching Porn) ☺️

Hmm ... I wonder why not!
If it worked (see above) you could do it with a single document. You would simply switch off the adjustment layer when you wanted a colour PDF.

Have the Move Tool active and select the Picture Frame object or Image object. Near the left end of the context toolbar is the scaling percentage, but note that the displayed number is imprecise because it has been rounded to an integer.
 

Yes, unfortunately a scaling percentage is not revealed for an embedded/linked document, only for an embedded/linked image file.
Scaling factors of width and height of any object could be additional fields in the Transform panel. Maybe one day.

In the absence of a proper solution I have been using the following workaround when copying and pasting from Word:
In addition to my target Publisher document, I create a second, empty Publisher document and delete all the style definitions. I import into this second document the styles from my target Publisher document. Then I copy & paste my text from Word, having made sure in advance that all the style-names match up. It's not important that the style-definitions match. Repeat Step 2. At this point I get the "Imported Text  Styles" dialog and replace all the conflicting style-definitions with those from the target document.  Finally I copy & paste from my second Publisher document into the target Publisher document. There should be no style conflicts and no new styles (like Title 1) should get created: mostly that works. Is this tedious? Of course. But it's a lot less tedious than the manual merge big smile had to do. (If you still lived up to your name after spending 40 mins on that, big smile, then hats off to you!)

This behavior wouldn't need changing if anyone at Serif would have thought through the issue when being developed and made the feature correct in the first place. 

Yep. This is one of those things that should not be as hard as it is. I can sympathize if Serif wants to change it but just haven't got to it yet, given the many things the users and they themselves want to accomplish. However, I do hope the current situation is not the intended end goal on this matter.

Fingers cross they fix the table of contents style sheet bug and the duplicate style sheet bugs!!

It would be better if it was in Publisher natively. Especially when using automation software to go through multiple pages. Having to switch to Studiolink first adds unnecessary complexity. 

Thanks. Issue logged. 

Hi @big smile,
We are aware of a similar issue, but it should only happen with PDF files, and only when you reload the document. If you do find a pattern, please let us know.

Automated caption tool would be great...

No.

In the end, I was getting close to a deadline, so I re-made the document from scratch and it works now. I guess maybe something had gone wrong? I do importing another Publisher documents into other publisher documents a lot, so if I run into problems in the future, I will reach out. 

+1 for "non-printable" layers...

Hi everyone !
So far I used Affinity Designer just on small individual taks or illustration, but I recently had to use it extensively to make an educational video with a friend of mine. This requires to do around 50 different illustrations,  mostly custom creations with few assets from Freepik here and there. I had to learn both flat design characters drawing and Affitnity Designer Photo.
As a global feedback for Affinity Designer, I want to say that it was a very pleasing software to use (nice UI, no lags, no crash), and I'm glad it has this very nice business model.
The video is in French, but here the result :
 
 
During the elaboration of this work, I find several limitations we could have make it easier. I opended and bumped various other forum threads, but here is a reacap of things I would really love to have for the next series of illustration I would have to make :
 
 
This one is a must have for me. Almost all my illustrations have some kind of symetry involved. This will really help
 
 
This will really help making some variations for a duplicated objets. Would be very nice !
 
 
This would help making some automation.
 
 
 
This would be the Graal and ultimately could solve other issue, like layer name processing etc. It would be very appreciated !
 
 
If I had to choose only one, the first I mentioned would be really helpful. Please bump the thread if you agree, hoping it will interest Affinity Designer devs
 
Thx for your attention, Cheers !