2 .TH WMC 1 "October 2005" "@PACKAGE_STRING@" "Wine Developers Manual"
4 wrc \- Wine Message Compiler
6 .BI "wmc " "[options] " "[inputfile]"
11 into FormatMessage[AW] compatible format encapsulated in a resourcescript
14 outputs the data either in a standard \fB.bin\fR formatted binary
15 file, or can generated inline resource data.
18 takes only one \fBinputfile\fR as argument (see \fBBUGS\fR). The
19 \fBinputfile\fR normally has extension \fB.mc\fR. The messages are read from
20 standard input if no inputfile is given. If the outputfile is not specified
21 with \fI-o\fR, then \fBwmc\fR will write the output to \fBinputfile.{rc,h}\fR.
22 The outputfile is named \fBwmc.tab.{rc,h}\fR if no inputfile was given.
26 Set output byte-order x={n[ative], l[ittle], b[ig]}. Default is n[ative].
29 Set 'custom-bit' in message-code values.
32 NON-FUNCTIONAL; Use decimal values in output
35 Set debug flag. This results is a parser trace and a lot of extra messages.
38 Print an informative usage message.
41 Write headerfile to \fIfile\fR. Default is \fIinputfile.h\fR.
44 Inline messagetable(s). This option skips the generation of all \fI.bin\fR files
45 and writes all output into the \fI.rc\fR file. This encoding is parsable with
49 Output to \fIfile\fR. Default is \fIinputfile.rc\fR.
52 Set the output format. Supported formats are \fBrc\fR (the default),
53 \fBres\fR, and \fBpot\fR.
56 Enable the generation of resource translations based on po files
57 loaded from the specified directory. That directory must follow the
58 gettext convention, in particular in must contain one .po file for
59 each language, and a LINGUAS file listing the available languages.
62 Assume that the inputfile is in unicode.
65 Write resource output in unicode formatted messagetable(s).
68 Show all supported codepages and languages.
71 Print version end exit.
74 Enable pedantic warnings.
76 The original syntax is extended to support codepages more smoothly. Normally,
77 codepages are based on the DOS\-codepage from the language setting. The
78 original syntax only allows the destination codepage to be set. However, this
79 is not enough for non\-DOS systems which do not use unicode source-files.
81 A new keyword \fICodepages\fR is introduced to set both input and output
82 codepages to anything one wants for each language. The syntax is similar to
85 Codepages '=' '(' language '=' cpin ':' cpout ... ')'
87 The \fIlanguage\fR is the numerical language\-ID or the alias set with
88 LanguageNames. The input\-codepage \fIcpin\fR and output\-codepage
89 \fIcpout\fR are the numerical codepage\-IDs. There can be multiple mapping
90 within the definition and the definition may occur more than once.
93 was written by Bertho A. Stultiens.
95 The message compiler should be able to have multiple inputfiles and combine
96 them into one outputfile. This would enable the splitting of languages into
99 Unicode detection of the input is suboptimal, to say the least. It should
100 recognize byte\-order\-marks (BOM) and decide what to do.
102 Decimal output is completely lacking. Don't know whether it should be
103 implemented because it is a, well, non-informative format change. It is
104 recognized on the commandline for some form of compatibility.
107 is part of the wine distribution, which is available through
110 development headquarters, at
111 .I http://www.winehq.org/.