Jump to content

Aliforce

Members
  • Posts

    8
  • Joined

  • Last visited

  1. Thanks for your quick reply - well you know what, I think you've got something there, how odd. I had to fiddle with my Adobe subscription today because of a dull billing issue at work which I won't bore you with, and this has also coincided with this. I had to install my Adobe fonts again. It's Adobe Caslon Pro which is OTF when I check it in Affinity, and the error looks the same in the Publisher document so it's not simply to do with the conversion to PDF. Looking through this document again, the major change is only with one type style which is a paragraph style for Chapter headings with a large illustration above. The space after the text has been shortened. The main body text spacing is fine because it's snapping to the baseline grid. I take on board your side note: looking at the text styles the leading is set to default so I could set to a fixed height to prevent in future. To be honest I panicked so much with this document I haven't dared open too many others to investigate further as It's my husband's birthday and I don't think I'd be to popular if I fell down an IT rabbit hole tonight!!
  2. Hi there, I've just updated Publisher and am on V2.5.6. Mac OS Sonoma 14.7. When I open documents with text styles set up, the line spacing has gone haywire. I'm including a PDF of the first few pages of a document before and after upgrade. This is seriously causing me problems as these are novels, not short documents. What is the best option, dial back to the earlier version again? Document after upgrade.pdf Document before upgrade.pdf
  3. Thank you, thank you, thank you. You have saved me so much time on a Sunday night!!!
  4. Thanks so much for this! It has been driving me mad today in a 500 page book I'm formatting. I checked everywhere except the Text Styles I'd set up. BINGO! Give yourself a gold star.
  5. THANK YOU, THANK YOU, THANK YOU! I was having multiple crashes and was going round in circles with this. You solved it! Give yourself a gold star!
  6. Thanks so much for your quick reply! So basically it will vary brush to brush ie: no one definitive answer. That actually makes sense as I noticed that the default stroke weight for the particular brushes I mentioned is huge - like 89pt for some. You can see in this example when I’ve applied one of the brushes to an 11 pt stroke created with the pen tool. I’ll see what the brush makers Retro Supply come back with and will share it here.
  7. I should also perhaps add, I'm taking these illustrations into an Affinity Publisher document.
  8. Hi there - I'm looking for some advice on best practice document scale when using textured vector brushes or raster brushes in Affinity Designer. I've just started to use some new brushes which were recommended in Spotlight here on Affinity. https://affinityspotlight.com/article/grave-etcher-vector-engraving-brushes-by-retrosupply-co/ They are great brushes but I'm a bit stumped as to how much I should scale up to preserve crispness in the final illustration as when I zoom in, the vector brushes are not true vectors, they behave like vectors (editable) but rely on raster images for the effects. This is explained in the suppliers own FAQs here https://support.retrosupply.co/article/81-why-are-my-affinity-designer-vector-texture-brushes-pixelated-when-i-zoom-in but they give no advice on how to avoid pixilation. I've emailed them, but thought this was actually a wider issue that some of you would have come across with raster brushes etc. So for example, if my end illustration will be printed at 5" x 5" . would setting up my original document at 15" x 15" at 300dpi be sufficient to avoid pixilation or should I just experiment. Is there an idiot proof formula? I don't want to go down a rabbit hole and find out I'm back to square one at the end of the process. Thanks in advance.
×
×
  • 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.