Jump to content


  • Content count

  • Joined

  • Last visited

About elgarak

  • Rank

Recent Profile Visitors

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

  1. It has happened a few times to me that Publisher (version 174) crashes/becomes unresponsive upon saving. At first I thought it was related to saving/replacing an existing file, but it happened to me yesterday with a completely new file, too. I then force-quit, restart, and usually just continue. Yesterday Publisher refused to start after this force-quit. Weird things was that it displayed "Force Quit" in the Dock, appeared in the Force Quit Window (as responsive), but there was no process visible in the Activity Monitor. No click on any "Force Quit" would remove it. I tried to kill that by logging out, but the log-out failed, so it seemed, due to these weird remnants. I cold re-booted the Mac, after which everything returned to normal. That's on a late 2012 Mac mini running Mojave, in case it matters.
  2. Smooth update from 139 to 140 for me. Automatic re-launch to the exact same state as before. Nice.
  3. Not a big deal, but... I'm using Mojave's Dark Mode, and naturally Affinity Publisher defaults with a dark interface. In the data fields (say, for entering margins, font size etc.) the text cursor is black on a very dark background (the numbers/data is white). At first I thought the cursor is missing altogether... Nevertheless, it's annoying when entering data. ( and .139)
  4. And a further text: After a Clean start, the issue shows up, too. Reliably when the Move Tool is highlighted while the text box is selected.
  5. Further test: I selected the text box with the Move Tool. The Move Tool was highlighted (as well as the text box). That's when the issue shows up. If I highlight the Frame Text Tool before inserting text, everything works fine. Double-checking... Yup, that's it.
  6. It did show up again after I made a master with page numbers, the expected four pages I need to get the text with text boxes and a flow between them. The file is attached, again saved just after I made the "Insert Text from File". I had selected the first page/textbox. Its context menu did NOT show the "Insert Text from File" command (I select it from the Text menu). The context menu looked like it belonged to a drawing element. RTF wrong insert 2.afpub
  7. After a Clean start, it worked! Seeing the Clean version, I just remembered that the context menu (right/ctrl-click) of the text box looked different when I had the trouble. The "Insert from File" command was NOT in it. I'm trying to re-create the issue now...
  8. I have uploaded the files. Just to make sure: Affinity Publisher was running for some time. I just closed another file, made a new one, made a text box on the first and only page of the new file, and tried to insert the RTF. It showed up with its own text box and formatting/textwidth. That's when I saved the file. Yesterday I had trouble re-creating the issue myself. It showed up with about fifty/fifty chance (feeled, I didn't count ). I wasn't able to pinpoint which combination of actions caused it. I am going to try a Clean start now.
  9. Interesting.... Just tried it again. New Affinity file, one page, one text box. Works as expected, text fills the text box. Undo insert text. Insert second page, make text box on 2nd page, make flow from first page and box to second page and box. Select first box, insert same RTF file as before. Text appears with its own text box way up high. (I'm hesitant sending the RTF, as it is a text not written by me.)
  10. I do not know if this has been mentioned before (can't find it), if this is bug, or if I'm doing something wrong. I thought the usual workflow (which worked for me before version 133) is: Make text box. Select text box. Choose "Insert Text from File", which should fill the selected text box (and below if the text is too long for the box). The last few tests for me resulted in the text inserted to the right of the text box, with its own new text box somewhere way up top (outside the page). So I had to delete the text box I made, select the text box of the text, and move it how I wanted it, and re-adjust the text flow. Seems like a bug, as I can't pre-set a couple of pages with boxes and a flow between them, and then fill them with text.
  11. I love it when an app comes together. Good job!
  12. Kinda makes sense. As I found out, as far as pure text (no math) is concerned, one can workaround by using standard installed system fonts directly in the LaTeX source (if one made or has access to the LaTeX source, and is not working with a PDF of someone else). Math still does not import properly all the time, even if the recommended replacement math fonts (Latin Modern Math, for one) are used.
  13. Affinity Publisher (and Designer) do not import PDFs generated by LaTeX properly. So far, it seems to be not influenced by the LaTeX engine (pdfLatex or XeLaTeX, for instance). First obvious problem is that Publisher does not use the fonts that are embedded in the PDF. First workaround tried by me was to install LaTeX specific fonts into macOS, and choose them in the replacement dialog, but this does not completely work (math doesn't read at all convincingly. Text works better that way, but diacritics (German umlauts) don't set correctly (the dots are set off to the left)). After some digging into the forums, a better workaround is to change the LaTeX source to use the macOS installed replacement fonts, and open and re-save the PDF with Preview. This does produce an improved import, as far as text is concerned. Math still has some problems. The equations are by now recognizable, but there are still the occasional (completely) wrong glyph used, and some sizes are wrong (for normal Roman font used within math environments). I have attached a small test file with some common elements (mostly equations). This file is done with standard pdfLaTeX and the LaTeX-specific Computer Modern fonts. As far as I checked, all fonts are embedded within the PDF. The PDF opens properly on my Windows test system in browsers and PDF readers, and prints properly. I can produce other variations, if needed. equations.pdf
  14. I wasn't sure if it counts as a bug... , as Designer has the same problems (probably uses the same engine), and supposedly Adobe InDesign also has problems importing them. I just decided to submit since I found iCalamus, which, at first test, seems to properly import. I will go ahead and submit a bug report in the bug forum (Mac).