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. Affinity Publisher 2 is so slow with large documents that it often crashes and I am forced to force quit the program.

    Whenever I need to use Data Merge for more than 500 records I have to resort to Affinity Publisher 1 which is very fast.

    In the latest case I was running a Find and Replace command after Data Merging to produce a 1300 page document: Affinity Publisher 2 crashed—Affinity Publisher 1 finished the replacement in just a few seconds.

    I have similar stories for exporting PDFs and unlinking images etc.

    Affinity Publisher 1 was a treat to use with large documents and really impressive!

  2. Hello everyone!

    I am using APv2.0.4 to export a data merged file to PDF. With about 1000 pages the file takes more than an hour to export using the PDF(print) preset.

    The same data merge done in APv1 will export to PDF in less than a second.

    Something is clearly wrong here and it does not seem related to PDF settings. (I have tried numerous presets and settings including the ones that avoid colour conversion, etc.)

    The static portion of the data merge is a pass-through PDF on a master page.

    Thank you!

  3. Hello,

    I have found that using the backspace key to delete objects will cause a crash if the object has been selected by default.

    Case 1: Create an object (it will be selected by default) and press backspace; Designer will crash.

    Case 2: Create two objects, select the first one with the arrow tool and press backspace (object is deleted as expected) now press backspace again (the second object is selected by default after the first object is deleted); Designer will crash.

    Here is case 2 in a screen recording (note the key being pressed on the virtual keyboard):

     

     

     

  4. Thank you for the feedback! If Publisher is going to interpret the data files automatically it needs to be more robust. In my case, it seems that Publisher only reads a portion of the file before deciding on the encoding. So if you have a data source that is 5000 records and the last record is the only one that contains utf-8 specific data it will be wrongly interpreted (no other application I tried has this issue on Mac and Linux).

    A BOM should not be necessary to make this work.

  5. Hello everyone!

    I am doing a data merge and I have a CSV that contains characters with diacritics. For some reason, Publisher will not read the CSV as utf-8. I can open the CSV in TextEdit, Pages and even less in Terminal and the characters show properly. I can even copy and paste the text from TextEdit into Publisher and the diacritics are preserved. What can I do to get Publisher to display diacritics via Data Merge?

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