I have 800 .hlp files which are not actually WinHelp, but some proprietary form of help file, and we need to convert them into something readable. I guess my first question is whether or not anyone can tell from the output below what type of help file this is. Open Interface comes up when you click on "Help" within the help application itself. Perhaps there is a software upgrade which would solve the problem.
Since it is not an actual WinHelp file, RoboHelp cannot import it. Instead of manually rewriting the files, I was wondering if an elaborate regular _expression_ could work, or whether some other software or programming language could be used. The file below contains formatting that I could theoretically recognize, and pull the appropriate data to make an html file. For example, I want to locate the first the "topic" line and make that the header for a new html document. The text between "\0\p\p\p will become the text below that. Any \subtopic will be hyperlinks to bookmarks to the corresponding \topic text below it, and so on.
I can write out what I want in Plain Language, so there must be a way in a programming language. I just need to be pointed in the right direction. Any ideas are greatly appreciated.
Thanks in advance.
Sincerely,
Andrew
\file "styles.hlp"
\def_style 0\font font.normal \fg color.black \bg color.transparent
\def_style 1\font font.normal \fg color.black \bg color.yellow
\def_style 2\font font.bold \fg color.blue \bg color.transparent \curs helpw.curstopic
\def_style 3\font font.normal \fg color.black \bg color.yellow
\def_style 4\font font.normal \fg color.black \bg color.yellow
\def_style 5\font font.normal \fg color.black \bg color.transparent
\def_style 7\font font.bold \fg color.black \bg color.transparent
\[------------------------------------------------\]
\topic "Purchasing Three-Way Match Index (TWPU) Window"
\0 \{\set_style "topic_title" Purchasing Three-Way Match Index (TWPU) Window \}
\0\p\p\p
Purchasing Three-Way Match Index (TWPU) provides status
information for purchase orders and subsequent documents.
This screen is organized by status for each purchase order.
\0\p\p
\{\subtopic "Status" \set_style "goto_style" Status \} \0\p
\{\subtopic "Vendor Number" \set_style "goto_style" Vendor Number \} \0\p
\{\subtopic "Vendor Addr Ind" \set_style "goto_style" Vendor Addr Ind \} \0\p
\{\subtopic "Purchase Order Transaction ID" \set_style "goto_style" Purchase Order Transaction ID \} \0\p
\{\subtopic "Line" \set_style "goto_style" Line \} \0\p
\{\subtopic "Match ID Transaction ID" \set_style "goto_style" Match ID Transaction ID \} \0\p
\{\subtopic "Line Num" \set_style "goto_style" Line Num \} \0\p
\{\subtopic "P/F Ind" \set_style "goto_style" P/F Ind \} \0\p
\{\subtopic "Payment Flag" \set_style "goto_style" Payment Flag \} \0\p
\{\subtopic "Cond Flag" \set_style "goto_style" Cond Flag \} \0\p
\[------------------------------------------------------------\]
\topic "Status" \set_style "topic_title" Status
\label XSTATUS_2
\0\p\p
Key field. Valid values are:
\0\p\p\{\set_style "valid_value" Entry Added During the Day [**]
\} \0 \0\p\p\{\set_style "valid_value" ThreeWay Match [A1]
\} \0 \0\p\p\{\set_style "valid_value" Three-Way Match Requiring Review [A2]
\} \0 A condition exists that requires manual review.
\0\p\p\{\set_style "valid_value" Received but not Invoiced [B1]
\} \0 \0\p\p\{\set_style "valid_value" Invoiced but not Received [B2]
\} \0 \0\p\p\{\set_style "valid_value" Neither Received nor Invoiced [C]
\} \0 \0\p\p\{\set_style "valid_value" Entry to be Deleted [*]
\} \0 The entry is deleted during the next processing cycle.
\0\p\p
\topic "Vendor Number" \set_style "topic_title" Vendor Number
\label VENDOR_NUMBER
\0\p\p
Key field. Displays the unique vendor code that identifies
the vendor associated with the order.
\0\p\p
\topic "Vendor Addr Ind" \set_style "topic_title" Vendor Addr Ind
\label VENDOR_ADDR_IND
\0\p\p
Key field. Part of the vendor code, this field indicates
whether an alternate address exists for the vendor.
\0\p\p
\topic "Purchase Order Transaction ID" \set_style "topic_title" Purchase Order Transaction ID
\label PO_TRANS_CODE
\label PO_NUMBER_AGENCY
\label PO_NUMBER_NUMBER
\0\p\p
Key field. Displays the unique document ID that identifies
this purchase order.
\0\p\p
\topic "Line" \set_style "topic_title" Line
\label PO_LINE
\0\p\p
Key field. Displays the line number from the purchase order.
\0\p\p
\topic "Match ID Transaction ID" \set_style "topic_title" Match ID Transaction ID
\label MATCH_TRANS_CODE
\label MATCH_NUMBER_AGENCY
\label MATCH_NUMBER_NUMBER
\0\p\p
Key field. Displays the transaction code and unique number
that identifies the Receiver (RC) or Vendor Invoice (VI)
associated with this match.
\0\p\p
\topic "Line Num" \set_style "topic_title" Line Num
\label MATCH_LINE
\0\p\p
Key field. Displays the line number of the Receiver (RC) or
Vendor Invoice (VI).
\0\p\p
\topic "P/F Ind" \set_style "topic_title" P/F Ind
\label FINAL_MATCH_FLAG
\0\p\p
Display only. Displays \{\set_style "valid_value" F \} \0 if the document matching the is a
final transaction (for example: final receipt or invoice).
Otherwise, this field displays \{\set_style "valid_value" P \} \0 for partial.
\0\p\p
\topic "Payment Flag" \set_style "topic_title" Payment Flag
\label PAYMENT_FLAG
\0\p\p
Display only. Displays \{\set_style "valid_value" Y \} \0 if final payment is made against
this match record.
\0\p\p
\topic "Cond Flag" \set_style "topic_title" Cond Flag
\label CONDITION_FLAG
\0\p\p
Display only. Displays \{\set_style "valid_value" Y \} \0 if there is a special condition
associated with one of the match records.
\0\p\p
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
