-
Posts
6,532 -
Joined
Everything posted by loukash
-
Nothing that I'm aware of. I'm still relying on Acrobat 10 for preflight control etc., as long as it works on my MacOS partitions (need to check if it works on Catalina). Eventually I'll likely migrate to PDF Checkpoint. Finding the correct setting is somewhat counterintuitive, but at the end of the day – as noted in the aforelinked thread – this should work: Color Space: As document (= CMYK) Profile: Use document profile (!) Embed profile: off (unless you want PDF/X) Honor spot colors: on It doesn't matter which profile you're using. You just don't want to convert from one to another after exporting. Because that's how PDF/X is supposed to work. Haven't noticed this ^ before: why would you want to "review in Photo"? ~~~ That all said, I just noticed that there's a bug when copying a K100 text/path from another Publisher document that has a different CMYK profile: it converts to composite black. Possibly it's because Document Setup > Color > Color Profile cannot be changed from "Convert" to "Assign" for some reason unknown to me. Could be that you're using a different CMYK profile in Photo than in Publisher?
- 11 replies
-
- affinity publisher
- colour
-
(and 2 more)
Tagged with:
-
Transform panel and type
loukash replied to StevieB's topic in Feedback for the V1 Affinity Suite of Products
The latter. You can also use guides or grid with Snapping, and then using the resize handle with Shift key instead of the Transform panel. (As a side note: I definitely find the Designer Transform panel less awkward and more predictable than the corresponding panel in AI CS5… ) You have the scale handle with modifier keys, which is universal for every selection and highly versatile. Is there anything that it can't do what the AI scale tool can? (That's a serious question as I don't remember off the top of my head.) -
Convert texts with tab stops into tables
loukash replied to PaRunk's topic in Feedback for Affinity Publisher V1 on Desktop
It's a multi-step process but it's relatively quick and simple: create a blank table; even one single cell should suffice copy rich text with tab separators to clipboard; if you're copying from another text editor, it won't work with plain unformatted text because for some reason bug select a whole cell – or any random number of cells – in your blank table, but do not place cursor inside it or your text lands inside the cell as a whole paste Definitely. -
Ah, fair enough, my bad. Alright, I just figured out that Text>Spacing is contextual. (I haven't noticed many such details yet, because likely of all the Designer bugs I'm still ending up finishing so many tasks in Illfrustrator CS5. Oh well…) So: if you select a word, Text>Spacing affects Tracking if you place a cursor, Text>Spacing affects Kerning Now, having that all cleared, this concept still applies: Voilà.
-
You mean Text>Spacing>Tighten/Loosen a.k.a. Tracking? I, for one, consider this a feature, not necessarily an omission. If I need "surgical" tools, I go to Characters panel > Positioning and Transform > click inside the Tracking field and use Arrow Up/Down to change in 1‰ steps. But yeah, why not. Having options is usually a Good Thing™. I just don't think something like that will land anywhere near the top of Serif's to-do-list.
-
I think I've encountered something similar yesterday, but cannot replicate it. Sometimes also, the New… dialog window remains blank until I click one of the preset sections.
- 6 replies
-
- affinity publisher
- publisher mac
-
(and 2 more)
Tagged with:
-
As a side note, I had to create the GIF in Photoshop CS5.5. Affinity Photo can't do. GraphicConverter can somewhat do, but the resulting GIF looked, um… ugly. Oh well…
- 20 replies
-
- affinity designer
- bug
-
(and 3 more)
Tagged with:
-
Use the "<" share symbol in the top right corner of the post you want to link to.
- 20 replies
-
- affinity designer
- bug
-
(and 3 more)
Tagged with:
-
I think I've stumbled upon that post as well. You mean something like "you're holding it wrong"?
- 20 replies
-
- affinity designer
- bug
-
(and 3 more)
Tagged with:
-
Here a follow up, a "workaround" to achieve the goal in Designer, without having to resort to Illustrator CS5 (which likely won't work on anything higher that El Capitan). The trick is to: close all open divider paths somewhere outside the form you want to divide process only two paths at a time to avoid dozens or hundreds of random superfluous nodes on your clean paths you may want to duplicate the dividers for each segment you want to divide See animated GIF. It's not looped (I hate looped GIFs!) so if it doesn't play, click the image to play it in an overlay: Task finished in about 15 minutes. Hey, that's still somewhat faster than if I had to cut the form with a cutter from those old red transparent film layers and positioning them on cardboard like we did in the 1980s and early 1990s. Still have a few pieces of that film (forgot its name) and cardboards for final drawings – and rapidograph pens – somewhere in my studio shelf…
- 20 replies
-
- affinity designer
- bug
-
(and 3 more)
Tagged with:
-
I have already posted this a few days ago, buried in a partially related thread, but reposting here for "posterity". I was attempting to divide one simple closed path with a few crossed free form lines. I.e. essentially wanting to create a jigsaw puzzle. A divide path functionality that I may have been using with FreeHand already back in the mid-1990s. And now: can't do! (Well, "could do" by adding nodes one by one on crossings, breaking and rejoining paths one by one, as was proposed in an earlier post in the aforementioned thread.) Definitely not what I wanted to get. The divider paths were open for a reason and must not "auto-close". The resulting forms cannot be cleaned up to the desired effect. Not to speak of more complex forms and paths. After spending literally an hour trying to figure it out in Designer and looking for workarounds, eventually I copied my simple paths to Illustrator CS5 (which still somewhat works on MacOS El Capitan), clicked a button, copied the divided form back to Designer. Task done within a minute:
- 20 replies
-
- affinity designer
- bug
-
(and 3 more)
Tagged with:
-
Thanks for this hint, it has brought me on the right path, so to speak. I had troubles to export a simple K=100 vector logo as a plain PDF from Designer. Something that's been a no-brainer with Illfrustrator CS ever since. Apart from Embed Profiles = NO, having "Use document profile" selected is also crucial: While you cannot actually unselect it yourself, the menu will be empty if you have just switched e.g. from Color Space RGB to Color Space CMYK while editing a preset. The RGB color space applies to the "PDF digital" presets. So if you don't switch to a full CMYK preset in advance, switching the color space in an RGB preset to CMYK will blank the Profile menu. That will ultimately result in a 4-color black export, no matter what. And that's a bug, not a feature.
-
Out of curiosity, I attempted to import a relatively simple brochure IDML, after finishing the layout in InDesign CS5.5 just earlier today. Most of the content are small flat tables that were autofilled with text and autoformatted in InDesign by importing a well formatted XML file that matches the tag structure of the InDesign document and its tables. I'm producing this brochure with InDesign since 9 years, having done about 30 of them so far. It just works fine, in spite of the rather rudimentary XML tag support for tables in CS5.5. (Don't know about the recent InDesign versions, but working with tags within tables in CS5.5 is a p.i.t.a., and back in the day it took me quite some time and trial'n'error to figure out how InDesign XML import works with tables.) The bug: As long as there are XML tags attached to the text frames in the IDML file, all tables within those tagged text frames will remain empty, with no text whatsoever. It affects just tables, not regular text in those frames. Removing all XML tags in InDesign and re-exporting as IMDL fixes the issue, the tables are now filled with the original text. (Other issues with IDML import and tables notwithstanding at this time…) Publisher 1.8.6, Serif store version Adobe InDesign CS5.5 (German version) MacOS 10.11.6 El Capitan
-
Default dialog buttons blank in Light Mode on El Capitan
loukash replied to loukash's topic in V1 Bugs found on macOS
Thanks. Sadly, as long as I still need Illustrator CS5 to perform basic boolean jobs that Designer appears to be incapable of, I'm stuck with that "old" MacOS…- 2 replies
-
- buttons
- el capitan
-
(and 2 more)
Tagged with:
-
I'm currently pulling the rest of my hair upon this, attempting to divide one simple closed path with a few crossed free form lines. I.e. essentially wanting to create a jigsaw puzzle. A divide path functionality that I may have been using with FreeHand back in the mid-1990s! And now: can't do! Well, "can do" by adding nodes one by one on crossings, breaking and rejoining paths one by one, as proposed in a post above. Gimme a break! Eventually copied my simple paths to Illfrustrator CS5 (which still somewhat works on MacOS El Capitan), clicked a button, copied them back to Designer. Task done within a minute, after spending an hour trying to figure it out in Designer. My goodness.
-
XML import request
loukash replied to Samwise's topic in Feedback for Affinity Publisher V1 on Desktop
Same here, thus bumping this thread.- 17 replies
-
Sadly, same for InDesign vs. Publisher. My personal InDesign "killer feature" is XML import and connecting XML tags directly to character and paragraph formats. Heck, it's been there since at least vCS3: layouting complex brochures based on dozens of tables by importing XML files from an online server takes me just a few hours, including double-checking the XML files for possible errors and subsequent proof reading of the finished layout. Can't do that with Publisher yet. Or perhaps I could, but the client couldn't pay me.
-
Metadata not in Affinity Designer?
loukash replied to loswochos's topic in Feedback for Affinity Designer V1 on Desktop
Um, what? Pardon my sarcasm, but even if I save my *.ai without PDF preview and if I then open it with the puny Preview.app, I still get some "useful information" from it like Title, Author, Subject and Content Creator in the Preview.app's Info window. So there's no reason why Designer couldn't at least partially read and display the existing metadata, and then make it fully editable as XMP/IPTC in its own file format. Anyway. Workaround: Since I'm currently migrating my DAM from iView/Expression Media catalogs to NeoFinder, I figured out that I can at least use exported XMP files from my Adobe documents as sidecars to *.afdesign in NeoFinder which can then edit and update them. NeoFinder doesn't read all obscure XMP fields that there are either, but all standard fields are there.