1WMC(1)                      Wine Developers Manual                      WMC(1)
2
3
4

NAME

6       wmc - Wine Message Compiler
7

SYNOPSIS

9       wmc [options] [inputfile]
10

DESCRIPTION

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
17       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

OPTIONS

24       -B x   Set output byte-order x={n[ative], l[ittle], b[ig]}. Default  is
25              n[ative].
26
27       -c     Set 'custom-bit' in message-code values.
28
29       -d     NON-FUNCTIONAL; Use decimal values in output
30
31       -D     Set  debug flag. This results is a parser trace and a lot of ex‐
32              tra messages.
33
34       -h, --help
35              Print an informative usage message and exits.
36
37       -H file
38              Write headerfile to file. Default is inputfile.h.
39
40       -i     Inline messagetable(s). This option skips the generation of  all
41              .bin  files and writes all output into the .rc file. This encod‐
42              ing is parsable with wrc(1).
43
44       --nls-dir=directory
45              Specify the directory to search for the NLS files containing the
46              codepage mapping tables.
47
48       -o, --output=file
49              Output to file. Default is inputfile.rc.
50
51       -O, --output-format=format
52              Set  the  output format. Supported formats are rc (the default),
53              res, and pot.
54
55       -P, --po-dir=directory
56              Enable the generation of resource translations based on po files
57              loaded  from the specified directory. That directory must follow
58              the gettext convention, in particular in must  contain  one  .po
59              file for each language, and a LINGUAS file listing the available
60              languages.
61
62       -u     Assume that the input file is in Unicode  or  UTF-8  format  and
63              skip codepage conversions.
64
65       -v     Show all supported codepages and languages.
66
67       -V, --version
68              Print version end exit.
69
70       -W, --pedantic
71              Enable pedantic warnings.
72

EXTENSIONS

74       The  original  syntax  is  extended to support codepages more smoothly.
75       Normally, codepages are based on the DOS  codepage  from  the  language
76       setting. The original syntax only allows the destination codepage to be
77       set. However, this is not enough for non-DOS systems which do  not  use
78       unicode source-files.
79
80       A  new  keyword  Codepages  is  introduced to set both input and output
81       codepages to anything one wants for each language. The syntax is  simi‐
82       lar to the other constructs:
83
84       Codepages '=' '(' language '=' cpin ':' cpout ... ')'
85
86       The language is the numerical language-ID or the alias set with Langua‐
87       geNames. The input codepage cpin and output codepage cpout are the  nu‐
88       merical codepage IDs. There can be multiple mappings within the defini‐
89       tion and the definition may occur more than once.
90

AUTHORS

92       wmc was written by Bertho A. Stultiens.
93

BUGS

95       The message compiler should be able to have multiple  input  files  and
96       combine  them  into one output file. This would enable the splitting of
97       languages into separate files.
98
99       Decimal output is completely lacking. Don't know whether it  should  be
100       implemented because it is a, well, non-informative format change. It is
101       recognized on the commandline for some form of compatibility.
102
103       Bugs can be reported on the Wine bug tracker https://bugs.winehq.org⟩.
104

AVAILABILITY

106       wmc is part of  the  Wine  distribution,  which  is  available  through
107       WineHQ, the Wine development headquarters https://www.winehq.org/⟩.
108

SEE ALSO

110       wine(1), wrc(1),
111       Wine documentation and support https://www.winehq.org/help⟩.
112
113
114
115Wine 6.10                        October 2005                           WMC(1)
Impressum