BofG

It's probably used a lot less since CC has become more widely adopted. I remember using it quite a lot, different companies and freelancers had various versions available and it made collaborating fairly straightforward. People have given good reason for needing it, maybe it is just a small percentage of the user base. I get the business logic of it, they are a small team and lots of other things people want are still not implemented. At the same time, maybe fostering some goodwill wouldn't hurt. In any case, from a technical standpoint it's possible and exists in other software.

That's a straw man argument. Are you saying that people are very unhappy that Adobe lets them save for older versions? It's a business decision. Time versus return. I'd wager there's also an element of "carrot and stick" about it all. The great new features are the carrot, and for those who don't have a need for the new features, well then there's the stick to help them along 😃

V1 does the same, it's nothing to do with kerning. There's an option in the export for "use longer t spans" which fixes it.

Show a screenshot of the colour tab under document setup. What you have described should work, so something is wrong somewhere.

I forget the exact name of the button, but drop the PNG into your file and there's a "k only" button that will show on the context menu. Edit. Oops, this button is in Designer and I realised you said you have publisher. Not sure if it's available there.

Really? That cannot be true. How would anyone producing artwork intended for PDF know where the limit is?

Change "resample" to "nearest neighbour" on the export settings.

Divide and conquer. Start by exporting a single page, and upload that. Problem still? Now you only have to find out what this issue is by changing things on a single page. Works as a single page? Try exporting two or three. Repeat until you find out where the issue comes from.

I completely disagree, you said it yourself that the Adobe suite allows back saving by dropping incompatible file features (it just drops them back to the next appropriate primitive element). This is a completely proprietary file format, known and used only by Serif. They were free to change it as needed, they could have even put some changes into the last V1 update if necessary. This was a time/business decision. I don't see why people feel the need to try and make out like it's an impossible task.

I agree that it should have been included. It's not as though there are multiple previous versions, it's one step and those new file inclusions for V2 could have been planned with a fall-back from the get go. The business case probably stacks up, just feels a bit like the users have been left out of the equation.

I can't directly help, but what I would advise is you immediately take a backup of that file to a separate location (disc or cloud).

I'm not sure if this is meant to be subtle comedy? Anyone who's used design apps in the past decade will know that's exactly what gets done. It's a shame there's no back-saving, it was already a pain being an Affinity user in an Adobe world, but now we will even have to be incompatible amongst ourselves.

Why have you chosen to use those? What reason is there for not exporting from Affinity directly to PDF? It would help to know which Affinity application(s) you are using.

Presumably someone has the original vector file - if you want the best quality output you really should be starting from that file.

That rapid tables thing and other such converters really shouldn't be recommended. They are nonsense for proper colour management. OP - do you have a printer profile for your sublimation material?

I'm betting it's the fill mode. The path direction is probably different between the two dots (it looks like one is flipped from the other).

I'd first off try setting "flatten transforms" on in the SVG export settings (click the "more.." button to see it).

It won't affect it on each side in isolation, but combined the margin of error doubles. E.g. side one shifts 1mm left, then side two also shifts 1mm left. Your offset is now 2mm. Of course it's possible that the second side shifts the opposite direction and so reduces the offset.

https://forum.affinity.serif.com/index.php?/topic/109961-export-svg-wrong-size/&do=findComment&comment=727443

Reverse image search and DMCA takedowns are the easiest. Failing that you need money to sue people. There's nothing you can do to the image to protect it if you want to publish it online without a watermark. If you control the page it's going on you can use a "noindex" tag to stop search engines picking it up.

I'm not 100% sure what you mean here, was the source document in Adobe RGB (1998) for both prints?

Draw two rectangles, one the full size of the image, one inset by the desired border size. Subtract the smaller one from the larger one. Set the fill colour on the resulting shape to white with a low opacity, and the stroke to red with inside alignment.

Does the Mac version still have the slow start up issue?

Preferences > user interface > Decimal places for Unit Types > Degrees

Attach your current attempt here.