Skip to main content
A
AIR-Chayah
Inspiring
March 31, 2016
Question

Problems with tables generated by Create PDF for Review

  • March 31, 2016
  • 1 reply
  • 1053 views

RH 2015. All updates installed.

Due to the nature of the product, the Help includes many very long tables. When you Create a PDF for Review, the tables look worse than they do in the online Help. Table headers don't continue to the next 'page' and the last row of a table on a PDF page ends up with no border.

  • Is there any way in RoboHelp to force table headers to continue to the next "page" (as they do in Word), or is this unreasonable because online Help doesn't distinguish "pages"?
  • Do any of you know of any ways to edit tables in the PDF? I've researched this and mostly seen comments that you can't do it, that's not what PDF was designed to do.

Thank you.

Carol

This topic has been closed for replies.

1 reply

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
April 3, 2016

The way to get table headers to go to the next page is to generate to Word first. There you can run a macro to apply that setting to all tables, then you generate to PDF.

Borders can be tricky. Does it fail in Word or is it at the Word to PDF stage?

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
A
AIR-ChayahAuthor
Inspiring
April 3, 2016

Hi, Peter.

We're now going through Create PDF for Review instead of going through a Printed Documentation SSL because of the internal errors we get with Printed Documentation SSLs (Adobe TCS is supposed to be looking at this problem.) Basically, the output is generated but the process fails to create the TOC, and we do get Word errors. We can use F9 to generate the TOC, but the output from our project isn't great. (We've not yet tried mapping styles, etc.)

When we use Create PDF for Review, we get a pretty decent looking PDF, much better than the output of the Printed Documentation SSL, and there are no errors. The only problem we have in the PDF created using Create PDF for Review is with the lack of table continuation.

Adobe TCS suggested that the problem with Printed Documentation might be related to the fact that we work out of Source Control and there might be a communication problem between TFS and RoboHelp. (We're also unable to import or create skins.)

Thanks again!

Carol

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
April 8, 2016

Good morning, Peter.

Here's the information that I got back from Adobe TCS after they set up a TFS environment.

"Further to the issue, the printed documentation is working fine on this project on Team Foundation Server. Also when I added a new WebHelp skin I was able to get the folder for the same on Visual Studio Explorer. I suspect the issue seems to be with the communication of the project on your computer to Team Foundation Server. Please try to create a new Team Project from File> New Team Project in Microsoft Visual Studio Source Control Explorer and then link the project and check the issue further."

Since our TFS release engineers are quite busy right now (we're at the tail end of development for a June release), we probably won't have time to try the new Team Project approach for at least a few weeks. When we do, I'll be sure to keep the forum posted on the results.

For now, for draft purposes, Create PDF for Review works well enough for everything except the tables and the missing image in the notes.

Regards,

Carol Levine


I'll look forward to your update and hope it is good news. It will be the

end of a frustrating period for you.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices