FrameMaker 2019 not converting landscape pages properly

[monrocks12]

Since upgrading to FrameMaker 2019, we have experienced issued when converting files with landscaped pages to PDF. When using the Save as PDF command, the content of the page is fine, but the header and footer text on the page is rotated and garbled. Printing to PDF solves this issues for single files. However, when we convert a book containing files with landscaped pages, it becomes problematic. Some books are too large to use the Print to PDF command, and replacing sections of the PDF rotates and moves the link boxes. Will a fix be coming for this issue? We did not have this problem with our last version of FrameMaker.

[Jeff_Coatsworth]

Are you all patched up? There were some PDF fixes in patch 2 (IIRC) - you might also try the PDF creation route via the Publishing pod for the new faster method of PDFing.

[erika-runninggirl]

Hi,

I just updated my version of FrameMaker 2019 becuase I have this same issue but it has not been fixed. Any suggestions on fixing it?

Erika

[Matt S - Tech Comm Tools]

(removed, as system duplicated the reply)

[Matt S - Tech Comm Tools]

I agree with Jeff...the better approach is to use the Publish panel, especially since the PDF engine is again improved in Fm 2020.

It sounds like the file might be corrupt. Try saving as MIF and then reopening in Fm. If that doesn't work, try pasting the content into a "new" Fm doc and retest.

Let us know what you find.

-Matt

[dauphinb]

My group's standard process uses Print Selected Files for PDF generation anyway, but recently I was experimenting with the Publishing pod and got exactly the same problem reported in the OP. We're probably a couple patches behind (because our byzantine corporate IT environment makes timely updates difficult; we're on FM2019, BTW), but I see another person has reported the same problem with a fully patched-up implementation. I tried this with a couple different files, all of which behave perfectly normally in other respects, so I question whether file corruption is the issue.

I'm interested to see if anyone has an answer: If so, I might revisit incorporating the Publishing pod into our workflow (which predates the existence of the Publishing pod!).