mrichardson

You fixed it with version 2.1! Thank You! Thank You! Thank You! I can finally exhale.

Well, I guess I've moved from one walled off garden to another walled off garden. At least Affinity has the common decency to license the software for perpetuity after you purchase it thus guaranteeing you'll always have access to your work. I know those entrepreneurs that must interface on projects with others using Adobe products (thus requiring file compatibility) will find little solace in the previous statement. Also the ability to programmatically create documents outside of Affinity's user interface is gone. Fortunately for me, the reasonable price they charge for their software eliminates these compatibility problems as reasons not to purchase the software. Affinity's guys and gals gotta eat and I don't begrudge them the choices they've made all things considered.

Is the .afpub format proprietary to serif? In other words, if I took it upon myself to reverse engineer the .indd format, would I be able to convert it to a format that was directly readable by Affinity publisher? I'm just wondering if the affinity formats are open source or a closely guarded secret. I have a hunch those adobe files look an awful lot like a .pdf file. I know for a fact that if you have an .AI file and you want to view it on a computer without Adobe Illustrator, but you do have a pdf viewer, then all you need to do is rename it. i.e. FileIWantToSee.ai gets renamed to FileIWantToSee.pdf. Voila, it will (probably) work. Reverse engineering the .indd file format might not be as simple as that, but it also might not be impossible as well. There must be some method to Adobe's madness and if you ever decode it you'll need to interface with Affinity's madness. Sounds like fun.

I purchased version 2, in hopes that this "simple" feature would be integrated into the new package. It's the one feature lacking that I really, really want. Clearly, the code to "move starting point using the spacebar" has been invented because it works like a champ with shapes. We just need to apply the same concept to the creations of marquee selections. Since this issue has been hanging around for 7 years, it's clearly a low priority for whatever reason. So, it's time to put my money where my mouth is. Give me access to the code for creation of the shapes and also the code for creation of the marquee selections and I'll try and write up a git pull request. Or give us a "pseudo" macro language where we can modify the activity of your program to give us custom features like this. If none of this can be accomplished, at least speak to the nature of why it has been relegated to the hind teat at Affinity. Inquiring minds want to know. Thanks for your attention to this matter.

Dear Callum, I'm embarrassed to say that I cannot find the rasterization option under the "print menu" that you referenced. I tried. I googled it and never did find it. I'm running version 1.10 f4c94 of publisher. I've combed all over the "print" dialog box and I cannot find the rasterization tick mark that you are talking about. Can you explain exactly, how to walk through the menus to find it? Thanks so much, over and out, Mark

Sorry for the lengthy title. I have a pdf that contains two tabloid pages with both text and images that I'm printing on a Xerox C8000 printer. If I bring the PDF file up on screen using the MAC OS finder and print the pdf then the output looks spectacular. However, oftentimes I want to make minor corrections to the PDF after it is generated so I'll open the PDF in Affinity Publisher, make the changes and save this document as an Affinity Publisher file. However when I go to print the document from Affinity Publisher afterwards, the output in certain textual fields has dramatic changes to the stroke width and color of the text (images are unaffected). What's particularly strange is that change will take place in the middle of a character. But, not all characters have this problem. Obviously, I have a work around (although it took me a long time to find it as I didn't anticipate this outcome) to just print from MAC OS and I'm grateful for that. I understand that the solution to the problem may be beyond Affinity's reach as users and print drivers are involved. However, importing PDFs is a fairly critical conversion function and if we can get that process streamlined we will all benefit. I'll upload a couple of snippet scans showcasing the problem. These scans are from a real estate brochure so please excuse the commercial aspect. It's just that these fragment scans are some of the best examples of the phenomena. DocumentationOf_PDF_ImportProblemWithAffinityPublisher.pdf