Peter Werner

I'm using an external (Apple) keyboard that does not have an Fn key. Pressing the Fn key on the built-in laptop keyboard does not change the behaviour I described, neither in conjunction with the F-keys on the external USB keyboard, nor using the F-keys on the built-in laptop keyboard. Further investigation shows that furthermore, the shortcut input control in the text style editor dialog box doesn't accept F14 and F15 since these seem to automatically be tied to adjusting screen brightness on the laptop screen. Holding the Fn keys has no effect on this behaviour. I think if all of this was a case of system shortcuts taking precedence, they would just carry out their system function when pressed instead of nothing happening, as they do in case of F14 and F15. By the way, I've come across another oddity: Assigning F16 shows a warning that the shortcut is already mapped to "Zoom Out". Turns out this shortcut actually works for zooming out the document, but in the keyboard shortcuts editor in preferences, only Cmd+- is listed for Zoom Out. Maybe this has to do with the shortcut editor only allowing being able to handle one (probably the first) shortcut per command.

Just did a quick test, and It would seem you are correct. You may want to post this in the Affinity Photo bug reports section.

Your comment makes me suspect I'm actually dealing with a bug. I thought I had mixed something up, but checking an older proof PDF I sent out to the client, actually I think the numbering re-started with each story at first and then something caused it to suddenly continue across stories without me linking the text frames. Removing the "Restart Numbering Now" attribute from the first paragraph of the second story causes numbering to continue from the previous story. The text styles were all created from scratch. Maybe it's just a really obvious setting I am missing. I'm afraid I can't share the document in question publicly since it was created for a client, but I would be able to send a copy to the development team if necessary. Still, even if it's a bug, it would actually be really useful to have both options.

The "Restart Numbering" setting currently allows resetting the counter per-document, per paragraph sequence, or manually only. Sometimes it would be useful to have a numbering sequence specific to a text frame or sequence of linked text frames, i.e. per story. This small handy setting would eliminate the need to manually reset numbering at the start of each story and therefore also one source of potential errors since it's quite easy to forget.

I think it is worth mentioning that now with that Publisher has shipped with Studio Link enabled, you can just go to the Photo persona and use the Channels panel to check your separations. For some reason, page/spread borders disappear, but it's still a viable workaround. You need Affinity Photo installed in order for this to work.

Works fine for me, I only had "Allow JPEG Compression" deactivated on the PDF/X-3 preset, otherwise my settings should be identical to yours. The screenshot shows the PDF re-imported into Affinity and as you can see it consists of a raster image with a clipping path. I made the file by simply creating the S as an ArtText object and dragged the placed image inside in the layers panel. If you are seeing different results, I'd say it is definitely a bug and not a design limitation of the Affinity backend or the PDF library.

