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

Efvee

Members
  • Posts

    81
  • Joined

  • Last visited

Posts posted by Efvee

  1. Thank you for the feedback!

    I was able to narrow it down to vector text in a placed PDF being rasterised.

    It does not rasterise if the text is "editable" or interpreted from PDF. (But that does mean some funny changes in appearance!)

    Native text is also not rasterised.

    So the problem needs to be redefined as "Booklet Printing Rasterising Text in Placed Passthrough PDFs".  

  2. Hello everyone!

    I have discovered that APub rasterises text when using the Booklet output option in the print dialogue box. I am used to using Booklet > Save as PDF for my workflow but I need the text to remain vector based. (I am printing to a production printer that [Konica Minolta C3080] that does much better when rasterising text on its own.)

    For my last job I imposed the pages manually to avoid this issue. Is there a way to do booklet imposition without rasterising text?

    Thank you!

  3. Hello everyone!

    I am seeing a very slow response when trying to select a colour when editing text. I don't know if this issue is new with 1.10.4 but I certainly do not remember seeing it before. I was demonstrating AP to a friend and I could not select the text colour during the session. (I thought it was not responding at all and multiple clicks only made it flash on the screen!)

    I am using a 2016 MacBook Pro (Core i7) 16G RAM, AP 1.10.4 (from App store), MacOS Monterey.

    Thank you for your attention!

     

  4. Hello everyone,

    I would like to suggest that Publisher's Data Merge feature be enhanced with the ability to remove blank entries. However, simply removing the blank line for a text merge can leave some messy things behind. I have an idea that we could use a special markup to tell Publisher what to remove with a blank field. That is, we define "field units" with double braces {{ }}. That way the whole "field unit" can be removed if a field is empty.

    Case 1: "<field1> <field2>" 

    Simple blank removal results for empty field1 (note the space before field2) : " <field2>" 

    Proposed "smart" solution using special notation: "{{<field1> }}<field2>"

    Results: "<field2>"

    Case 2: 

    {{<field1> }}<field2>{{
    <field3>}}
    <field5>
    {{<field4> or if you prefer: }}<field5>

    Here we have the option to choose to remove some text adjacent to a field (field4) and remove a line break before a field (field3) and preserve the line break (field5).

    A simple "Remove blank lines" checkbox would not take into account cases where you might like a line break preserved when a field is missing.

    I hope this makes sense! :) 

  5. 6 hours ago, Dan C said:

    I found it slightly more consistent when double clicking the preset thumbnail - could you please try this for me and let me know if it applies?

    Double-clicking does not change the behaviour for me. If I quit Photo and launch it afresh, the preset will apply the first time I click it but subsequent attempts will have no effect.

    Thank you for the feedback!

×
×
  • 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.