Jump to content


  • Content count

  • Joined

  • Last visited

  1. Thanks for the subscript / superscript clarifications, Walt and Sean. Still, the advanced typography features palette deserves to be looked at... And as always: a big thanks to Serif for providing us with such excellent products!
  2. A lot of advanced typography features seem to be broken in 1.7. It's not just stylistic sets and alternates but also subscript / superscript etc... I somehow thought this was so obvious someone already reported it but it somehow slipped through the cracks :-(
  3. Goner__

    Problems with accents

    I am having the same Issues as well. Czech keyboard. Attempts to type e.g. é result in ,é (acute accent interpreted as lower single quote). Just minor teething issues. Publisher is GREAT!
  4. Well, I never! Rabari, you nailed it! /Library/Dictionaries indeed seems to work. Thank you my friend!
  5. Ending spaces are truncated in auto-correct definitions. Entries such as "TEXT[SPACE]" -> "TEXT[NON-BREAKING SPACE]" become "TEXT" -> "TEXT[NON-BREAKING SPACE]" once you exit the line. Unsurprisingly, the results are less than satisfactory: TEXT[NON-BREAKING SPACE][SPACE] Just a nitpick, Publisher is great already and I am sure it will become much better judging from how Designer and Photo evolved!
  6. First and formost, congratulations to the whole Affinity team for an excellent launch and a big thank you for providing us with such an excellent software suite! One issue that's been bugging me for some time and has not been resolved as far as I know: Hunspell hyphenation dictionaries are ignored when placed in the system Spelling folder, i.e /Users/Profile_Name]/Library/Spelling They are picked up only if placed DIRECTLY into the app package, i.e. /Applications/Affinity Publisher.app/Contents/Resources/Dictionaries Am I doing something wrong? Cheers!
  7. Exactly. That said, there seem to be a few issues with this process which I already reported a few betas ago. When you specify a bullet character style at paragraph style level, some properties seem to be applied correctly (colour for instance), some, such at point size, seem to be wrong. For instance, when you want to use an 8pt bullet with a 11pt paragraph style, the bullet is 11pt large when the bulleted paragraph style is applied to an unstyled paragraph. You have to go to the Bullets and Numbering tab on the PAragraph pane, remove the character style in the Style field and apply it again (after which it is applied correctly). Interestingly, the bug seems to affect other paragraph properties such as leading. In my project, extra leading space is applied between character-styled bullet paragraphs and this can be fixed only by removing and re-applying the bullet character style.
  8. To make it even MORE interesting, further investigations show that everything is *completely* fine if you select "Prefer Linked" image placement policy and insert the PDF via Picture Frame Rectangle Tool... Did not have the time to test whether it was the Prefer Linked setting that fixed it or placing the PDF through the tool instead of drag-and-dropping it into the document. Now the document works like a charm...
  9. After embedding SOME (not all) PDFs into an afpub document (e.g. a simple flowchart, ca. 300 kb) and turning text wrap on, performance degrades significantly. For instance , there is a delay of several seconds when inputting new text and Publisher becomes extremely resource hungry, consuming 200+ %CPU. The situation is better for some PDFs, worse for others. My investigations show that OmniGraffle PDFs are extremely bad in this respect and one is attached to this ticket for testing purposes. Interestingly enough, the text lag / %CPU issue can be fixed by taking the objects out of the embedded PDF and moving them directly into the afpub. (there are other performace issues related to that, but the text lag seems to be gone) Thanks for looking into this matter Flowcharting Symbology.pdf
  10. I may be doing something wrong but after defining a custom character style (which changes for instance the bullet's font size, colour and baseline shift) and applying it via Paragraph Style --> Bullets and Numbering --> Style, SOME (though not all) properties are not applied consistently. Namely, everything is ok for paragraphs using the style at the time it is defined / updated. However, when applying the style to new paragraphs, SOME paragraph style properties seem to be applied to the bullet instead of the character style. (Colour, for instance, seems to be always correct, unlike font size, baseline shift, leading override etc.) How to recreate: create a "Bulleted" paragraph style with font size 12pt, Auto colour create a "Red Bullet" character style with font size 8pt, baseline shift -2pt and red colour apply the character style to bullets in the "Bulleted" paragraph style In this scenario: already existing "Bulleted" paragraphs will have correctly formatted bullets using the "Red Bullet" character style when applying the "Bulleted" paragraph style to an unformated paragraph, the bullet will be RED with a font size of 12pt (instead of 8pt as defined in "Red Bullet"), without baseline shift. Hopefully you can understand what I mean. Anyway, hats off for all the hard work you put into Publisher. It's shaping up to be a delight to work with!
  11. illusie, I just downloaded your .afpub, exported without touching anything and the PDF is OK, including the ligatures. My guess is the font file is to blame. What Georgia version do you have? I'm running v5.00x-4 (default system font).
  12. Mike, I couldn't agree more about the "cleverness" of installing fonts separately to restrict them to certain applications only. Microsoft has been doing this for some time with Office for Mac—for reasons which remain a mystery to me. If anyone wants to use the faces in other software (which is often not the brightest idea, considering that most Microsoft legacy fonts are intended for screen use and not suitable for serious DTP work) it's a simple matter of copying the font files from one folder to another...
  13. Exactly Mike. Legacy Microsoft/Windows fonts have been notoriously bad in this respect and font hadling in Office apps leaves a lot to be desired. That said, MS has been releasing improved versions of their fonts such as Georgia Pro, Verdana Pro, Arial Nova, Gill Sans Nova etc., which come with OTF features such as ligatures, proper small caps, etc. https://www.microsoft.com/en-us/store/top-free/apps/pc?category=personalization\fonts
  14. How to replicate: Place a rectangle as the page background, stretching across the whole master spread and covering both the even (left) and odd (right) page Assign master to left and right layout pages. All elements are applied correctly on the right page in this case, including the background layer "inherited" from the left master page. Save and close file. Re-open file. Observed issue: The background layer/rectangle covering both pages is transparent on the right page Colour palette still indicates the correct colour but it is not displayed correctly All other master spread elements placed on the right master page only are ok. The background layer remains white/transparent in exported PDFs. Re-applying the master spread solves the issue until next save / re-open. Am I the only one observing this issue? I'd expect this to be reported by others (since the process is pretty standard) but I did not find it in the bug reports and it has been there since the first bublic beta. Strangely enough, this does not seem to be 100 consistent. It happens on a regular basis in my test publication, but only once in the sample Affinity brochure (see pages 6&7 or the attached screenshot, page 7 should have dark background).
  15. Goner__

    Do not work on Mojave

    Not an issue in my case. Running beta .133 without this issue on Mojave. Can you try and provide more information to track down the bug?

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | 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.