These are HTML - IPF conversion utilities. They are designed to allow HTML and IPF documents to be quickly converted, making it easier to write in both formats. They are compliant with the version 3.2 HTML specification. IPF is the document format used for OS/2 on-line references.
All HTML tags and symbols are substituted for their equivalent IPF symbol, and vice versa. The output files should be checked to validate or correct them. This converter is designed to do 95% of the work.
This converter is shareware. It is freely available on the Internet. It may be freely distributed with all files intact, but I would like to be informed if it is distributed as part of any packages. Users must NOT be charged for this converter; it is up to them to register.
It will hopefully be available for Linux (it is compiled using Red Hat release 3.0.3 (Picasso)), OS/2 Warp 3.0, DOS 3.3, and Windows 3.1 (95 and NT). Download the latest version from your favourite FTP site, or check at my home page.
For Linux users, ask your System Administrator to put the executables html2ipf and ipf2html in the /usr/bin directory.
For OS/2, DOS, and Windows users, place the executables HTML2IPF.EXE and IPF2HTML.EXE in any directory, but preferably in your path.
OS/2 users might like to create program objects for the executables. Then drop any HTML/IPF file onto the Html2ipf/Ipf2html object, and it will convert them for you. (You might need the emx.dll runtime library.)
Windows 3.1/95/NT users may create an icon (or a shadow) pointing to the executables. You may need to use the icon's arguments to set the file to convert, or using the File Manager, drop the HTML/IPF file icon onto the appropriate executable's icon.
The converters may operate in a few modes. Type
html2ipf -? or ipf2html -?
to list the usage modes. The possible modes are
| Arguments | Description |
| -s | Simple conversion |
| -a | Adds HTML/IPF tag arguments (default mode) |
| -l | Lists all tags found, in html.out (or ipf.out) |
| -b | Adds and lists HTML/IPF tags (ie both -a and -l) |
| -? | Reports usage instructions |
To simply convert an HTML file to IPF, type
html2ipf HTML file
Where the first argument, HTML file, is the file to convert. A new file, result.out, contains the resultant IPF file. Edit it to suit your needs.
These converters do not convert the complete tags. They find the best equivalent tag, and place it in the output file. The rest of the tag is also placed, unchanged, after it. It's left up to YOU to complete the document.
To convert an HTML file to IPF and use a different filename for output, type html2ipf HTML file IPF file
Where IPF file will contain the resultant IPF file.
You may use one of the above arguments for a conversion mode, as in
html2ipf -l HTML file
-s will not write the unconverted tags to the output file. -a will; it is the default mode. -l will produce an additonal file, html.out (or ipf.out), which lists all HTML/IPF tags and symbols detected with the lines numbers where they were found. -b will do both; write the remaining tags and list them. Unknown tags will also be listed in this file, to find which tags weren't recognised.
These converters are shareware. Everybody may freely distribute these HTML - IPF conversion tools, as long as all files are intact. Personal users who use them on a regular basis (eg fortnightly) must register by sending
to the author. Businesses must register by sending
to the author, for each machine it is used on. Site license agreements may be negotiable.
PLEASE register by informing the author by post. This will encourage future releases. Make sure you include your contact details, version, and operating system. If anyone has suggestions for improvement, problems, complaints, or a job (!) for me, I would love to hear from you!
Mr Antonino IannellaEmail antonino@usa.net or nettuno@light.iinet.net.au.
Download latest versions from http://members.tripod.com/~antonino.
Version 1 - Released. Line numbers might be inaccurate in html.out/ipf.out.
Does not remove hidden text from IPF files; places a warning instead.
Does not use embedded files; links to them instead.
Problems occur when converting symbols, since HTML and IPF use
different character sets, as do UNIX and DOS-OS/2.