Dave Harris

Hi, charlesonamac, welcome to the forums. Most of the EPS content of the first two files is a bitmap image rather than vector, and there's nothing we can do to improve it. If you can get the seller to provide it as SVG or PDF, that might be better. What's happening here is that Illustrator is embedding an Illustrator document as a comment in the EPS. When Illustrator opens it, it ignores the EPS and just reads the comment. We can't read the comment because the Illustrator document format is private and proprietary.

I'm having trouble reproducing this. It works for me on some test files. Maybe it is specific to your PDF. Could you attach one that shows the problem, please?

I don't understand; Affinity Designer supports text on a path already. Draw a line with the pen tool, click on it with the Art text tool, and start typing. Or use Layer > Convert to Text Path. No need to create a brush. Were you not aware, or am I missing something?

We certainly intend to do it, even though it's not listed on the roadmap. It won't be before Christmas, but we are aware of how urgently its wanted.

By default Affinity only imports the first page, but there are controls to choose which page, or select all pages, in the PDF Options dialog that opens. Since Affinity is not a multi-page application, in the Mac App Store version each PDF page becomes a layer, and you have to hide and show the layer you want to work on. The current Customer Beta supports artboards, so with that each PDF page becomes an artboard. Either way you should be able to access every page in the file. If it's not working for you, can you give us some more information? Are the controls in the PDF Options disabled, or do they get ignored?

Tile patterns are described here. Using them generally produces smaller and better quality files, but some apps don't understand them. If Flatten transforms is not checked, we attempt to preserve more of the document's group structure so that objects are described in the coordinate system of their container. If it is checked, we generally output fewer groups and transforms; for example, we transform the curve data itself before outputting it. Transforms have to be output for rotated text and bitmaps regardless. If Longer text spans is unchecked, then we try to reproduce the position of each character of text exactly, even if this means adding many tspans. If it is checked, we produce fewer tspans, but the text won't be positioned as exactly. That each line becomes a separate text element is an idiosyncrasy of how our export is implemented. Our SVG import is still fairly basic. Embedded fonts and fallback fonts are not yet implemented. Nor do we do tile patterns.

I have no idea. We have a lot of potential features and projects to juggle.

If you open them and install them using Font Book, Affinity should see them and use them. You might need to reset fonts (in Preferences) or restart Affinity after the change.

Hi, Riocordo. Eventually yes, but not this year.

Not before Christmas. Our goal is to update the Mac App Store before Christmas, and to meet that we can't be adding new features.

CherylEt has been flagged as a spammer. Which almost certainly means they posted something, as well as clicked the Like button.

That is the kind of thing Publisher will do.

If you check both Favour editable text over fidelity and Group lines of text into text frames, then Designer will try to turn text into reflowing paragraphs with tabstops and alignment. That is what Publisher will do, too; they will use the same code. We won't be importing native Indesign files.

OK, we'll give more control over printers marks.

Probably, but I can't promise anything at this stage.

Not for a long while.

Those are global preferences. Each document also has its own profile. Does Document > Convert ICC Profile... have PROPHOTO RGB selected? You can also override the profile during export, so check that ICC Profile is set to Use document format (which it should be by default in the beta).

The first forum post by new a user need to be approved before it becomes visible, to reduce the amount of spam posts we get. We usually approve quickly, but this time not quick enough. Now you're approved this shouldn't be an issue for your future posts.

It's a bug. We'll fix it for the next beta.

Currently no; printers marks are all or nothing for PDF. Is that a problem, or merely a preference? Not yet, but we plan to add that soon. When checked, it enables some PDF features that reduce file size and improve quality, but which some other apps don't understand. The features currently include gradient fills, 1-bit masks, stretched and stroked text, and tiling patterns. Hopefully this will be resolved when we preview bleed on the canvas, but it will be worth checking again to make sure it doesn't get overlooked.

I'm sorry, currently we have no preview for colour separations.

I believe we conform to all of that, except that Text as Curves is currently disabled, which we'll fix in the next beta.

If you tell us what the bugs are, we might be able to fix them. (Preferably with a simple example .afdesign file.)

We support the slightly later PDF/X-3:2003 standard. Do you have a printer that requires 2002 not 2003?

HairyDalek, thanks for the file. It does export here, but I am missing the JohnstonITC font, so it looks like it is an issue with that font. Can you send me a copy of that font so I can look into it? I'll delete it after. You can use a PM here, or send it to our support email. PDF/X-1a does not allow unembedded fonts, so the control is disabled, but I guess it should be enabled to allow them to be converted to curves.