Dave Harris

I've attached an example .afdesign file, and also the SVG that Affinity created with the "for export" preset. It seems to me it the transforms are organised how you want. There is a transform on the Person group, and the other elements (I just drew a face) are nested within it and so relative to that transform: <g id="Person" transform="matrix(1,0,0,1,137.84,395.893)"> <g id="Mouth" transform="matrix(4.43588,0,0,4.14447,-835.145,-914.053)"> <ellipse cx="284.858" cy="326.466" rx="41.792" ry="35.78" style="..."/> </g> <ellipse id="Eye-2" cx="371.395" cy="396.322" rx="31.512" ry="25.832" style="..."/> <g id="Eye-1" transform="matrix(1,0,0,1,-19.0497,-7.6625)"> <ellipse cx="498.755" cy="416.346" rx="28.584" ry="31.132" style="..."/> </g> <g id="Mouth1" transform="matrix(-0.005566,-0.999985,2.21284,-0.0123169,-728.309,884.612)"> <path d="..." style="..."/> </g> </g> <path id="Island-2" d="..." style="..."/> <path id="Island-1" d="..." style="..."/> Example.afdesign Example.svg

Saivan, I've answered in the original thread, here, because I saw that first.

Does unticking File > Export > SVG > More > Flatten transforms give the relative transforms you want?

Jakerlund, that sounds like something text styles would help with. I happen to be working on that now, for inclusion in 1.5 later this year.

We're aiming for the end of this year, but if it takes longer to get it ready we will take the time necessary.

Specifically, ticking FIle > Export > SVG > More > Add line breaks will make the exported file a lot more readable for humans. It's ticked by default for the Export preset, but unticked for Web in order to help minimise file size.

The purple strokes are to highlight snapping candidates. You can hide them by unticking Show snapping candidates in the Snapping Options. This will leave snapping on.

If you could attach the document here, we can take a look and see what is going on. You can delete everything except the offending text (and use Save As) first, to get rid of anything confidential.

Hi Vernon, welcome to the forums. We do preserve Pantone spot colours from PDF. I'm not sure about EPS but I suspect not. The colour panel show show the colour as a tint of the Pantone colour when the object is selected. It does need to be in the PDF as a named spot colour, not a process colour.

This is a bug which will be fixed in 1.5. Meanwhile, one workaround is to change the colour after you've placed the text but before you start typing. Also, if you place the text, set the colour, then click away without typing, it will set the colour for new Art text.

The most likely setting to help is File > Export > SVG > More > Set viewBox. Some apps seem to want the viewBox, and some don't.

The large file sizes happen because our file format is optimised for loading speed rather than size. The original images were probably JPEG, but in we store them as ZIP which does not really compress photographs at all. To add insult to injury, we typically store the JPEG as well, and then store multiple copies of the image at successively smaller resolutions. There was a plan to have a "minimise space" option on the Save dialog, but it's not happened yet. I think we will have to do something before Publisher, because Publisher documents could be hundreds of pages and have a lot of images.

Ah, yes; Illustrator will do that. I don't think there's any way around it. Illustrator doesn't support EPS gradients unless it created the file itself.

It depends on the gradients. Simple linear, radial and elliptical gradients should be fine, at PostScript level 3. Affinity has a Conical gradient, which EPS does not support. Noise in colours, or transparency, or blend modes will also cause rasterising . Have you tried importing the EPS you just exported back into Affinity, and then using the Layers tabs to look for unexpected images? That can help track down which objects got rasterised.

Advanced features are parts of the PDF specification that Illustrator and some other apps don't support, but which are worth using because they improve print quality. In this case the particular feature is 1-bit transparency masks, and there is a bug in Affinity that means they got exported wrong. Switching off advanced features is a workaround that hides the bug. We'll fix the bug for the 1.5 beta.

It should be in the 1.5 beta, which should available in a matter of weeks rather than months.

Well, a user-defined unit would need some extra user interface to define it, and it would need to be stored in the document, which makes it different to all our existing units. Currently you can change the number of decimal places for units in Preferences, and that would need to be re-thought now the list of units is not fixed. It's all doable, but it takes more time than we'd like. What other units do you need? Bear in mind that inch-marks and foot-marks were supposed to be including from the beginning, and it's a bug that they don't work. They will work in 1.5.

It looks like Corel Draw doesn't support PDF embedded fonts. Some apps don't. It's quite hard to do. Although Affinity can embed fonts in the PDFs it exports, even it doesn't read fonts embedded in the PDFs it imports (yet). I gather switching off File > Export > PDF > More > Allow advance features helps produce PDFs that Corel Draw can read.

Have you tried using Art text? Frame text will evolve a lot for Publisher, when we'll have multiple columns in a frame, and flowing a single story between multiple text frames. Any options for auto resizing frames, and UI involving frames, will have to be considered in that context.

I don't know if creating baseline grids will make it into Designer or Photo. They will be able to edit Publisher documents that have baseline grids.

We're talking about the advance from the top of the frame to the baseline of the first line of text. I used "baseline" as short-hand for that phrase. Ben has been working on improved snapping for text. This will include a form of snapping text baselines. This is different from a proper baseline grid, which we will also do.

We don't currently support baseline grids, but when they do, they will affect the text baselines directly, so the first baseline advance will be irrelevant. I am wondering what app you are using that draws the text frame as you describe. I just checked InDesign and Illustrator, and neither includes the accent area in the text frame. InDesign has Object > Text Frame Options > Baseline Options that purports to support Ascent and Cap Height, but its Ascent does not include accents either. Illustrator doesn't have the option that I can see, and seems to always use what Indesign calls Ascent. The baseline we use seems to match Illustrator.

You can convert text to curves during the PDF export, by using File > Export > PDF > More > Embed fonts: Text as curves. I hope this helps.

The height of the caret is the height of the text (including the area for accents etc). Why is it a problem if it goes outside the text box? On a non-retina display the old caret was 2 pixels wide, with a half-pixel white shadow. It's now 1 pixel wide, with the same shadow. On a retina display OS X will scale it up to double those values.

I'm afraid not. We only support outline glyphs, not bitmap glyphs, which is what emoji are.