Bugs in PDF processing from a Google Doc

A number of bugs exist regarding creating a PDF form a Google Doc.

Has anyone experienced these? Are they Known bugs?

  1. Auto Numbering on Headings does not work. ( comes out blank)

  2. First-page header/footer does not work.

  3. Tab stops to align/headers and footers do not work. So left aligned, centre right-aligned, typical of headers does not align properly)

Page Headers, Page Footers, and Page Numbering are Not Supported

Workflow templates do not support automatic page headers, page footers, or page numbering.

If your Word template file contains Word Headers, Word Footers, or Page Numbers they will be ignored.

  • Instead, you should include your header contents at the start of your template as normal content. It will appear once at the start of the resulting document.
  • You should include your footer contents at the end of your template as normal content. It will appear once at the end of the resulting document.

To handle automatic page headers, page footers, and page numbering, we would need to implement a “page layout engine” that computes the page location of each element being displayed. We would need to be aware of page boundaries, so that we could:

  • Insert a footer at the end of each page.
  • Insert a bottom margin at the end of each page.
  • Insert a top margin at the start of each new page.
  • Insert a header at the start of each new page.
  • Insert appropriate page numbers.

We do not support any of these features because implementing a “page layout engine” is a lot of work. It is not work that we have done.

5 Likes

Thanks for your reply.

It’s shame because it makes it unworkable for my planned professional application.

However, I do understand the complexities, having myself implemented PDF print engines for our offline apps using Microsoft Word, Javascript and CSS.

1 Like

I understand. I have the same issues… I doubt this will work for you, but there’s this…

2 Likes