jstask

Since I do not know how to create such a profile, I did another workaround: Export 2 PDFs, an X-3 for the CMYK part and an PDF 1.7 for the RGB parts. Layer merged together in Acrobat, which could become a tedious task. So i hope this will get fixed soon, since I don't want to be the person responsible for color conversion if no cymk value is provided. Besides that, I would prefer an output intent independent PDF.

This works. It's counterintuitive, since the edit color dialog for palette color does not offer a transparency value. The reason for an exact numeric value is repeatability. I think Affinity should improve this.

IF I need different text frames with a certain opacity percent applied to each background colour, it's the way to do it.
If I ask someone, or want to decrease 5% opacity, I want it to be possible. If I want to set different objects at the same opacity, I want to be able to do it, in a month or six, simply using the same value. If I want 10 objects ranging from 0 to 10% opacity, etc.
Of course we can use tricks, there's always be useful tricks to use due to a lack of feature... but please, not for simple actions like those.
 
And I really don't understand this inquisition.
Especially for things that other already mentioned, meaning that several of us need what isn't too complicated to add (at least in this case).
The apps lack value inputs for some colour panels, degre value for gradient position, percentage value for the amount of resizing done when pasting an object or a style, etc. And those input are sometime available in other panels or effects!
Perhaps it sound strange to you that we want complete control and the ability to modify perfectly some values, and not only "à la louche"... but it's how some of us work.  And each time I dismissed a warning about such missing options, in the end, it came back to bite me, because I needed the option later, and it was too late to redo the whole work in another app or a waste of time.
And it's not because it's impossible, the value exists, it's just not displayed in a numerical input.

Your comment sounds a bit weird. If it is a matter of efficient workflow and you only need this fill opacity for a second object (or "a few"), then it may feel cumbersome to create a palette swatch first.
Of course, you can easily get around this by not using a fill colour for the text frame at all, but instead setting a separate shape object and its layer opacity. – So the question is not whether an improved user interface would hurt, but rather why a user interface would hurt first + thus cause a discussion.
The Affinity UI is even more weird: If you created a global swatch with reduced opacity then there is no UI to edit its opacity afterwards – which can require the creation of a new swatch instead, making the "global" property useless this way.

 

I just noticed that the opacity value in the upper right corner of the swatches palette reflect the current value applied to the object, but you can't change the value of the actual swatch.

This works. It's counterintuitive, since the edit color dialog for palette color does not offer a transparency value. The reason for an exact numeric value is repeatability. I think Affinity should improve this.

Hello!
As discussed on several threats here in the forums, a european PDF-"Master" and notable member of some PDF-workgroups posted today
https://pdf-aktuell.ch/pa/language/en/disastrous-pdf-x-4-compatibility-with-new-affinity-publisher-1-0/
Please fix the PDF-import or add a PDF-Pass-through. Its really important for using Publisher day by day.

Affinity Publisher looks truly excellent — but I can’t see how to add either footnotes or endnotes. Where have you hidden them?
[There’s a small bit of my brain that’s telling me that you haven’t implemented either yet, but I can’t believe that. Of what possible use would this beautiful new app be without such a basic functionality? I think it’s more likely that you’ve hidden them somewhere or that you’re calling them something else and that I just haven’t found them yet. Please tell me that’s right....]

Hi there, I can't wait for the full retail version of Publisher, will be putting in my pre-order (I know it's close) in the next couple of days!
But I'd like to know if there's any chance anyone has thought about adding either a prepress plug-in or Persona to fully press check documents as you can in Adobe Acrobat DC Pro?
For example check that spot ink or CMYK separations and rasterisations are correct as required for the print destination.. Acrobat has remained as my only tether to Adobe, it would be nice to be completely free at some point in the future! Anyone else think this?
Thanks for listening... 
Cheers
Kind Regards
Piers Le Sueur

With the default settings i experience some problems with black colors.
First i would suggest to add a default document-swatch with a overprinting black, (and probably a non overprinting one). I need these colors in every print-design.
In the default PDF export-settings (except the web-preset) the checkbox is marked to embed profiles. For CMYK documents i don't want this behaviour. In most situations i would prefer to export untagged CMYK colors (Device CMYK, instead of ICC-based CYMK) and tagged (ICC-based) RGB but with a output intent set to the documents cmyk profile. I did not manage to do that with Affinity Publisher (and Designer)
With the current PDF export presets a black color is always tagged causing acrobat and printers to separate k into cmyk due to the color-profile.

… wie viele Jahre — ja: Jahrzehnte — sind wir ohne diese Funktionen ausgekommen, ohne dass jemand aud die Idee gekommen wäre, sie als „essentiell“ einzufordern?
Keine Frage: Diese Funktionen sind wichtig und wünschenwert, aber sind sie wirklich zu erwarten in einer Vorversion zur ersten Ausgabe eines 50-€-Programms?

With the default settings i experience some problems with black colors.
First i would suggest to add a default document-swatch with a overprinting black, (and probably a non overprinting one). I need these colors in every print-design.
In the default PDF export-settings (except the web-preset) the checkbox is marked to embed profiles. For CMYK documents i don't want this behaviour. In most situations i would prefer to export untagged CMYK colors (Device CMYK, instead of ICC-based CYMK) and tagged (ICC-based) RGB but with a output intent set to the documents cmyk profile. I did not manage to do that with Affinity Publisher (and Designer)
With the current PDF export presets a black color is always tagged causing acrobat and printers to separate k into cmyk due to the color-profile.