1WMC(1) Wine Developers Manual WMC(1)
2
6 wmc - Wine Message Compiler
7
9 wmc [options] [inputfile]
10
12 wmc compiles messages from inputfile into FormatMessage[AW] compatible
13 format encapsulated in a resourcescript format. wmc outputs the data
14 either in a standard .bin formatted binary file, or can generated in‐
15 line resource data.
16 wmc takes only one inputfile as argument (see BUGS). The inputfile nor‐
18 mally has extension .mc. The messages are read from standard input if
19 no inputfile is given. If the outputfile is not specified with -o, then
20 wmc will write the output to inputfile.{rc,h}. The outputfile is named
21 wmc.tab.{rc,h} if no inputfile was given.
22
24 -c Set 'custom-bit' in message-code values.
25 -d NON-FUNCTIONAL; Use decimal values in output
27 -D Set debug flag. This results is a parser trace and a lot of ex‐
29 tra messages.
30 -h, --help
32 Print an informative usage message and exits.
33 -H file
35 Write headerfile to file. Default is inputfile.h.
36 -i Inline messagetable(s). This option skips the generation of all
38 .bin files and writes all output into the .rc file. This encod‐
39 ing is parsable with wrc(1).
40 --nls-dir=directory
42 Specify the directory to search for the NLS files containing the
43 codepage mapping tables.
44 -o, --output=file
46 Output to file. Default is inputfile.rc.
47 -O, --output-format=format
49 Set the output format. Supported formats are rc (the default),
50 res, and pot.
51 -P, --po-dir=directory
53 Enable the generation of resource translations based on po files
54 loaded from the specified directory. That directory must follow
55 the gettext convention, in particular in must contain one .po
56 file for each language, and a LINGUAS file listing the available
57 languages.
58 -u Assume that the input file is in Unicode or UTF-8 format and
60 skip codepage conversions.
61 -v Show all supported codepages and languages.
63 -V, --version
65 Print version end exit.
66 -W, --pedantic
68 Enable pedantic warnings.
69
71 The original syntax is extended to support codepages more smoothly.
72 Normally, codepages are based on the DOS codepage from the language
73 setting. The original syntax only allows the destination codepage to be
74 set. However, this is not enough for non-DOS systems which do not use
75 unicode source-files.
76 A new keyword Codepages is introduced to set both input and output
78 codepages to anything one wants for each language. The syntax is simi‐
79 lar to the other constructs:
80 Codepages '=' '(' language '=' cpin ':' cpout ... ')'
82 The language is the numerical language-ID or the alias set with Langua‐
84 geNames. The input codepage cpin and output codepage cpout are the nu‐
85 merical codepage IDs. There can be multiple mappings within the defini‐
86 tion and the definition may occur more than once.
87
89 wmc was written by Bertho A. Stultiens.
90
92 The message compiler should be able to have multiple input files and
93 combine them into one output file. This would enable the splitting of
94 languages into separate files.
95 Decimal output is completely lacking. Don't know whether it should be
97 implemented because it is a, well, non-informative format change. It is
98 recognized on the commandline for some form of compatibility.
99 Bugs can be reported on the Wine bug tracker ⟨https://bugs.winehq.org⟩.
101
103 wmc is part of the Wine distribution, which is available through
104 WineHQ, the Wine development headquarters ⟨https://www.winehq.org/⟩.
105
107 wine(1), wrc(1),
108 Wine documentation and support ⟨https://www.winehq.org/help⟩.
109Wine 8.19 October 2005 WMC(1)