How to use the combination INF2HTML and HTML2IPF+IPFC ?
Lars Erdmann
I want to update an .INF file. I used INF2HTML to generate HTML output,
updated the HTML and tried to compile back to .INF via HTML2IPF+IPFC.
In principle this works. However all chapter nesting is destroyed in the
resulting .INF file.
What do I have to do/how do I have to call these tools to get back the
chapter nesting of the original document ?
Thanks for any help,
Lars
Steven Levine
wrote:
Hallo Lars,
> What do I have to do/how do I have to call these tools to get back the
> chapter nesting of the original document ?
Which version of the tools are you using? There are a number of
versions floating about.
A quick look at the version of html2ipf used by xworkplaces leads me
to believe that the chapters are defined by the page nesting. Does
this match what you are seeing?
Steven
--
---------------------------------------------------------------------
Steven Levine <ste...@earthlink.bogus.net>
eCS/Warp/DIY etc. www.scoug.com www.ecomstation.com
---------------------------------------------------------------------
Lars Erdmann
> On Wed, 9 Dec 2009 19:56:31 UTC, Lars Erdmann <lars.e...@arcor.de>
wrote:
>
> Hallo Lars,
>
>> What do I have to do/how do I have to call these tools to get back
the chapter nesting of the original document ?
>
> Which version of the tools are you using? There are a number of
versions floating about.
I took what I could find from hobbes:
1.) INF2HTML: Version 0.91 (version listed in readme.txt)
2.) HTML2IPF: Version 0.1.1 (version string output by tool)
3.) IPFC: Version 4.00.007 (version string output by tool)
> A quick look at the version of html2ipf used by xworkplaces leads me
to believe that the chapters are defined by the page nesting. Does this
match what you are seeing?
I believe not, judging from what you say.
I observe this: INF2HTML creates HTML lists from IPF chapters that are
on the same chapter level, containing HTML list elements for each IPF
chapter (and so on, recursively down until a chapter contains no further
subchapters but only IPF text paragraphs which are converted to HTML
paragraph elements).
HTML2IPF (correctly) converts these HTML elements to IPF lists and list
elements. But then, this leads to all chapter information being lost.
The resulting IPF (and INF of course) naturally only shows a flat list
without any chapter info.
Are you saying that the HTML2IPF version from netlabs (XWorkplace)
behaves differently ?
Lars
Steven Levine
wrote:
Hi Lars,
> I took what I could find from hobbes:
> 1.) INF2HTML: Version 0.91 (version listed in readme.txt)
> 2.) HTML2IPF: Version 0.1.1 (version string output by tool)
> 3.) IPFC: Version 4.00.007 (version string output by tool)
FWIW, you might want to cosider using OpenWatcom's wipfc. If you find
defects, at least they can be fixed.
> Are you saying that the HTML2IPF version from netlabs (XWorkplace)
> behaves differently ?
It might. Like I said, I only had time to take a quick look at the
source. I noticed a Depth variable near the code that output the :h
tags and I suspected it might be used to control chapter nesting.
Marcel Müller
> I want to update an .INF file. I used INF2HTML to generate HTML output,
> updated the HTML and tried to compile back to .INF via HTML2IPF+IPFC.
> In principle this works. However all chapter nesting is destroyed in the
> resulting .INF file.
Well, at least HTML2INF is not able to produce reasonable results in the
index structure of heavily cross linked pages. It is used by the PM123
source tree too, and I had to make major changes to source of HTML2IPF
and some changes to the HTML source too to get reasonable IPF documents.
This is a bit relaxed if the HTML documents are generated from IPF
because this reduces to a subset of the HTML language. However, as you
noticed, the document tree can only be preserved by additional (invalid)
attributes in the HTML root node. HTML editors likely will destroy this
kind of information because it is not part of the standard.
> What do I have to do/how do I have to call these tools to get back the
> chapter nesting of the original document ?
I would recommend to make the HTML version to the leading document and
generate the IPF version as part of the build process. Of course, you
still have to take care of the limited IPF features, because some things
definitely cannot be mapped to IPF, e.g. icons in tables.
Marcel