en:docs:tk:tools:mkmsgf

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
en:docs:tk:tools:mkmsgf [2024/03/26 13:06] – prokusheven:docs:tk:tools:mkmsgf [2024/03/26 13:10] (current) – prokushev
Line 111: Line 111:
  
     The infile file should have a .TXT extension.     The infile file should have a .TXT extension.
-    The outfile file should have a .MSG extension.+    The outfile file can have a .MSG or .INC extension.
  
 Help-message file names begin with the component identifier, followed by H.MSG. For example, the help file associated with the component identifier DOS would be DOSH.MSG. Help-message file names begin with the component identifier, followed by H.MSG. For example, the help file associated with the component identifier DOS would be DOSH.MSG.
  
 ===== Options ===== ===== Options =====
- 
  
 Text-based messages in different code pages can be created using MKMSGF to display errors, help information, prompt, or provide general information to the application user. Text-based messages in different code pages can be created using MKMSGF to display errors, help information, prompt, or provide general information to the application user.
Line 130: Line 129:
  
     Infile is the ASCII-text source file.     Infile is the ASCII-text source file.
-    Outfile is the binary output message file.+    Outfile is the binary output message file or MASM include file.
     @controlfile is the message definition file.     @controlfile is the message definition file.
  
Line 141: Line 140:
   /V Verbose display of message file control variables as the message file is being created.   /V Verbose display of message file control variables as the message file is being created.
   /? Help display of command syntax for MKMSGF.   /? Help display of command syntax for MKMSGF.
 +  /A    Produce MASM include file using INC file as include file for message constants
 +  /C    Produce MASM include file using H file as include file for message constants
 +  /I    Include paths
      
 Note: Any combination of /P, /D, /L, and /V switches can be used for either the command line or @controlfile execution method. Note: Any combination of /P, /D, /L, and /V switches can be used for either the command line or @controlfile execution method.
Line 192: Line 194:
 /E /E
  
-See the The Extended Structure page for more information. This tacks on what I call a fake extended header at the end of the file and updates the header offset.+Produce fake extended header. This tacks on what I call a fake extended header at the end of the file and updates the header offset.
  
-Control Files+===== Control File =====
  
 The control file (@controlfile) is used to create multiple-code-page message files. The at sign (@) is not part of the file name, but rather, a delimiter required before a control-file name. The control file (@controlfile) is used to create multiple-code-page message files. The at sign (@) is not part of the file name, but rather, a delimiter required before a control-file name.