Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies reply
    1
  • Subscribers subscribers
    3
  • Views views
    649
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Pagination not possible on rendering documents to HTML using KeyView Export SDK

VijayasankarNR
 

This issue is with respect to Micro Focus Filr,  In Filr we use Keyview Export SDK's HTML Export to render the documents to HTML and use it as file preview in the iframe. Now,  when I preview the HTML, there are no page definitions, it's acts as an single page (refe preview.PNG). I tried different template examples and played around with it to get effective pagination. It did not help.  Is it possible to achieve pagination by changing some configuration in the ini file? Or atleast produce different html files for every page (like done with default.ini template but without the table of contents)

And I also see that height and width of the document are not retained in the Html output, Also curious how does converting the document to pdf using pdf export retains the pagination, as well as height and width of the document when HTML does not.

~ Vijay

  • 0

    To split the HTML into separate files, take a look at bPutBlocksInSeparateFiles in the KVHTMLOptionsEx section/structure.

    What constitutes a "page" is determined by one of two factors: either something stored within the document itself, or on-the-fly size/positioning calculations that are done within the application displaying the document. PDF, as a layout format, relies on the former, where the page is actually a unit within the document structure itself. Most word processing formats, e.g. MS Word's DOC and DOCX, rely mostly on the latter; while they do allow you to insert explicit page breaks, most are implicitly based on things like the size of the font and pages.

    HTML doesn't natively support the notion of a page, nor do web browsers' default views really do so, either. Most functionality that you see doing this requires additional styling/scripting to determine where such breaks need to occur, and to produce a page-like rendering of the document. The HTML Export APIs allow a number of places for developers to insert formatting/styling of their own.

    If there's some aspect of this you'd like to delve into further, I'd recommend opening a support ticket.

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.