SYNOPSIS

DESCRIPTION

         compiles messages from  into FormatMessage[AW] compatible
       format encapsulated in a resourcescript format.   outputs  the  data
       either  in  a  standard    formatted  binary file, or can generated
       inline resource data.
        takes only one  as argument (see ). The  nor-
       mally  has  extension . The messages are read from standard input if
       no inputfile is given. If the outputfile is not specified with , then
        will write the output to .  The outputfile is named
        if no inputfile was given.

OPTIONS

           Set output byte-order x={n[ative], l[ittle], b[ig]}. Default  is
              n[ative].
            Set 'custom-bit' in message-code values.
            NON-FUNCTIONAL; Use decimal values in output
            Set  debug  flag.  This  results  is a parser trace and a lot of
              extra messages.
            Print an informative usage message.

              Write headerfile to . Default is .
            Inline messagetable(s). This option skips the generation of  all
                files and writes all output into the  file. This encod-
              ing is parsable with .

              Output to . Default is .
            Assume that the inputfile is in unicode.
            Write resource output in unicode formatted messagetable(s).
            Show all supported codepages and languages.
            Print version end exit.
            Enable pedantic warnings.

EXTENSIONS

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

AUTHORS

        was written by Bertho A. Stultiens.

BUGS

       The  message  compiler  should  be able to have multiple inputfiles and
       combine them into one outputfile. This would enable  the  splitting  of
       languages into separate files.
       Unicode  detection  of  the  input  is suboptimal, to say the least. It
       should recognize byte-order-marks (BOM) and decide what to do.
       Decimal output is completely lacking. Don't know whether it  should  be
       implemented because it is a, well, non-informative format change. It is
       recognized on the commandline for some form of compatibility.

AVAILABILITY

        is part of  the  wine  distribution,  which  is  available  through
       WineHQ, the  development headquarters, at

SEE ALSO

       ,
Wine 1.1.9                       October 2005