Dave Harris

Another option is to pay for the full version, and then if you don't like it use the Mac App Store's refund policy. Chances are, if you liked it during your brief trial, you'll want to keep it anyway. We also have a trial version of Affinity Photo. Although a different app, it has a lot in common with Designer and testing it may help you decide.

PDF does not have a DPI setting, so we deduce one from any embedded bitmaps we find. Obviously it doesn't make much difference to the vector content, but doing this does mean that any areas rasterised on export will get similar quality to the images already there. I tried exporting at 72dpi and 192dpi and then imported into PhotoShop. It used 300dpi for both, so I think it is just lucky its default happened to match what your document originally was. I'm not sure where you are seeing DPI in Illustrator, but when I exported to PNG it wanted to use 72dpi for both, so again I don't think it is doing anything clever.

Not yet. It's getting closer to the top of our list, along with PDF/X which is now in beta.

Paul, that only holds for PDFs and .ai files. The reason being, having the replacement fonts in advance helps with text positioning. A more general Find and Replace for fonts (and other attributes) is something we plan to add later.

This is by design, I'm afraid. EPS specifies the document size as an integral number of points. The document size is 102.75pt x 137.25pt. You can see this by changing the document units to points, selecting the white background rectangle, and looking at its size in the Transform tab. The height gets rounded up to 138, which is why the top rectangle is offset by 0.75pt. (The offset is at the top rather than the bottom because EPS puts its origin at the bottom left instead of top left). If you import the EPS again, you'll see that the white background rectangle has the same size, and the page is 0.75pt taller. We do write a hi-res size as well, but since it's optional and many other apps (eg, Preview) ignore it, we ignore it too. When you change your document 72dpi, because the document units are pixels, you are actually making it smaller. You are also giving it an integral size in points, because there are 72 points per inch so 183px at 72dpi = 183pt exactly. That's why the problem goes away. EPS is not a great format, especially for web-related work. If you must use it, I recommend you set your document size to be an exact number of points.

I haven't decided what to do about them. At the moment we output simple gradient fills as vector. To stop Illustrator warning about them we'd have to rasterise instead. That will make the PDFs larger and lower quality. That would be a shame, especially as Illustrator does seem to import them OK (it rasterises them itself). I could make it an option, but I doubt many people would find and use it, so that would be a cop-out.

It seems to be to do with the way the clip is made. If you first create the text, then Copy the pattern, select the text and use Edit > Paste Inside, the result is the same visually but exports as vector. You can get the same result by dragging in the Layers tab, but you have to put the pattern below the text rather than vice versa. Creating the clip by dragging the text alongside the layer you want to apply it to, seems to confuse Affinity because the text can have multiple strokes and fills. It's only safe to export as vector if none of the strokes or fills would be visible, and currently it doesn't bother to check.

I've fixed that too. I think that's everything mentioned in this thread (apart from the Illustrator warnings).

Try using File > Export > EPS > More and check Minimise size and uncheck Relative coordinates. I've downloaded the TypeTool 3 demo, and it failed for me with our default export but succeeded with those options, for simple vector shapes.

If you use File > Export > More, most formats have an option for whether to embed the colour profile, which you can switch off. The Export Persona has this too. In practice it doesn't work very well with the Mac App Store version. It should work with the current beta, which you can download from the relevant sections of this forum.

Thanks. I can reproduce that.

Makes sense to me. You can always Convert to Curves later if you need to, but you can't convert to non-destructive later.

We're planning this relatively soon. Now we have PDF/X, we want to complete the other main pro-print options so we have a complete set; this should include Pantone and bleed.

I've fixed the CMYK colours getting inverted in Illustrator, the issue with the nose on the moon, and the failure to export at all. I still get warnings from Illustrator about gradient fills and 1-bit masks. These will be in the next beta. I've not yet looked at the issue you raised in #9. Does it also happen when printing (in the preview)? Could you send the document?

I'm not familiar with the term, "postscript hash text" - do you mean text that has been converted to curves? We don't force text to curves for PDF or SVG; currently we do for EPS, and for PSD it gets rasterised. There is an option to convert to curves, in File > Export > More, so the first thing may be to check that didn't somehow get switched on. Is it just simple text, or does it have a complex fill, stroke, transparency or effects, or is it used for vector clipping?

Did the outline get rasterised? Does it work if you create a simple rectangle, with a solid fill and no effects, noise or transparency, and export that, just to see if it works?

Not currently. I believe we show the same area that Acrobat shows. I'll consider adding an option to include the bigger area.

This will be fixed in the next beta. That's right. For vector clipping the curve has to be a pure vector, without any colour of its own.

Thanks.

Ah, I was expecting an Affinity Designer file and that looked like a screenshot of one. I couldn't reproduce the issues in the first post with that (and it's hard to see where the rectangle on the nose would come from in a plain JPEG). It does look like Illustrator is having a problem with our CMYK JPEGs. That would be an Illustrator limitation, as Acrobat Pro not only loads them correctly but the pre-flight check confirms they are PDF/X-1a. I'll see if we can work around it. PDF/X-3 and above will be OK because that supports RGB. I do appreciate it. I was getting lots of reports of issues, but no sample files I could reproduce them with. Thanks. I've found and fixed a problem we were having with alpha with that. It now exports, but Illustrator is very unhappy with it. It says, "An unknown imaging construct was encountered". Again, Acrobat Pro pre-flight checks say it is fine. I'll continue to look into it. Thanks. I can reproduce the nose problem with that.

This will be fixed in the next beta. It was due to text not getting its line styles set correctly, and hence going out with mitre joins. For some reason the font has some spikey corners that produced big mitres. You can get the same result in Affinity by changing the text stroke.

Removing metadata should be available in the next beta.

I've not been able to reproduce any of these problems, so it would help if you could attach a file that does. If it is any file for you, then it should be easy for you to find one. Simple files preferred. Have you tried using File > Export > More > Use old PDF export engine?

Is the original Affinity file available for me to try with?

Can you attach the original file so we can take a look? And which app are you using to look at the PDF? You can control whether unsupported features get rasterised or ignored with File > Export > More > Rasterise > Nothing.