Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Besides the time to investigate and report the bug, it took me a good deal of time of actual work to clean up the article when I was copying from Publisher to post as our online version. However, I have since discovered a faster way than manually editing all the errors, and it may be relevant information. For Publisher 2 documents, I have found that I can copy a story and paste it into Publisher 1 in a simple frame, then copy again to paste into the external program. In this way, I still have rich text but without the issues. It’s definitely not ideal, but it will help get me through this until the bug is fixed. Thanks @MikeTO for letting me know about the similar post on Windows, and to @Pyanepsion for your work documenting the issue there too.
  2. I have discovered that copying certain strings of characters from Publisher 2 and pasting into various rich text editors results in extra spaces added where there was none before. To demonstrate: Open the attached file in Publisher 2. Copy the French word L’État. Paste it into an external program that accepts rich text, such as Apple Pages, Microsoft Word, or even TextEdit in rich text mode. Below are the results I get, in this case pasted directly into this post. First line is copied from the document when opened in Publisher 1.10.6, which works as expected, and second is from Publisher 2.0.3. L’État (Publisher 1.10.6) L’É tat (Publisher 2.0.3) Notice the extra space after the accented E. I have noticed this pattern in numerous words that have an apostrophe (but not a straight apostrophe) followed by an accented character. I also gave a second example it the file which you can try: jusqu’à la fin (Publisher 1.10.6) jusqu’à la fin (Publisher 2.0.3) In this case one space became two, but I notice it is still the same pattern of a space being added following an apostrophe together with an accented character. Tested on iMac (Retina 5K, 27-inch, 2019) on macOS Ventura 13.1. L'État test.afpub
  3. I am an Antidote user too, and I will be glad to see the day when integration is possible. What is needed is not that Serif specifically integrate this one tool, but rather that they provide an architecture for third parties to build their own integrations. That is surely how Antidote is able to integrate with a number of text-related applications, such as Publisher’s biggest competitor.
  4. Here’s a weird one and hard to explain. Below I have a video demonstration if you prefer. Here is a text explanation: Normally, when copying a paragraph that has automatic numbering (i.e., a “Bullets and Numberings” setting), when the text is pasted into an external program (ex: TextEdit), the number gets prepended as part of the text. But when: The text is in a multicolumn text frame, With “Balance text in columns” turned on, You copy from any column but the last in the frame When you paste into another program, … the number that gets pasted is wrong. It seems to always be the next number (or letter) after the last item in the list. Recipe: Open the attached sample document. Copy the “Line 3” paragraph in Column 1. Paste into TextEdit. What gets pasted is “16. Line 3" Columns 3, 6, and 9 (that is, the last column in each frame) work as expected, but every other numbered item will be numbered as 16 in this document. If you turn off “Balance text in columns,” copying and pasting from all columns works as expected. Numbered List Copy Problem.mp4 I have tested in Publisher 1.10.6, 2.0 and beta, all with the same results. I have macOS Ventura 13.0.1 on a 2019 5K iMac. Numbered List Copy Problem.afpub
  5. Thanks for that. I tested that myself before I posted, and it did not work. It would seem I got tripped up by the “Match case” issue myself.
  6. Thanks. I couldn’t find that report when I searched (I even tried visually scanning all post titles in the Publisher 2 Mac bugs, while it is still just a few pages). I tried to search again based on the terminology you used. I clearly overlooked this one, of which my post is but a duplicate:
  7. Edit: The problem was already reported here previously. --------- Here you see part of the Edit Text Style window (for a Paragraph style). Notice that two of the section titles are cut off: This is with the UI Font set to Large, whereas Default does not have this problem. I suggest some better way to handle longer text, which surely effects not only UI Font size but other languages. For a start, it looks like there would actually be plenty of space for the missing words in English at this font size. By the way, there is a little niggle along the same lines that is not worth making a separate report over, but it just “bugs” me. Why the inconsistency here: Color & Decorations Position & Transform Bullets and Numbering
  8. In case you are looking for a workaround (and I recognize that maybe you are not), you can use [:upper:] and [:lower:] inside of character class brackets, and that will work with Publisher’s regex. One word of caution: if “Match case” is not checked, then both both expressions will match both upper and lower.
  9. I don’t think so. I regularly see it in various places in the dark UI style as well.
  10. A laver is “a basin used to wash the body, especially for ritual purification.” An undocumented feature?
  11. Maybe Serif can work out something, but in the meantime I recommend you don’t work on files on a network drive (pCloud or otherwise). I also use pCloud, and almost all of my Affinity documents are on pCloud, but rather than work on them from the pCloud Drive, I have those folders set up as synced folders by pCloud. There are no issues with this arrangement, since the files are local copies not affected by the whims of an Internet connection.
  12. On Mac, usually programs won’t launch at all if they fall short of the required OS version, and I think that is the case with Affinity. So I think that is likely not the issue here. I would ask @suntrop whether this happens in a new document made from a default preset. There may well be some condition in an existing document that is exposing a bug.
  13. I’m sure it will. I have it running on a 2016 iPad Pro. Here is the official compatibility list from Serif’s site.
  14. Stepaan’s stated intention was to thank Serif, not help them. Posting it in a forum seems appropriate. He may also wish to help in various ways, but that is not the point here.
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.