Dave Harris

Hazelg, If you could attach or send me the PDF and .afdesign file, I'll take a look at it.

Hi Hazelg, welcome to the forums. This beta is now redundant as the Mac App Store version is the most up to date version available. That's why it won't run. Affinity Designer can export PDFs at 350 DPI, but that resolution only affects raster/bitmap graphics, not vector. Vector graphics use a decimal representation, and the DPI doesn't matter for them. Do you think your project is using 72 DPI for raster? In File > Export > PDF, after the Raster DPI control there should be a note; if that says "(Nothing will be rasterised)" there should be nothing to worry about.

Hi lostsatellites, welcome to the forums. You are probably using a stroke setting that is not supported by those file formats. In that case we have to expand the stroke into a shape to preserve its appearance. The Stroke panel settings most likely to cause this are Align:, which needs to be Align Stroke to Centre, and Join, which needs to be not Bevel Join. Using a pressure profile will also cause this. I hope this helps.

In the Stroke panel this is called a miter join, and the number to change is the Miter: on the right side of the panel. It defaults to 1.414 but for sharper joins you need a bigger number.

Oliver, we will fix the clipping, but it will take a while longer now.

Thanks for the report. This should be fixed in the next beta. Changing the stroke alignment will probably cause the text to be converted to curves (since PDF doesn't support aligned strokes). As a workaround you can make this happen for any alignment, by setting File > Export > PDF > More > Embed Fonts: Text as Curves.

That is a limitation of Illustrator. If you open the PDF in Acrobat Pro and look at the Layers pane, you should see the layers (and be able to hide and show them). If this doesn't work, then something is wrong with Designer and we can look into it. If it does work, then it's Illustrator that is refusing to recognise the layers.

This surprises me because I would expect it to work for for old document too. If you can attach an example .afdesign file, or send one to the support email, I will take a look and find out what is happening.

This was fixed in 1.4.1 (beta 2).

Yes, this is part of v 1.4. There's no specific UI for it; layers are always exported with their names. For example: New document Create a layer Add a shape Create a second layer Add a shape Export as PDF with any of the presets Open in Acrobat Pro Show the layers pane Layer 1 and Layer 2 are listed, and can be shown and hidden. I hope this is what you were expecting.

I'm afraid not. To do that would involve decoding the fonts embedded in the PDF, which we don't currently attempt to do.

Our PDF Export now includes named layers if the PDF level supports it (that is, > 1.4). They become optional content. We don't currently export hidden layers, and it is just Layer objects and not groups, so not all the structure is preserved.

Affinity Publisher won't have footnotes in its initial release. They will come later.

I'm sorry; I don't understand what you are asking for. Could you be more specific about the configuration of marks that causes the problem, and how it should be changed?

In my experience most PDFs get smaller. We have more options to control the size, including JPEG compression, downsampling, and font embedding. If you could attach an example .afdesign document that shows the problem, we can take a look. As you've noticed, it's not all files because vector-only ones get smaller, so there may be something that you commonly do that causes the larger size.

I've not been able to reproduce it either. Can you open the Typography panel and check whether you have anything unexpected enabled? If the problem only affects one character, it may be that you have some OpenType feature replacing the 'e' with an alternate version, such as a superscripted one.

The compression formats we use for PDF export are JPEG, PNG and Zip. JPEG is a lossy image format, and we provide an option to disable it in case you need images to be pixel-perfect. (That's the option Darren describes). We don't currently provide any option to disable the other two because they are both lossless and should be universally understood. We could consider a feature request to add such an option. However, I don't think we'd be able to do it soon, and as far as I can tell your vinyl cutting content is saying the problem is in their software and they already have a fix for it.

Sérgio, AI should be able to open our SVGs, and usually can. If you have one that doesn't work, attach the .afdesign file here, or send it to our support email, and we'll take a look.

I'm afraid support for Tamil is going to be a bit sketchy because we don't have any Tamil speakers in the company, and we don't claim to support it. However, if you can send the font you are using to our support email, I will have a look and see what is happening. Since Tamil is a left-to-right language, I would have hoped our generic OpenType support would have been enough to get it working. We will only use the font to investigate this problem and then delete it.

Thanks for the report. This will be fixed in the next release. (I don't think it made today's beta.)

I wouldn't have thought it would be necessary to have a rearrange option during export. Artboards are exported in is the same order they are created, so normally there should be no need to reorder them at all. New document, create 3 artboards Artboard1, Artboard2, Artboard3, and they'll export as Page 1, Page 2, Page 3 respectively. We plan to add proper multi-page support, with a Pages panel, and that should render this issue moot.

Artboards are exported in the order of the Layer panel, lowest first. (That's also the order that objects are drawn in.)

Text wrapping around other objects will be a Publisher feature. Here I meant text wrapping within a frame. Designer (and Photo) both do this, even if the frame is not a rectangle.

By default Frame text has paragraph space after, and Art text doesn't. I'm guessing this is what is confusing you. The difference is because of their different roles. Frame text is for body text with long paragraphs that wrap; space after is the typographically best way to separate the paragraphs. Art text doesn't wrap and so isn't suited to long paragraphs. Adding a space after each line would be annoying. If you set Frame text not to have paragraph space after, its vertical spacing will behave like Art text. There's no difference in how their 12pt leading behaves. Leading should normally be set on paragraphs, not characters. Paragraph leading does honour small sizes. For example, if you set it to Exactly 8pt, then you'll get the overlapping lines you expect. Setting leading on paragraphs will generally ensure the vertical spacing is uniform over the whole paragraph. The character leading override is only for rare situations where, for example, you have an equation or something else in the text that needs a bit more space. In general, the leading used will be the highest leading in the line, so changing leading override for one word can only make it bigger. However, currently it behaves as if every line had a character with the paragraph's leading. I agree this is probably wrong so I'll get this changed. If you are using leading as intended it should rarely be an issue because you'd rarely want one line in a paragraph to have smaller leading than all the rest.

Each character of text has a language attribute. Words are spell-checked in the language of the first character of the word. You can have English words checked against an English spelling dictionary, and Norwegian words checked against a Norwegian dictionary, if you set each word to have the appropriate language. You can change which language a piece of text has, by using the Character panel. Does that make sense?