Separate header and footer

I’ve been using your library today. It seems to be the light at the end of the tunnel for some problems we have been having with docx extraction when docs contain headers, footers, endnotes and footnotes. Almost everything else we’ve tried has been incapable of parsing these properly when they co-exist in a document. And no system dependencies… I salute you!

One issue I have found is that both the header and footer content gets bundled into data._headers. Is there much of a change to make to separate the footer into a new data._footers property?

[thegoatherder]

I’m looking for all visible text… but I don’t think it’s a huge deal if we do get some hidden text included in the extracts. I’d say go the easy route!

On Mon 24 May 2021 at 01:21, Stuart Watt @.***> wrote:

Quick question @thegoatherder https://github.com/thegoatherder – I assume you don’t worry about whether a header/footer is shown? One of the sneaky things I found is that, e.g., someone can have a “first page only” header that is switched off, so it’s never seen. Can I assume you don’t care whether the header/footer is actually rendered?

It’s very hard to tell whether any particular headers/footers are actually shown, because that can depend on everything down to the pagination, and therefore font size, etc.

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/morungos/node-word-extractor/issues/34#issuecomment-846652474, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC7EJHCEPUZBGT25KFFEY3TPGL2DANCNFSM45JT452A .

–

---

“Are you sleep walking through your waking life …or wake walking through your dreams?”

[thegoatherder]

@morungos thank you very much for your time on this, it’s been a massive help. I can confirm getFooters() is working as expected on our test data.