Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Last revisionBoth sides next revision | ||
en:docs:tk:tools:mkmsgf [2024/01/21 11:51] – prokushev | en:docs:tk:tools:mkmsgf [2024/03/26 13:06] – prokushev | ||
---|---|---|---|
Line 89: | Line 89: | ||
RMS | RMS | ||
ROM | ROM | ||
- | RUS | + | RUS |
SHL | SHL | ||
SHC | SHC | ||
Line 103: | Line 103: | ||
For a complete list of code pages and country codes, see the code page table under [[https:// | 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 115: | Line 115: | ||
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 132: | Line 133: | ||
@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 186: | Line 188: | ||
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. | 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. | ||
+ | |||
Control Files | Control Files | ||