h_d

You can find out about macOS data detectors here. Doesn't look as though they can be turned off in Preview.

In macOS Preview you can ctrl-click on the number and then choose Copy from the contextual menu:

I have tried Acrobat Reader for Apple Mac with my test pdf and it doesn't display a phone number popup.

MacOS Preview. It's clever like that. Not an Affinity thing.

Or do you mean something like this: I drew the L shape with the Pen Tool in Polygon Mode, then adjusted the text wrap using Text - Text Wrap - Edit Text Wrap Settings.

Draw the shape with the Pen tool in Polygon Mode, close the shape then Layer - Convert to Text Frame. You can adjust the nodes of the text frame using Node Tool.

Also make sure that you have selected the layer that you want to cut from. Screen Recording 2023-02-07 at 20.53.22.mov (I rasterised my original Rectangle layer to turn it into a Pixel layer.)

Turn on snapping. Screen Recording 2023-02-07 at 20.42.11.mov

Is this what you want - Screen Recording 2023-02-07 at 20.38.02.mov (using the Gradient Tool on a Radial gradient)

The Basic tab in the Brushes panel (Window-Brushes in Photo v2) includes a number of 'feathered' or soft-edge brushes: And hiding under the unobtrusive Edit Brush button is a plethora of settings:

There's a camera setting for the E-M1 MkII that switches between AdobeRGB and sRGB. As far as I can tell, the only way you can check the setting in Affinity Photo's Develop persona is via Window-Metadata-Raw Data and then scroll through hunting for the ICC Profile: (This is from a Panasonic .rw2 file.) But I have to confess I'm clutching at straws offering that as a solution. It may also be something in your RAW conversion settings. If you could zip and upload the original .orf files someone might be able to double-check.

One option would be to omit the outlying exposures (P2030016 and P2030019) and leave de-ghosting turned off when you do the HDR merge. This will avoid introducing the blurred whisker in the long-exposure image: (Out of focus? Camera shake? Cat shake?) With the following settings: I get a tone mapped image like this: You can then make further destructive tweaks in the Tone Mapping persona or non-destructive adjustments in the Photo persona. Not sure about the reasons for colour cast, but it might also be worth trying with the original out-of-camera images, and checking the camera's Color Space settings. The files you uploaded have an sRGB profile but if the originals were shot using AdobeRGB the conversion may have caused issues.

You could install the free 30-day trials and test things out. You have nothing to lose. To say 'I visit here and see bugs, so everything must be wrong' is like saying 'I visit a hospital and see sick people, so everyone must be ill.'

You can get a 30-day free unlimited trial of Publisher (all functionality) if you scroll to the bottom of this page.

That's mainly because it's not hyphenated, and I haven't made any adjustments to word or letter spacing. Here it is with Auto-Hyphenation on (no other changes): Turning on hyphenation in my Pages example has a less dramatic effect because the frame is much wider and the spacing can be more evenly distributed:

You might want to clarify 'Football' too ⚽ / 🏈 / 🏉 😉

What I meant was that the original shape (in Pages) and the new shape (in Publisher) don't have to be the same width: justified text copies and pastes from one to the other without any spacing issues. Original text in a Pages text frame: The text from Pages copied and pasted into Publisher:

I think it depends on compatibility between Publisher and the source application, and possibly on the OS too. For example, pasting styled text from Apple Pages into Publisher seems to work pretty much perfectly - justification, indentation, leading etc are replicated exactly. Spaces between words are accounted for in the justification engine - the shapes of the source and target frames don't come into play. I agree though that in many cases

What happens if you Place the pdf into an existing Publisher document? I get all sorts of crud if I Open, but this if I Place test.pdf: (Publisher is not a pdf editor...)

No worries, hope my first suggestion makes your workflow easier.

Or what's not on the screen...

Press the Tab key. Alternatively, go to Window - Studio - and choose Show Left Studio:

Good evening, Personally I wouldn't rely on accurate conversion of pre-formatted text from Word. I would paste the text into a plain-text editor, remove any and all formatting, copy and paste into Affinity and apply all the character and paragraph styles there. That way you know you're getting what you want. (I'd also use Publisher rather than Designer for a newsletter, but that's up to you...)

Deselect to remove the pixel selection, then click on the HSL Shift Adjustment layer and paint on it in black or white. (It's a mask.)

You will definitely need a data source to start with, in order to generate the fields for the merge. You can't just type them into the Merge Layout document: they have to be inserted from the Fields panel. However, if your different sources have the same data structure and field names, you can delete the original source in the Data Merge manager and add the second source to your existing Merge Layout document. Brief illustration. Here I've got a 6x6 Merge Layout document with two fields ('code' and 'Number') generated from Data Source A: When I click Generate it creates a new merged document. The 'code' in each case is just the letter A, the 'Numbers' are sequential from 1-36: I save and close my A merged document. The data merge layout document is still open. In the Data Merge Manager I delete Source A: And replace it with Source B by clicking the insignificant little icon at the bottom left: Source B is identical in structure to Source A, and has identical field names, but the 'code' fields have been changed to the letter 'B'. I click Generate again and a new merged document is created, this time with the data from source B: So basically you can re-use your Data Merge layout with different sets of data, as long as the data structure and field names are the same. Hope this helps.