Jump to content


  • Content Count

  • Joined

  • Last visited

1 Follower

About Lagarto

  • Rank
    Dedicated User

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. For me, personally, the most valuable (new, still just in beta, to be soon appearing in the release version 1.9) features are capability to select objects by their type, or by an attribute used in a selected object. It does not appear that these features will be in Publisher 1.9 (but they are accessible within Publisher, as will be the features mentioned above, when using the Designer Persona of Publisher).
  2. Based on the fact that this behavior still exists in the current release candidate 2 ( it seems that the 1.9 release version will only have very limited support for passthrough PDFs whenever there are PDF/X based methods involved either in the placed files (whether embedded or linked), or when trying to use PDF/X-basd methods at export time. According to my experiments (not very thorough), when using PDF/X based export method, all PDFs without proper output intent will be rasterized, but in addition to that all color values, even for non-rasterized elements will be translated according to the target profile, even when output intent is given and there is no profile conflict. That means that K-only blacks will always become four-color-black, whenwhether rasterized or not, when the export PDF is based on a PDF/X standard. They seem to remain as they are (= genuinely passed through) only when producing non-PDF/X based PDFs from non-PDF/X based source PDFs. The current preflight-warnings also seem to be all over the place and inaccurate, as when I tested this file, there are no forced rasterization problems placing PDF/X-based PDFs in the document (fonts were retained as fonts) even when producing with PDF/X-based methods (that's because the PDF files that initially contained fonts, the long text and yellow logo, both had an output intent). When producing a non PDF/X based export using "PDF (for press)" preset (using otherwise the default settings but just not embedding the target profile), MOST things seem to work as expected test_passthrough_pressready_non_embedded.pdf What I see in the attached "PDF (press only)" export, related to behavior of black ink, is that the long text in the background is K100 but knocks out (e.g., at the red "MUNCHEN" text) while it is marked to be overprinted in the original (and does overprint if exported from InDesign). The black parts in other PDFs seem to work as in the source PDFs so the black text in the blue star is K100 and overprints while the monkey is four-color-black, the black text in the yellow logo has its blacks in K100 and overprinted so that the text, and inner half of the black outline, have M10 Y100 showing through from the background, while the outer edge of the outline is K100 (the outline being center aligned so the effect of the background is affecting only the inner half). [UPDATE: As a comparison, when the same file -- with all PDFs marked to be passed through -- is exported using PDF/X-4 export method (unchanged), the black in the blue star will be translated to four-color black because the file does not have color intent -- even if it is DeviceCMYK -- and the long text remains as knocking out; otherwise the file seems to behave as expected and export similarly as when exported from InDesign.] IMO, PDF passthrough is not ready for showtime in Affinity Publisher. As have been shown in other posts, export time color conversions will not be supported, either (they are in PDF/X-based exports, but then everything without color intent becomes rasterized, and all color values are also translated, whether there is need for that or not). If the feature works in the release version similarly as it does now in the beta, there will be lots of confused posts and need for technical support. EDIT: I just repeated the same tests on macOS RC2 and the results were identical there.
  3. I just used the same case that appeared initially in your post, as I am not aware of details e.g. in context of specific Xerox printers, but it is good that you pointed this out. I suppose there are also printshop specific naming practices so it is always good idea to check this out before wasting time and material for erroneously separating prints.
  4. You can rename spot color swatches as you wish (using the same context menu as above for applying overprint), so if you use names like clear, white, gold and silver you should be able to separate objects assigned with these colors and have them printed with equivalent printer inks.
  5. The default mode for any spot color swatch is to knockout, so if you need overprint, you need to specifically force it (note the circle mark on the top right of the swatch): < overprint_knockout_02jpg
  6. I think it will be, once version 1.9 is released as you cannot select objects by attributes in the current versions. As for checking that the job is done, the same feature (select by attribute) could be used to see that there are no objects left unconverted (another method would be use e.g. Adobe Acrobat Pro Output preview and check distribution of spot colors within an exported PDF -- there is no similar feature in Affinity apps).
  7. One way to use Affinity apps on a Mac would be purchasing Windows licenses and installing the apps on Windows 10 Pro (ability to host a remote session requires the Pro version), and then use the free Microsoft Remote Desktop App on macOS to access the apps on the Windows computer. The production files can easily be transferred across the platforms via Clipboard, and switching between the operating systems can be done with a keyboard shortcut.
  8. Keeping the composition as curves is probably not important as this is a Photo project, but creating a Boolean compound by first adding the curves created from the text and subtracting it from the background rectangle allows adjusting the overlapping parts (if that is important): target.afphoto UPDATE: Here's another one where text is kept as text, while still working with vector masks rather than blend modes: target_text.afphoto
  9. You could also consider renaming the conflicting fonts using some font utility so that you can install alternative Frutiger and Garamond versions on your computer and use the proper fonts even if using different names (this of course could cause problems if you need to share your files, and least requires constant remapping of fonts on both ends, but would at least allow printing the jobe with the correct fonts).
  10. Use FontBook to check that you have actually the font installed on system level (and not just activated by the font manager). This font gives a warning related to ambiguous fontnames (identical family and full names): It can nevertheless be installed after the check, and when it appears as an installed user font on system level, should also show without problems in Affinitty apps: ...so the difference between your and your friend's installation might be that your friend has the font installed on system level, while you do not have, and Affinity apps might fail to enumerate fonts that have only been activated by the font manager (especially if that is not fully compliant with the OS). I tested this on Big Sur 11.1 (running Publisher in native mode). EDIT: The font I used was the same 1999 Macromedia FontoGrapher created TrueType (legacy) font that you seemed to have so the font technology itself is still fully supported.
  11. Thanks for the update. Are these fonts Type 1 (old PostScript format)? I have no clear picture of the way commenting is made possible (using free tools like Adobe Acrobat Reader DC, and other PDF tools), but I typically use the following Save As feature from within Adobe Acrobat Pro to make sure that the document can be commented from as varied PDF environments as possible: As I previously tried the commenting feature, the initial PDF was created in Affinity Publisher, which probably cannot apply this kind of "Reader Extension", but it also used just Arial so very basic features. Perhaps problems with adding comments are related to complexity of the document to be commented so that e.g. embedded fonts not installed on the clients' computer will cause problems if the PDF is not specifically extended for comments? UPDATE: Reader extension, even if specifically mentioning commenting as feature to be enabled, does not seem to be necessary when using up-to-date PDF tools, but it might be useful when it is likely that the clients have legacy PDF apps (like old Adobe Acrobat Readers) installed. E.g., not having a font used by the PDF installed does not prevent commenting, nor does it prevent the user from saving the PDF with comments on their own system, when using a recent version of Acrobat Reader DC (a free version), but this would not probably be possible on older systems with legacy PDF reading apps. For those kinds of environments, ability to save as "reader extended" PDF might be useful, and allow features not normally available in free version(s) of the app(s) .
  12. Perhaps this is then related to OS version (or Intel/M1), I've tested this on Big Sur 11.1 and M1 and there the setting does not have effect (which is good, because no matter what the setting is, I get properly behaving smart objects in Photoshop 2021 on this mac). I also ensured with the Clipboard viewer on both operating systems that I do not have confused settings, so when I turn on SVG option, the Clipboard has additional SVG data (in addition to PDF data), and when turned off, there is no such data. EDIT: To be more specific, I run Designer in native mode and PS is of course running in Rosetta 2 -- so perhaps there is "miscommunication" that prevents this problem to occur in this environment. But on Windows, turning on SVG definitely causes problems with Photoshop CS6 (will test this later with PS 2021...)
  13. Still more odd! I just tested this on macOS with PS 2021 and there turning on or off this setting does not have any effect (meaning that I get well behaving smart objects disregarding the state of this setting). Which platform and which version of Photoshop are you using?
  14. @SidianMSJones and @haakoo -- did you mean that this setting must be turned off to have the desired behavior, as now that I turned the setting on (tested this on Windows), I can experience similar rasterization, and also behavior described by @Jowday -- meaning that if the Clipboard has both PDF and SVG data, this confuses Photoshop. I thought (misunderstood) that @haakoo's post described a solution rather than problem
  15. This is odd, as I checked this on two systems where this setting was turned off but smart objects worked fine (meaning that Photoshop received vector data from Designer also when this setting is off). Perhaps this option has effect on more complex drawings -- I'll check this with Clipboard viewer to see what exacrly gets on the Clipboard and is exchanged when the option is turned off...
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.