wmc(1) - f14

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

NAME

6       wrc - 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
15       inline 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
32              extra messages.
33
34       -h     Print an informative usage message.
35
36       -H file
37              Write headerfile to file. Default is inputfile.h.
38
39       -i     Inline messagetable(s). This option skips the generation of  all
40              .bin  files and writes all output into the .rc file. This encod‐
41              ing is parsable with wrc(1).
42
43       -o file
44              Output to file. Default is inputfile.rc.
45
46       -O format
47              Set the output format. Supported formats are rc  (the  default),
48              res, and pot.
49
50       -P directory
51              Enable the generation of resource translations based on po files
52              loaded from the specified directory. That directory must  follow
53              the  gettext  convention,  in particular in must contain one .po
54              file for each language, and a LINGUAS file listing the available
55              languages.
56
57       -u     Assume that the inputfile is in unicode.
58
59       -U     Write resource output in unicode formatted messagetable(s).
60
61       -v     Show all supported codepages and languages.
62
63       -V     Print version end exit.
64
65       -W     Enable pedantic warnings.
66

EXTENSIONS

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

AUTHORS

86       wmc was written by Bertho A. Stultiens.
87

BUGS

89       The message compiler should be able to  have  multiple  inputfiles  and
90       combine  them  into  one outputfile. This would enable the splitting of
91       languages into separate files.
92
93       Unicode detection of the input is suboptimal,  to  say  the  least.  It
94       should recognize byte-order-marks (BOM) and decide what to do.
95
96       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

AVAILABILITY

101       wmc  is  part  of  the  wine  distribution,  which is available through
102       WineHQ, the wine development headquarters, at http://www.winehq.org/.
103