Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

mkerrlst(1) [bsd man page]

MKERRLST(1)						      General Commands Manual						       MKERRLST(1)

mkerrlst - create system error file SYNOPSIS
mkerrlst [ -i inputfile ] [ -o outputfile ] DESCRIPTION
Mkerrlst(1) creates error message files in the format described by syserrlst(5). With no arguments mkerrlst creates the file /etc/syserrlst from the internal array sys_errlist. Give just the -o option mkerrlst will create the file outputfile from the internal array sys_errlist. Given just the -i option mkerrlst will create the file /etc/syserrlst from the input file inputfile. Given both -i and -o options mkerrlst will create the error message file outputfile from the strings contained in inputfile. NOTE: error messages are numbered from 0. If the error 0 does not have a message associated with it the first string in inputfile must still be present. RETURN VALUE
mkerrlst exits with status of 0 if no errors are encountered. If errors do occur an error message is printed on stderr and the exit status is 1. ERRORS
mkerrlst(1) can encounter any of the errors for the open(2), lseek(2), read(2), or write(2) system calls. SEE ALSO
syserrlst(3) syserrlst(5) HISTORY
mkerrlst(1), first appeared in 2.11BSD. BUGS
Error messages can be a maximum of 80 characters. 3rd Berkeley Distribution March 14, 1996 MKERRLST(1)

Check Out this Related Man Page

WMC(1)							      Wine Developers Manual							    WMC(1)

wrc - Wine Message Compiler SYNOPSIS
wmc [options] [inputfile] DESCRIPTION
wmc compiles messages from inputfile into FormatMessage[AW] compatible format encapsulated in a resourcescript format. wmc outputs the data either in a standard .bin formatted binary file, or can generated inline resource data. wmc takes only one inputfile as argument (see BUGS). The inputfile normally has extension .mc. The messages are read from standard input if no inputfile is given. If the outputfile is not specified with -o, then wmc will write the output to inputfile.{rc,h}. The outputfile is named{rc,h} if no inputfile was given. OPTIONS
-B x Set output byte-order x={n[ative], l[ittle], b[ig]}. Default is n[ative]. -c Set 'custom-bit' in message-code values. -d NON-FUNCTIONAL; Use decimal values in output -D Set debug flag. This results is a parser trace and a lot of extra messages. -h Print an informative usage message. -H file Write headerfile to file. Default is inputfile.h. -i Inline messagetable(s). This option skips the generation of all .bin files and writes all output into the .rc file. This encoding is parsable with wrc(1). -o file Output to file. Default is inputfile.rc. -u Assume that the inputfile is in unicode. -U Write resource output in unicode formatted messagetable(s). -v Show all supported codepages and languages. -V Print version end exit. -W 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 Codepages is introduced to set both input and output codepages to anything one wants for each language. The syntax is similar to the other constructs: Codepages '=' '(' language '=' cpin ':' cpout ... ')' The language is the numerical language-ID or the alias set with LanguageNames. The input-codepage cpin and output-codepage cpout are the numerical codepage-IDs. There can be multiple mapping within the definition and the definition may occur more than once. AUTHORS
wmc 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
wmc is part of the wine distribution, which is available through WineHQ, the wine development headquarters, at SEE ALSO
wine(1), wrc(1) Wine 1.2-rc6 October 2005 WMC(1)
Man Page