html2ipf.cmd
because it's so damn slow and doesn't support
string replacements.
ipfc
from the Developer's
Toolkit. See "Requirements" for where to get this utility.
make.cmd
file on the top level of the XWorkplace source
files to have the doc files created.
I recommend translating all the .HTML
files and
keep using make.cmd
to have the HTML files converted into a single .IPF file
(using my h2i
utility), which can then be fed into ipfc
.
This has the advantage that you'll only have to change some panels
in future versions, of which I will keep track. Also, I always note changes
to the INF and HLP files in the HTML source files in HTML comments tags, so
you can easily search for what's changed.
The "root" file in each of the two source directories
is called xfldrXXX.html
, respectively, with "xxx" being your
country code (which you should change in this one filename because
h2i
will use this name for the target IPF file also).
In any case, mind these important notes:
xfldrXXX.html
is the "root" file.
All other files are somwhere below in the INF/HLP table-of-contents
hierarchy, depending on the SUBLINKS
tags in the HTML source files.
h2i
sorts the IPF pages internally
alphabetically according to the filenames, that's why I've
implemented these strange naming conventions. I admit that since
the structure has developed over time, it may not seem very
logical to you, but it works. Changing things here will result
in a lot of work, since all the links in the HTML files would
have to be adjusted also.