David in Яuislip

Gotta think of the forum server space
8,533 GradMap.afphoto
4,618 GradMap.psd

Try a gradient map, a little fussy to create but you get to choose where the tone splits are rather than rely on posterise which I've never had much luck with. The gradient map is in the psd as they can't be exported, at least I don't know how to

GradMap.psd

Make sure that Resample is ticked in the resize document dialog

Aha, cannot change dimensions if resample is off so Plan B
Use the transform panel with the Lock aspect ratio chain clicked on
Type *2<enter> in the width box then Document/Unclip Canvas
Both approaches work here

In the Data Merge Manager you can specify the separator you want to use:

 
But using LibreOffice Calc, I have no problem generating a CSV file whose fields contain the "," character, and which uses the ";" as the separator. And as mentioned above, any fields that contain a "," are automatically quoted. And the file works properly for Data Merge.
Samples (using Publisher 2.5.0.2402, but should open in Publisher 2.4):
data-merge-test.afpub Untitled 2.csv

Affinity csv import doesn't allow sep=; at the top. I tried it earlier to test here but it assumes there's another record
name;date of birth
"John Doe, xyz";"15. September 2015"
should've worked, as it doesn't I would check the encoding, if it's not UTF-8 then convert it, if it is then I give up
Tsv might be an alternative but I've never got that to work

I’m guessing that this shouldn’t apply if
sep=;
is specified at the top of the CSV file, but in any case the OP says
 

<gemitus>
O cara, o cara, altera cara!
</gemitus>

I’m sure a discussion about limited use of Latin could go on ad nauseam. 

My use of Latin was limited to quod erat demonstrandum and I don't use that much these days
Accipio auctoritatem tuam - fidem Google

Yes, hyphenation is rather important as Latin can often be set in a column view alongside a language like Italian or English, on a page, so in two column view Latin needs to be hyphenated as has been traditionally in old Missals, as one small example.  

My previous experience with hyphenation dictionaries in the user area is that they have no effect
The program comes with hyph_la.dic as Mike notes
It's the only file in C:\Program Files\Affinity\Publisher\Resources\Dictionaries\la
I have added la.dic, la.aff & hyph_la.dic to C:\ProgramData\Affinity\Common\1.0\Dictionaries\la\
I created a new style based on Body but with the Language and Hyphenation set to Latin
As standard the word suspiramus hyphenates thus:
su-
suspi-
suspira-
suspiramus
After adding sus5p5iram5us to user hyph_la.dic it now does this:
sus-
susp-
suspiram-
suspiramus
Quid mirum
But apart from that is it correct to hyphenate Latin at all?
The language was pretty dead by about 700 AD and Gutenberg didn't print his Bible until 1455

It imports ok into V1.10.6, not that I will ever use it, it would be like going back to a dial-up modem

Thank you David in Ruislip. Intriguing. Will contemplate. This may be a bit beyond my skillset (eg. 'nest the shape into the clipping position' is like a foreign language to me). I think I'll have to do some Googling to be able to follow your directions. But I will....
 
 

I'd advise a trial of DxO Viewpoint, also integrates with Photolab, dead easy and superb results

That's great that it works on Windows, but it's not possible on macOS. I did try it out and it didn't work.
Affinity isn't the only Mac app with this limitation since most use the macOS implementation of Hunspell, including LibreOffice. One approach taken by some who want to use a supplementary dictionary is to merge the en_GB or en_US dictionary with the supplementary dictionary (alpha sorting and updating the count at the top of course) and then installing that merged dictionary. That approach works fine although it's obviously less convenient.

You should be able to do that with data merge
Use the spreadsheet to strip the file extension
Column B formula is =MID(A2,1,C2)
Column C formula is =FIND(".",A2)-1

Yes, please consider this because it will reduce the amount of scrolling needed to see all of your posts. For me, it is annoying enough to have to do that that I often just skip to the next topic.

Is this the "long shot"? (ps: how about a horizontal signature, less long?)

Possibly you can use Data Merge to place images together with text.

I can’t imagine this can be done in any Affinity app currently.
i would probably try to export as SVG and use any suitable script languages or text editor to change the color codes in a fixed place of that file and save the modified copy of the file under the name of the color.
You may create a vector layer and suitable blend mode (like color).

You can rename slices in the Export Persona like this


or use Ghostscript to produce both sets with little effort from the pdf, quite handy if you only have Publisher gswin64 -dSAFER -sDEVICE=pdfwrite -o NewTitleGS_%d.pdf ExtractingPagesAndImages.pdf gswin64 -dSAFER -sDEVICE=jpeg -dJPEGQ=85 -o NewTitleGS_%d.jpg ExtractingPagesAndImages.pdf Results 96312 NewTitleGS_1.pdf 154812 NewTitle.pdf 95441 NewTitleGS_2.pdf 154833 NewTitle_2.pdf 95419 NewTitleGS_3.pdf 154566 NewTitle_3.pdf 145405 NewTitleGS_1.jpg 148746 NewTitle_1.jpg 143307 NewTitleGS_2.jpg 146235 NewTitle_2.jpg 143722 NewTitleGS_3.jpg 146502 NewTitle_3.jpg For a few hundred files use %03d rather than %d and you'll get NewTitleGS_001.pdf etc

that'd be my suspicion 
On this pc which is hardly a racing bike, the spec is in my signature, the 100000x40000px psb loads in 2m 30s, ½ hour is unusable
Filling a selection of 32000x16000 with a colour takes 4s

Yes, edge sharpness, what we used to call acutance in the darkroom days
Lots of info about sharpening on the internet, much of it twaddle
If you read an expert, the late Bruce Fraser, he recommended using Luminosity blend mode and restricting sharpening to midtones between levels 25 & 200 which translates to 10 & 78 in Photo Blend Ranges. The attached macro attempts to do that, adjust USM parameters as required
As an example I took an image 5076x3806 px and resized using Bicubic to 800x600, saved as png without sharpening, with Photo USM at radius=0.3, factor=2 and the macro. These were converted to webp at quality 65 using cwebp
File sizes:
webp65    png    
34386    640974    SharpenNone
55290    788657    SharpenUSM
53586    761879    Sharpen25-200
Now a visual example. Note how a browser will follow windows display settings and upscale images. This can be corrected with Javascript. Note also that sharpening can be done on an unsharpened image by the browser. It's not much different from using an image editor and there is a good saving on filesize. File zipped  to avoid forum mangling
Bonus point if you know the location

Sharpen25-200Lum.afmacro SharpenDemo.zip

That's because it doesn't appear as part of the logo or the placed Photoshop file, it has been added to the Publisher file directly...

I doubt it as Canva has Magic Animate
Here I've used the mirror filter and simply taken screenshots at diffent Number of mirrors, stacked, cropped and exported as slices then
img2webp -lossy -m 6 -q 20 -d 300 slice1.png slice2.png slice3.png slice4.png slice5.png slice4.png slice3.png slice2.png -o out.webp
which can be viewed in a browser
img2webp is part of the cwebp package available at
https://developers.google.com/speed/webp
For other formats you could use imagemagick or ffmpeg
out.zip