rumo

I second this, like in the old thread.

@claidheamdanns I fully agree with your point of view. Without GREP styles I still miss a crucial tool. Whenever a project requires more then basic typography, like kerning punctiation or other microadjustments, I am lost without Indesign. I was told that the staff has it on their list, but that was two years ago.

+1. Came across this today. This is a basic typography feature, not something worth some kind of workaround. Looks like the more I use Publisher, the more I ran into those "missing basic typography features".

That’s a feature not easy to spot. I’d still like an option to have select/deselect not logged by the timeline, but the ability to branch the protocol is a completely different approach. I have to try and test it. Thanks Walt!

Yeah, but that’s still a workaround, not a solution, right? Thanks nonetheless @Johannes.

Thanks mate! Never thought of this, but it definitely is a better workaround (there could still be an option though).

Has this one been solved yet? Came across it recently and thought it would be my printer. Then prints from Apple Preview turned out to be fine, as always. So I ended up doing the same workaround as @Johannes.

+1 . You can’t do sophisticated typography without it.

Hi, is there any way to NOT have the select/deselect command included in the protocol? I have tried to get used to that ever since I switched from Indesign, and it looks like I can’t. For example, when I go back in history (protocol) to undo something to just have a look like it looked before and then deselect the current object to really have a proper look without disturbing blue lines around it, I can’t redo that because the protocol logged the deselect as an action. So whatever changes I did, I have to do them again. I doesn’t make any sense to me why select/deselect should be part of the protocol at all. Or didn’t I get something here? Best, Johannes

If we can open IDML files, are there plans that we can also export into IDML at some point? It would be just vice versa I guess. Thanks for the updates and all the necessary efforts. I appreciate it. However, I would be glad to see a world-ready paragraph composer, first-line only base grid fit, a pipette tool that can copy styles and GREP implemented. Then AfPub would finally be a full Indesign replacement for sophisticated book projects. 👍

Thank you very much in return @Jon P. I appreciate that. Maybe adding a feature similar to the World Ready Composer would solve the issue. And I have confidence that the you are interpreting the font correctly. However, neither Fontlab nor fontdrop.info nor Typeface have this feature and render the font as it is supposed to be, without any issue. What do you think about that?

@Alfred Cheers mate, that post got lost in translation somehow. My bad. Thanks Jon, it’s on its way.

My pleasure, @thomaso. Update: The font also works fine the Typeface font organizer and also in Fontlab 7. So unless I am not mistaken (possible) it is likely to be a bug in Publisher. I hope that somebody from the tech staff sees this thread and reaches out, so I can sent them the font file for investigation.

The text is set in German, and nothing happens when I change the language. Also, since the font only works in Indesign CC when the Adobe World-Ready Paragraph composer (aka. global) is activated, I thought that there might be something similar in Publisher. But I clicked myself through all options in the glyphs, paragraph and text box panel, without solving the issue.

Of course not ;). It is a pre-production version and some joints still need to be smoothed out. But that is not related to the problem I have with Publisher.

Hi guys, I am experiencing a weird behavior of Publisher with a preproduction font that lays heavily on the contextual alternate Opentype feature. The problem: The font is valid and works fine in Indesign CC 2021 and the Typeface font manager as well as on fontdrop.info. However, when I turn on the contextual alternatives in Publisher, all of them are rendered except for the ones related to the lowercase "i" (like "is", "in" etc.) . See first screenshot for Publisher (blue), second for Indesign CC (black). I am able to reproduce the issue. Please note that I can only provide the font file directly to the support staff. Cheers, Johannes Latest version of Publisher macOS Mojave (latest) Hardware Acc.: On

I still second this. Dear Affinity staff, this is a must have in the field of editorial design.

Any news on this? I know it’s about 3,5 years after the initial post, but I tried to to the exact as @PDL: I have exported DNGs from Capture One and imported them into Affinity Photo's Panorama tool. Stitching works fine, but I can't export the document as a DNG, so it can't be fully edited in Capture One. Since DNG is an open format I wonder if it is difficult to bake it into Affinity Photo?

Any update on this? The workaround is nice, but this option is a must for typographers, actually.

Hi @Gabe, sorry for the even longer delay in return. This happened in several documents, but I have to check back to see if it still happens after the latest updates.

Hi folks, is there any way to tell Affinity to NOT track a deselect, caused by a mouse click, as part of the protocol palette? Because for me, this is somewhat annoying. Coming from Adobe last year, I am used to go back in time, watch a previous state, maybe copy a certain element and then go forth to the latest state. Now with Affinity, as soon as I click somewhere on the canvas in the previous state (for example to get rid of a visually distracting selection), the protocol changes and I can’t go forth to my latest edit. Best, Johannes

Sorry, @Chris B, didn’t check in for a while. I give it another try with the latest update!

Hi @MEB, thanks again. I figured it out by myself in the moment you replied, but your profound answer, especially on live filters, relates to all questions that I might have come up soon. I also understand that some of the workflow differences come from the different "logic" between PS and Photo. Maybe there could be shortcuts that automatically generate those masks, like alt-clicking between to layers or something like that. Especially since Photo has an eye on astrophotographers who would further benefit from convenient masking. Keep up the good work!

@MEB Thank you so much! That was really helpful. I think I must have messed up something with the alpha channel, but now I was able to reproduce it. One more question, and I hope it is not too off-topic: How do I can insert grayscale images into a mask? Is that possible after all? Edit: Nevermind, I figured it out by myself. This was helpful.

Sorry for warming this up once again. But I am not sure what mistake I am making, though I am a very skilled Photoshop-User (15+ years). I investigated your demo file @MEB. But I just can’t make it happen that my curves layer nests (and applies) to the mask instead of the parent layer. When I drag and drop the adjustment layer onto to mask layer, so that the vertical bar appears, the layer snaps to the parent layer (thus every adjustments apply to that instead of to the mask). I can’t make it open a second child (nested) layer like in the demo file. Neither with a pixel layer nor with with a folder. I appreciate the non-destructive manner, but editing mask trough curves etc. is pretty basic editing stuff and this approach causes some strain, to be honest. Case study: I have a filled pixel layer (night sky with stars) on top of another one. All I want is the upper layer to only show the bright stars. In PS, I would duplicate the upper pixel layer, turn it into b&w and copy it into the original layer’s mask. Then I would invert the mask and tweak it further through curves, maybe finished with a slight gaussian blur. In PS, this was a matter of a minute. In Photo, I already spent an hour to figure out how to do the most basic step. I am puzzled. Edit: Okay, I finally managed to nest the layers properly, but only for a top level mask layer (not with a mask nested to a pixel layer). But since it is all non destructive, I still can’t paste a b&w layer into a mask layer. What am I doing wrong?