Jump to content
You must now use your email address to sign in [click for more info] ×

eworkflow

Members
  • Posts

    18
  • Joined

  • Last visited

Everything posted by eworkflow

  1. My client provides manuscripts containing all needed basic character formats but uses 2 consecutive paragraph characters whenever only one new paragraph character is needed to correctly convert the text to the Publisher's paragraph styles. Since the manuscript is on the cloud storage and its viewer provides no text editing capabilities, I want to avoid creating any format revisions there, and also want to avoid creating my local storage version of it. I try to use Find and Replace of the Publisher 2.2 but finding double pilcrow ¶¶ and replacing it with ¶ fails. Please advise.
  2. Thank you for this simple guide. My typographical limitation showed here but, at least, I rejected the visual result of a faux small cap. Sadly, that's not always the case...
  3. See "SELECTED POEMS" header rendering on this screen grab and notice letters "S" and "P" are rendered too thick for a proper small cap variant. Please advise.t.
  4. This critical error while saving to pCloud just happened in Photo 2.1.1 on my Mac M2. So I think that it was never solved and might be a side effect of how pCloud mis-communicates with Photo and probably other apps in the Affinity suite AND a poor exception handling by Affinity app (there is no reason why the Photo would not offer to save it to any other location than pCloud before it stops hard. Losing work is the last thing anybody wants to experience with any app.
  5. Thank you for the help. I was unaware that I need to select Page Box / BleedBox after I place a PDF that has bleeds. Certainly, choosing that option on a file place option panel (not existing) prior to placement would be more intuitive.
  6. I attached that exported PDF file in the post; The file itself includes screengrabs. What else do you want me to include? As I mentioned, that PDF file contains bleeds and seems to "lose" them after its placed in the Designer. I have no idea where "I specify Bleedbox for the "Page Box" setting in the Context Toolbar for the Placed file". I simply expected that Designer will place what I exported without a need of modifying any placement box options, which I can't even see prior to the placement, so it's not really intuitive.
  7. You can perform this simple test that fails. I create the initial doc in Designer with 51p x 66p dimensions with asymmetrical bleed of 0p and 0p9 and export it as PDF with Include bleeds option (selected twice on export panel - somebody please explain why it must be listed there twice). Then, I place the exported PDF back in the Designer. The exported/placed PDF does not contain any bleeds. To be more precise, I think exported PDF includes bleeds, but it is getting placed without bleeds. PDF-export-test-EXPORT.pdf
  8. This seems to have nothing to do with unit conversion accuracy and exists until now with v2.1.1. You can perform this simple test that fails. In my latest case, I create the initial doc in Designer with 51p x 66p dimensions with asymmetrical bleed of 0p and 0p9 and generate a PDF with bleeds from it. Then, I create an empty doc in Designer with the same dimensions & bleeds and open the previously exported PDF in it: the PDF does not fit quite by far. Advise, please.
  9. My AffPub2 on Win11 crashes happened when I "played" with Notes / Footnotes / Custom / Bottom of Frame parameters (to learn their effect, so it was pretty random) while I had cursor placed within the footnote, but I am not sure at this time what were the steps. I will try to follow it proactively.
  10. Thank you, Old Bruce, for your kind help. Please note that "my solution" (see above, using Frame Break insert while "Allow split notes" in on) works somewhat "cleaner" for me, although it requires a little manual cleanup of the overflow footnote's first line created that way. It's necessary to mention that using Frame Break insert without first "Allow split notes" on, hangs my AffPub2 on Win11. Thanks again.
  11. ...a follow-up note: the "Allow split note" must be also on for my solution to work correctly.
  12. I dug deeper and I think I found a good solution for my problem. My problem (purposefully detailed): split a 9-line Bottom of Frame footnote at the end of the 5th line. My solution: 1) Position cursor at the end of the 5th line; 2) Use top menu Text / Insert / Breaks / Frame Break.
  13. I find Footnote Custom Positioning somewhat inadequate. For example, the Chicago Manual of Style leaves to the writer to accurately control where a long footnote overflows to the next page. The idea is to never split a footnote at the end of a sentence, so readers get a clear indication a footnote continues on the next page. APub2's "Allow split notes" seems to be less rigorous. Why not use a more intuitive UI, such as maybe "Force split note", allowing the user to simply use a new paragraph character within the footnote text to force the exact position where the footnote text continue on the next page? Please advise.
  14. Well, crashing APub2 after manipulating footnote parameters is not limited to MacOS; It happens to me repetitiously on Win11, forcing the document's recovery.
  15. My Win10 (21H2) desktop returns "Setup failed" message shorty after attempting Designer, Photo, and Publisher installations. No previous version update problems were encountered in the past. Please advise. UPDATE: Those apps install with no problem after a fresh system reboot.
  16. In my case, all three Affinity's apps, basically, became unusable with 1.10.4: it takes several minutes (!) of "Loading fonts" now to start each app and it does not become faster on the subsequent starts nor I added any significant number of new fonts. There was no such problem with the previous releases. I would consider it a serious bug that, apparently, affects certain percentage of PCs.
×
×
  • 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.