Not 100% sure about early versions of InDesign, but I at least don't remember running into any issues in that respect. But you may well be correct since around InDesign 1.5 and shortly thereafter 2.0.X when I started using the software, printers here always still asked for native files and not PDF so back then it wouldn't have been something I would have to worry about. That being said, if I create a shape in any of the Affinity apps, import an image and drag it inside to clip it, it exports to PDF as an image clipped inside a path (tested with the PDF/X-3 setting). The edges are sharp and not pixelated no matter how much I zoom in (tested in Apple Preview and by placing the PDF into an InDesign document, can't try Acrobat Pro right now because the updater corrupted my installation once again). Re-Importing the PDF into Affinity retains that path as a clipping mask for the raster image. Ergo the Affinity backend as well as the PDF library it is using (apparently PDFlib + PDI) are perfectly capable of outputting bitmaps with clipping paths, they are just not doing so in the case of the effects in the original poster's case for whatever reason. One possible explanation is that the partially transparent raster image on the left that is overlapping the lines somehow triggers rasterization of the objects below if any effects are applied, which to me looks like a bug.

I cannot possibly imagine that the Serif team would choose a PDF library that cannot clip a pre-rendered raster image into a path, that's pretty much as basic as it gets.

My apologies, I must have used different wording when searching for existing threads. Thanks for the replies!

I have a document with a few two-column text frames. On the left pages of two double spreads, the column resizing double arrow mouse cursor appears in the wrong spot, either two the left or to the right of the column gutter. On the right pages of the spreads, the hotspot is centered on the right column gutter guide (rather than the center of the gutter as one would expect). The feature can still be used since the offset remains constant if the user clicks and drags. One just has to find the right spot inside the text where the phantom handle appears. In that area, clicking to place the text caret is not possible since the column resize behaviour "steals" the mouse events. I have not tested if this is related to that particular document or not, but just in case, I have made a copy of the file where I encountered the bug that I can provide staff with if the issue cannot be reproduced otherwise.

These effects should still export as raster images clipped inside of the corresponding paths and not raster images only, so there is clearly something wrong here beyond just the resolution of the effects. Whether this is by design or a bug I cannot say.

I can assign F1 through F16 for paragraph styles, but pressing the corresponding key with a text cursor in a text frame has no effect. Assigning other shortcuts, say, Ctrl+Y, works as expected. Tested with German keyboard layout on English language setting of Publisher, USB keyboard connected to MacBook. OS is 10.11.6 (El Capitan). Curiously, pressing any F-keys hides the transform controls and frame/column outlines temporarily until the mouse pointer is moved. If this has to do with certain F-keys being taken over by OS shortcuts like launching Dashboard etc., I would expect Publisher to check for that and display a corresponding warning when assigning the shortcut.

Affinity currently lacks a lot of options required for full professional CJK typesetting, including things like Furigana and Warichu, dedicated composition/line break options etc., it's not just vertical text. My understanding is that they are going to get the basic features for roman typesetting done first to make Publisher and the rest of the Affinity range as usable as possible as a layout software for the roman languages and only then add features for full CJK and RTL language support a later point in time, which is completely understandable. At least IME for CJK languages seems to work fine now in Affinity 1.7 after being completely broken in earlier releases. That's already a good indication that this topic isn't ignored by the development team. I hope that one day we will have full CJK and RTL script support in Publisher. The last thing we could hope for is a messy and fragmented situation like with InDesign where you have to install multiple versions of InDesign in parallel, all of them developed by third party companies where you can only hope they don't mess each other's files up.

Running a web server for an API (or a web browser or Flash Player for dialog boxes) is exactly the same type of bloat that we all criticize Adobe for. They, too, are running at least one local node.js web server in the background even if none of their applications are active. You may have noticed it because it occasionally hangs, crashes or blocks system shutdown. Scripting isn't that performant in the first place, and running single command through a full-blown set of script interpreter, API in that scripting language wrapping and parsing the HTTP communication, HTTP server, system TCP/IP stack and what not is such a colossal waste of resources, not to mention it opens up the entire system to security vulnerabilities. If you really have a compelling case why you absolutely must automate Affinity applications over an HTTP API, you could easily implement the relevant parts of such an API yourself, either via a native C++ plugin, or even easier, with a Python script and Flask (a combination which by the way could probably replace InDesign Server with a desktop version of Publisher for quite a few use cases). This is by no means about what is trending, but what makes the moste sense in terms of providing an efficient, robust, powerful, extensible and future-proof scripting workflow. Besides, Python has been a staple of application scripting in the VFX industry (among others) for decades, and for a reason. This is by no means just a "trend" and there is no indication whatsoever that it will go away any time soon. As an established solution, there are a lot of companies invested in it so continued development is pretty much guaranteed for the foreseeable future. Lua is indeed great for smaller quick and easy scripts and easy to integrate in a C++ program, but not that suitable for more complex solutions (hello, Adobe Lightroom Classic mess) and its object-oriented language features are lacking compared to Python. C is not even a scripting language and does not scale too well, which is why it has been replaced by C++ as the language of choice for larger native software projects decades ago. It is also not true that the complexity of implementing one solution in different languages is always the same – it is true for very, very simple code, but as solutions become more complex, some languages, and their ecosystems, are significantly more powerful than others. As someone who has worked with both Python and VBScript I can tell you that there are some things that would be a nightmare to write in VBScript and a five minute exercise in Python. We don't need a hundred haphazardly integrated scripting solutions so everyone can avoid spending 30 minutes to learn a few basic new syntax rules, but one great scripting solution that is well thought-out, seamlessly integrated, simple and easy for basic tasks but powerful enough for the most complex requirements that arise, and interfaces well with the outside world (AppleScript/COM, network/HTTP APIs, third party libraries and applications, native code etc.).

I just came across a workflow stumbling block while working on letterheads with Publisher and delivering them as MS Word templates. There were multiple variations of the letterheads for different departments, which were created as different pages in Publisher in a single document based on common Master Pages My workflow was as following: Design everything in Publisher Create slices of header and footer for export to PDF Iterate on the design in Publisher until approved by client Place PDF graphics of header and footer in Word, recreate text that needs to be editable and text styles in Word, make color Palettes via PowerPoint (due to Microsoft logic) Last minute fixes: Make changes in Publisher, re-export the slices and replace the images in Word Deliver MS Word templates and color palette files To my knowledge, this is a pretty standard workflow for doing branding projects where MS Office templates are required. Since Publisher has no Export persona, I created my slices for my letter header and footer by opening the Publisher document inside Photo. Trouble is, Designer and Photo only support one page. When opening a document, they always just display Page 1. This can be circumvented by opening the file via the File menu in Publisher. In that case they will open the page that is currently active in Publisher. For me that meant that I had to go my target page in Publisher, use the menu to open that page in Photo, create my slices, save, close, re-open in Publisher, go to the next page, create my slices and so on. This is not only very cumbersome, but it also makes it really difficult to copy slices, settings or dimensions to keep them consistent across pages. Imagine that I find that I want my footer slice to be a bit larger after all because one version has some extra elements and I want them to be a consistent size – I'd have to close, re-open the document in Photo via Publisher for every single page and make my edits while remembering the dimensions to type in. The same applies to exporting the slices after a design change – when not using continuous export (haven't tested if that works from Publisher), this workflow also requires closing and re-opening the file for each page I want to re-export slices from. Imagine a change on a master page with slices on a 15 page document. That's a waste of time and unnecessarily frustrating. I guess the limit on page navigation was imposed onto Designer and Photo to prevent people from just downloading blank files with multiple pages and using those instead of buying Designer or Photo. My proposed solution would be to offer page navigation in the Export persona in both Designer and Photo. Then just always return to the default page 1 when going back to the main Photo or Vector persona if Publisher is not installed. Another possibility would be to take it further and globally enable page navigation in Photo and Designer if Publisher is installed, similar to the Vector and Photo personas in Publisher. The last option would be to add the Export persona to Publisher, but I'd say that's probably overkill.