Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| en:docs:tk:tools:mkmsgf [2024/01/21 07:05] – prokushev | en:docs:tk:tools:mkmsgf [2024/09/05 01:46] (current) – [Syntax] prokushev | ||
|---|---|---|---|
| Line 23: | Line 23: | ||
| | | |!| | | |!| | | | |!| | | |!| | ||
| | | |)|/V|(| | | | |)|/V|(| | ||
| + | | | |!| | | |!| | ||
| + | | | |)|/Q|(| | ||
| | | |!| | | |!| | | | |!| | | |!| | ||
| | | |)|/D <DBCS range or country> | | | |)|/D <DBCS range or country> | ||
| | | |!| | | |!| | | | |!| | | |!| | ||
| - | | | |)|/P <code page>|(| | + | | | |)|/P codepage|(| | 
| | | |!| | | |!| | | | |!| | | |!| | ||
| | | |)|/L < | | | |)|/L < | ||
| | | |!| | | |!| | | | |!| | | |!| | ||
| - | | | |)|/I <path>|(| | + | | | |)|/I path|(| | 
| | | |!| | | |!| | | | |!| | | |!| | ||
| | | |)|/A|(| | | | |)|/A|(| | ||
| Line 38: | Line 40: | ||
| </ | </ | ||
| - | MKMSGF infile[.ext] outfile[.ext] [/?] [/V] [/D <DBCS range or country> | + | |
| ===== Arguments ===== | ===== Arguments ===== | ||
| Line 89: | Line 91: | ||
|         RMS      |         RMS      | ||
|         ROM      |         ROM      | ||
| - |         RUS      | + |         RUS      | 
|         SHL      |         SHL      | ||
|         SHC      |         SHC      | ||
| Line 101: | Line 103: | ||
|         SLO      |         SLO      | ||
| - | For a complete list of code pages and country codes, see the code page table under COUNTRYCODE in the online book Control Program Programming Guide and Reference. | + | For a complete list of code pages and country codes, see the code page table under [[https:// | 
| + | ===== 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. | 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 infile file should have a .TXT extension. | ||
| - |     The outfile file should  | + | 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, | Text-based messages in different code pages can be created using MKMSGF to display errors, help information, | ||
| Line 129: | Line 131: | ||
| Infile is the ASCII-text source file. | Infile is the ASCII-text source file. | ||
| - | + |      | |
| - | Example: | + | |
| - | + | ||
| - | MSG | + | |
| - | MSG0001I: (mm%4dd%4yy) %2%4%1%4%3 | + | |
| - | MSG0002I: (dd%4mm%4yy) %1%4%2%4%3 | + | |
| - | MSG0003I: Current date is: %0 | + | |
| - | + | ||
| - | %0 is a special argument that displays a prompt for user input. | + | |
| - | %1 - %9 are the arguments the user can use to insert text in a message. | + | |
| - | + | ||
| - |      | + | |
| @controlfile is the message definition file. | @controlfile is the message definition file. | ||
| - | Options Summary | + | ===== Options Summary  | 
| Type Meaning | Type Meaning | ||
| /P Code-page ID for the input message file. | /P Code-page ID for the input message file. | ||
| Line 150: | Line 142: | ||
| /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 197: | 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 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 | /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  | + | |
| + | ===== Control  | ||
| 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. | ||




