Differences

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

--- en:docs:tk:tools:mkmsgf [2024/01/21 11:51] – prokushev
+++ en:docs:tk:tools:mkmsgf [2024/05/23 08:49] – prokushev
@@ Line 23: / Line 23: @@
 | | |!| | | |!|
 | | |)|/V|(|
+| | |!| | | |!|
+| | |)|/Q|(|
 | | |!| | | |!|
 | | |)|/D <DBCS range or country>|(|
@@ Line 89: / Line 91: @@
         RMS     23      1       Rhaeto-Romanic          Switzerland
         ROM     24      1       Romanian                Romania
-        RUS     25      1       Russian                 U.S.S.R.
+        RUS     25      1       Russian                 Russian Federation
         SHL     26      1       Croato-Serbian (Lat     Yugoslavia
         SHC     26      2       Serbo-Croatian (Cyr     Yugoslavia
@@ Line 103: / Line 105: @@
 For a complete list of code pages and country codes, see the code page table under [[https://komh.github.io/os2books/os2tk45/cp2/061_L2_COUNTRYCODE.html|COUNTRYCODE]] in the online book Control Program Programming Guide and Reference.
+===== Output File =====
-Output File
 The output file contains the indexed message file that DosGetMessage will use. The output-file name can be any valid OS/2 file name, optionally preceded by a drive letter and a path. The output file cannot have the same name as the input file.
@@ Line 111: / Line 113: @@
     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.
-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.
@@ Line 129: / Line 131: @@
     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.
-Options Summary
+===== Options Summary =====
   Type 	Meaning
   /P 	Code-page ID for the input message file.
@@ Line 139: / Line 142: @@
   /V 	Verbose display of message file control variables as the message file is being created.
   /? 	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.
@@ Line 186: / Line 192: @@
 A valid language family with invalid or undefined language version id will cause a default value of 1 to be set for language version.
-/A /C /I Options
-I saw these and documented them as existing years ago, but never really looked at them in depth. I made some notes on a separate page: The A, C, and I Options.
 /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.