Jump to content

Efvee

Members
  • Posts

    85
  • Joined

  • Last visited

Posts posted by Efvee

  1. I do understand how to apply local overrides and I use them in scenarios like this currently. I still think having the ability to apply multiple styles would open up a useful capability. The styles could override each other hierarchically much the way styles are applied in CSS. Of course, the advantage to using styles is being able to make changes later without having to go through all the paragraphs one by one.
     
     

  2. I sometimes find myself wanting to apply multiple styles to a paragraph. This would be useful if one wants to add a paragraph decoration to text that is already styled.

    Scenario, I have 4 consecutive paragraphs each with a separate paragraph style. If I want to use text decorations to offset just these four paragraphs I would have to create 4 additional styles. With style stacking, I could just add the text decoration style on top resulting in only having to create 1 additional style.

  3. Thank you all for the feedback. I really appreciate it.

    It seems to me the best way to ensure page to page consistency is with the baseline grid. I will see if I can talk my layout people into it.

    It would be nice to have Affinity Publisher calculate the drop cap based on actual line position, i.e. after calculating the line spacing but obviously that is a future hope and is no immediate solution.

     

  4. Hello everyone!

    I have searched the forum but I could not find anyone reporting the particular issue I am seeing. When I apply vertical justification to a text frame that also contains a drop cap the drop cap size no longer matches the second line of the paragraph. This results in an appearance that is undesirable for my layout staff. I am attaching a screen shot below. The left paragraph shows the correct sizing with vertical justification turned off, the second shows the problem with the leading and drop cap misalignment. Is there any way to solve this?

    Unfortunately, manual adjustment will not work in this case because vertical justification applies variable spacing.
     

    image.thumb.png.19c89c1ac66dc8af7037c25086b3d9f7.png

    Thank you! 

  5. 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!

  6. 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!

  7. 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):

     

     

     

  8. 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.

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