Jump to content

ricecrispies

Members
  • Posts

    60
  • Joined

  • Last visited

Recent Profile Visitors

583 profile views
  1. I have a document that I have made in Affinity Publisher that I need to export as a PDF and then tag in another application to make it accessible. The problem is that many of the diagrams in the document are composed of multiple elements (bitmaps, text, vectors), which leads to complete chaos when I open the PDF in Foxit Editor Pro. Some of the bitmaps don't show up; the read order jumps backwards and forwards through the document like crazy; and for one element (a vector graphic logo), the alt text that I assign doesn't get read out by the screen reader; meanwhile, the screen reader reads out every bit of text in the diagrams, even though I don't want it to. What I want to do is to flatten each of these bundles of bitmaps, text, and vectors into a single image before I export. How can I do that?
  2. I worked without hardware acceleration this evening for a while without a crash. I'll report back here if that changes. Otherwise, assume that the problem is solved and thanks for the tip!
  3. Today I have tried to use Publisher and Photo for the first time in a while, but they crash, freeze or hang every few minutes. I haven't tried using Designer today, so I don't know how that would behave. I am running them on Windows 10 21H1 and using version 1.10.4 of both applications. Publisher crashed a couple of times while I was trying to open the print dialogue, and another time when I was trying to open a file. It also froze and refused to terminate when I selected "exit". I don't remember all the other crashes. The project I was working on was a trivially simple single sheet with a little text. And then this evening I have found that Photo is similarly unstable. It hung when I tried to open an afphoto project and crashed when I tried to open an image from the clipboard as a project. There was another crash that I don't remember the circumstances of. And all this was probably within the space of 20 minutes.
  4. Sorry, I forgot to follow this thread when I created it, which is why I didn't reply. Unfortunately, 5 months later, I am still getting crashes. Since July I have upgraded to the latest version (1.10.4.1198) but, after starting to use Publisher again yesterday, I have been getting several crashes per hour. These occur in various situations. It happened once while opening a Publisher file, and several times while opening the print dialogue. I also had a freeze today when I was trying to exit Publisher. The projects I am working on at the moment are trivially simple. Just a little bit of black text on a white background on a single page of 6"×4". I've been printing to an ordinary Brother laser printer and a Canon Pixma i7250 inkjet, so again, nothing complicated.
  5. Well updating the fonts fixed the naming issue, but there are still discrepancies. Some of the worst ones were fixed, such as the dots in a colon being square rather than round in Word, but some remain. The text I wanted was simply ::1 (the ipv6 loopback address). In Affinity, the space between the two colons and that between the second colon and the 1 are about the same. In Word, the space between the colons is considerably greater, looking oblong rather than square. The way Affinity does it actually looks better, but I assume that the Microsoft would have tested the font in their own products, in which case it would be Affinity that is deviant, not Word.
  6. I created a Word document with a lot of different monospaced fonts so that I could compare them. I then tried to use some of the same fonts in Affinity photo, but found that the weights were nothing like the weights displayed in Word. For instance, Cascadia Mono SemiBold and Cascadia Code SemiBold are not even offered as options in Photo (only regular and italic are offered). Meanwhile, ordinary Cascadia Mono is much heavier in Word than in Photo, where it is little more than lines, rather than shapes. What is going on?
  7. HI Dan, I've uploaded the file. Some more background: Because of this bug, which is to do with resizing the document, I had to delete the text boxes I had created before resizing, after copying and pasting their contents into new text boxes. The anchors with an em-dash at the end of their names seem to be those belonging to the deleted text boxes. However, even after accounting for these, there were still quite a few other duplicate anchors. Some of these I had already deleted by the time the document had got to the state it was in when I uploaded it here.
  8. I have found a kind of workaround. It is possible to delete the unwanted anchors after the PDF has been created using the freeware Foxit Reader, but that still leaves all the garbage anchors in the original Publisher document.
  9. In the document I am currently working on I have discovered that there are a huge number of excess anchors, usually between 3 and 5 for each heading. Some have names that relate to previous versions of the titles of headings that have now changed. Some of these excess anchors I have been able to delete, but there are a huge number of supposed anchors in the list of anchors, all with an em-dash at the ends of their names, that don't seem to actually have a corresponding anchor in the actual document. If I try to delete these non-anchors, they don't go away, but instead chunks get deleted from the text of the document. How can I get rid of these non-anchor anchors without destroying my document?
  10. I've just discovered that I can use Export to create PDFs instead of Print. That gives many more options, including digital PDFs, and doesn't fuss about page size.
  11. The trouble is that it still prints to a A4 or a handful of other sizes, which you have to choose by going into the printer properties, but not A6. In other words you end up with an A4 document in which only the top left quadrant of each page is printed.
  12. I've found a workaround. I can't say for certain that it doesn't involve some degradation of the quality of the document, but it's fine for my current purposes: It's the online converter at https://pdf2go.com/resize-pdf I ran the file I got through a virus scanner, just to be safe, but it seems OK.
  13. In the document that I am working on in Publisher at the moment, when I try to open the Print dialogue (i.e. when I click to ignore pre-flight warnings), Publisher crashes around 50% of the time. I experience other fairly frequent completely unexpected crashes as well, but the print dialogue crashes are by far the most frequent. I also have other problems with printing. I have been trying to print to PDF, and at least a couple of times it has created corrupted PDFs and then refused to print PDFs at all afterwards saying there is a problem initialising the printer. Not knowing what else to do, I reboot to get it working again. I have also been having trouble printing to file. (I was trying to create an XPS file because Microsoft Print to PDF doesn't offer the option of printing to A6), but the XPS files it creates are corrupt and cannot be read by Window XPS Reader or the online service I was trying to use to convert them to PDF. I am using Publisher 1.9.2.1035 on Windows 10 version 21H1. I have attached the project I am working on. It is the first project I have done in Publisher for a year, so I don't know whether I can reproduce the problems with other projects. clock manual A5.afpub EDIT: After having dozens of these crashes, I can now say that it happens completely predictably. The ratio of crashes is exactly 50%. Crashes and successful opening of the print dialogue strictly alternate. If last time it crashed, then this time it will work. If last time it worked, then this time it will crash.
  14. Is there a way to print an A6 document from Publisher to PDF in Windows 10 (version 21H1)? In the advanced printer properties as accessed through the control panel, a huge number of paper sizes are defined for the PDF printer, including A6, but when it comes to actually printing, the printer properties that are accessible from the Publisher print dialogue only include a tiny handful of those sizes, and A6 is one of those excluded. The only solution I have come across so far is a hugely complicated registry hack. I don't mind tweaking a value here and there in the registry, but I'm not comfortable rewriting whole chunks of it. And in any case, the registry hack is for defining new paper sizes, not for enabling paper sizes that have already been defined.
×
×
  • 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.