Jump to content
You must now use your email address to sign in [click for more info] ×

spamjim

Members
  • Posts

    16
  • Joined

  • Last visited

Posts posted by spamjim

  1. On 10/10/2018 at 4:58 AM, MEB said:

    Serif has opted for keeping it as DPI. There's no point in going through this discussion again. We appreciate the feedback and references/links posted but if there was plans to revert this the dev team would probably have done it by now.

    Using the proper term (PPI) would be a great feature of a 2.0 release.    😃   I'd upgrade just for that.

  2. Joachim_L, I'm not reporting a problem.  I'm saying that Publisher appears to handle this function better than InDesign.

    Michail, to restore a master page, you can still "apply master..." to any page where you have edited detached master page elements. However, in the way that Publisher is detaching master page elements, it does not seem like it would be too much trouble for developers to allow the ability to restore individual elements instead of resetting the entire master page design.

     

  3. In the InDesign method, there is something bad if you unlock everything: you no longer have the benefit of a master page. Future changes made to a master page will not apply to the standard page that has everything unlocked.

    However, we may be dealing with something much better than InDesign CS5.5 (my point of reference). The matter may have changed in the Publisher betas since this topic started (or maybe I did not realize it at the time). As I look at 1.7.0.283, the master page editing features go beyond ID's capabilities.  Publisher appears smart enough to understand what you have changed from the master page. If you turn a black box on the master page to red on a standard page, it retains that red, even if you move the box again on the master page...the red box on the standard page moves too. 

    The only fault I see with Publisher is that the "Edit Detached" command does not seem to be available in the Preferences for Hot Keys. But maybe that is a good thing as well. It shouldn't be too easy to hack up a master page template.

  4. It is doubtful this is something in line with the audience and market for Publisher.  As you've noted with specific outputs, much of the "interactivity" options you see in other applications serve a company's larger portfolio of publishing services or intellectual property. For example, you can make interactive PDFs in Adobe software because PDF is developed by Adobe.

    A first step to getting interactivity output options is to be able to tag content and export XML. That's what these other add-on developers work with to generate their "interactive" output.

  5. On 12/27/2018 at 12:40 PM, CraigB said:

    I've read all the apologists about a 'maybe later' IDML import...

    ...

    I'll look at it again when Serif announces IDML import functionality (with a comparable interchange export functionality). Hopefully CS6 won't stop working with a future Mac update or I'll be going back to Quark (who added IDML import late last year). If I incur the significant one-time cost to move to Quark I will have little reason to consider Affinity Publisher for a very, very long time.

    There's no need to carelessly classify another as an "apologist" to diminish their credibility and recognition of the reality. Nobody can expect to effectively import ID design data if you don't have the Affinity features ready yet to support features coming from ID.

    If you're old enough, look back to the advent of ID. It had a very crude PM and QXD importer. ID users most often had to recreate their legacy documents. ID has never had a QXD importer beyond version QuarkXPress 4 and the PM imports (from Adobe's own software) have always been garbage. Adobe had huge resources to develop importers with ID1 (and all subsequent releases) but still did not live up to our current expectations of Affinity.

    As you know, each page layout developer intentionally limits the interchange of their documents. We recognize this as "vendor lock in". Instead of blaming developers for not being able to read/import, we can blame ourselves for choosing a proprietary format.

  6. Publisher moved from spot inks and CMYK, as of the 2013 release. It is limited to RGB garbage. GIGO!  Even if a conversion to Affinity Publisher was offered, you'd need to correct all the linked/embedded assets and color. If you have legacy MS Publisher documents, it is best to maintain a pre-2013 installation or start from scratch with a program like Affinity Publisher.

     

  7. The description of this PSD export preset might be improved for the Windows audience that does not use Final Cut Pro X, but may use a similar program that cannot import all PSD features.

     

    I suspect this PSD preset flattens or simplifies some PSD "layer effects" for better compatibility in programs like Final Cut Pro X. 

     

    Maybe "PSD (preserve portability)" may be a better label for this preset.

     

     

    post-40817-0-63134600-1480698222_thumb.png

×
×
  • Create New...

Important Information

Terms of Use | 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.