SallijaneG

I had a similar issue tried all sorts of exports, and it turned out that I had duplicates of the font on the computer; when I got rid of the extras, the problem resolved.

Baseline Grid makes sense; had not thought of that.

I subscribe to the MyFonts newsletter, which often has sales, and also get a lot of good free fonts at FontSquirrel.

It would be nice, as would color fonts, but tagged PDFs for accessibility is WAY more important.

What does your Paragraph leading specification say? At the top of the Paragraph screen, is Exactly selected? If so, then choosing 17 should give you the result you want.

My assumption (and we know what happens when one assumes) is that it would look O.K., but not be editable. Going in the other direction, InDesign to Publisher, requires the InDesign document to be output as an IDML file, and the result is good but not perfect.

Yes, but my understanding is that requirements for e-books and printing presses are different enough that conversion is really complex. I don’t know enough to know how much extra infrastructure is required (Is something like InDesign that does both twice the size of Publisher? What choices in the early stages commits a project to being either paper-optimized or web-optimized?), but if it is critical for some users, they should keep pushing. I find in my work the tagged-PDF accessibility issues more important. Lots of users with varied needs. . . .

I have a colleague who is able to do it manually with Adobe Acrobat, but we are a small grassroots group that publishes <1 document per month. Not sure about better options for those with serious volumes, but this is a serious missing piece and should be the single item for which we all clamor. They did listen to all the requests for footnotes, so maybe. . . . .?

One of the big requests was provided: footnotes! Now we all need to keep clamoring for tagged PDF/EPUB options!

I do a lot of hybrid publications that are printed and viewed on the Web, I had someone demonstrate what a screen reader does with a PDF and was appalled at how inaccessible they are by nature. This is mission-critical; we need to be able to produce accessible PDFs from Publisher files, and although I am personally in an organization that has someone who can take the extra time it needs from Publisher as compared to InDesign, it will be a major stumbling block for growth. I am an amateur; my work is for grassroots groups that cannot afford Adobe and I personally refuse to spend the extra for a subscription, but I am an exception, willing to muddle through. Generally, this will be a deal-breaker for many.

I like this idea, though as a nonprofessional being able to simply switch personas rather than programs is usually enough for me.

Yeah, it startled me for the first time, too, but then I realized that the output would be the same and I got used to the new look.

Should I post my similar problem here or as a new topic? Early 2015 Mac, 11.7.6 Big Sur. Publisher 2.1, a file updated from last year’s issue of the same newsletter, when printing the Zilla Slab font is partly corrupted—strange characters added over and between words; curly brackets, underscores, hyphens, ampersands, double brackets, pilcrows, ligatures (ffi, fl, etc.). Cooper Hewitt text on same page is clean. I copied a paragraph of Zilla Slab into Libre Office, exported it as a graphic, and the text is clean. Attaching samples here. News&Views23Summer.pg2.pdf

I switched to a newer PDF format and exported, no change. I added new pages and copied the various pieces onto them, got weird results (only the header image showing up in the PDF, for instance), and this morning thought—HA! I have 2 in the series that worked, I will just paste the text from the problem file into a clone of one of those, and it worked, exported into the Media Library with no issue. (BTW, I am something of an amateur; clipping path? I’ll have to look that up. Hmm, I did not knowingly create a clipping path—no background removal, just a few text boxes and graphics placed on a single letter-sized page; I guess it will just remain a mystery. Thanks for your efforts.)

From their perspective, this is probably a feature, not a bug—encourages folks to stay within the Google eco-system. Sorry, not I! (Maybe I am just too cynical.)

I am putting this here because it seemed to be related; I searched “black background” to see if others had a similar problem. I created the file below, “2207 HOSS FactSheet” in Affinity Publisher, 1.10.5, on a Macbook Pro, Big Sur, 11.6.5, then exported as a PDF. It looked fine, so then I uploaded it to WordPress media library, and got the file called “What the Heck?”—the text was suddenly unreadable on the black background. I solved it by creating a white 8.5x11" rectangle, and layering it under everything else—but that is a work-around, not a solution. I have 2 other files in the series of fact sheets, same issue, same work-around. I just exported as a PNG, to make it easier to see the difference side by side; that file is “What 2207 HOSS FactSheet”. Help? 2207 HOSS FactSheet.pdf

Thanks, Dezinah, that is really helpful for understanding what is needed.

Because I am creating documents mostly for print, knew InDesign really well and transferred seamlessly to Affinity Publisher et al., and now need to make accessible documents, and just learned that EPUB is the easiest format for screen readers. (My PDF documents are increasingly often also being posted to Web sites.) Also, Google docs eliminates all the formatting when someone opens a PDF, destroying the aesthetics on which I worked so hard—though perhaps rather than make the actual file accessible, the staff person who is doing the accessible version should go ahead and do that through Google or Libre/Open Office.

That is what we are doing at UUJEC; we have a subscription to Acrobat Pro through TechSoup, but it takes lots of time for our one part-time staff person to add accessibility. Support for tagging would make this much easier! Please, major request for version 2.0!

How many records did you have? 24? I think it copied the format of the first page to create enough boxes for each. I cheated with mine, given that I had to get them in the mail today and still had copies to make and multiple meetings, exported the pages as JPEGs and inserted them into the Open Office template for Avery labels. Next time, I convert the template to a PDF, import it into Publisher, and try again.

Thanks; seeing this project laid out helped me get my address labels to work! (on 15 individual, label-sized pages—next step, using an Avery label template.) It has been a long time since I did this sort of project.

I am also on Sierra, though an early-2015 laptop, and am not planning to update right away. Just being conservative. . .

I have the 3 Affinity programs (1.8.3) on Macbook Pro, Sierra 10.12.6, and have no immediate plans to upgrade my system or get a new computer. I am was considering going to 1.8.6, checking here for system requirements, and am now concerned about the application- and file-size issues that I see in this discussion. Can anyone tell me if I am missing a compelling reason for me to update the Affinity programs?

Yes, when I create a new file and want to save it to a specific folder, unless that folder was one of the most recent I opened (Macbook Pro, Sierra, 10.12.6), I either have to go to that folder separately to open and save something, so that it becomes one of my recent places, or stash it on the desktop until I get around to dragging my documents off the desktop to their respective proper places. An extra unnecessary step.