wmc: Fix manpage formatting.
This commit is contained in:
parent
f753720eb5
commit
3864fd8d37
|
@ -1,9 +1,9 @@
|
||||||
.\" -*- nroff -*-
|
|
||||||
.TH WMC 1 "October 2005" "@PACKAGE_STRING@" "Wine Developers Manual"
|
.TH WMC 1 "October 2005" "@PACKAGE_STRING@" "Wine Developers Manual"
|
||||||
.SH NAME
|
.SH NAME
|
||||||
wmc \- Wine Message Compiler
|
wmc \- Wine Message Compiler
|
||||||
.SH SYNOPSIS
|
.SH SYNOPSIS
|
||||||
.BI "wmc " "[options] " "[inputfile]"
|
.B wmc
|
||||||
|
.RI [ options ]\ [ inputfile ]
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
.B wmc
|
.B wmc
|
||||||
compiles messages from
|
compiles messages from
|
||||||
|
@ -11,15 +11,15 @@ compiles messages from
|
||||||
into FormatMessage[AW] compatible format encapsulated in a resourcescript
|
into FormatMessage[AW] compatible format encapsulated in a resourcescript
|
||||||
format.
|
format.
|
||||||
.B wmc
|
.B wmc
|
||||||
outputs the data either in a standard \fB.bin\fR formatted binary
|
outputs the data either in a standard \fI.bin\fR formatted binary
|
||||||
file, or can generated inline resource data.
|
file, or can generated inline resource data.
|
||||||
.PP
|
.PP
|
||||||
.B wmc
|
.B wmc
|
||||||
takes only one \fBinputfile\fR as argument (see \fBBUGS\fR). The
|
takes only one \fIinputfile\fR as argument (see \fBBUGS\fR). The
|
||||||
\fBinputfile\fR normally has extension \fB.mc\fR. The messages are read from
|
\fIinputfile\fR normally has extension \fI.mc\fR. The messages are read from
|
||||||
standard input if no inputfile is given. If the outputfile is not specified
|
standard input if no inputfile is given. If the outputfile is not specified
|
||||||
with \fI-o\fR, then \fBwmc\fR will write the output to \fBinputfile.{rc,h}\fR.
|
with \fB-o\fR, then \fBwmc\fR will write the output to \fIinputfile.{rc,h}\fR.
|
||||||
The outputfile is named \fBwmc.tab.{rc,h}\fR if no inputfile was given.
|
The outputfile is named \fIwmc.tab.{rc,h}\fR if no inputfile was given.
|
||||||
.SH OPTIONS
|
.SH OPTIONS
|
||||||
.TP
|
.TP
|
||||||
.BI \-B\ x
|
.BI \-B\ x
|
||||||
|
@ -55,7 +55,7 @@ Set the output format. Supported formats are \fBrc\fR (the default),
|
||||||
.BI \-P\ directory
|
.BI \-P\ directory
|
||||||
Enable the generation of resource translations based on po files
|
Enable the generation of resource translations based on po files
|
||||||
loaded from the specified directory. That directory must follow the
|
loaded from the specified directory. That directory must follow the
|
||||||
gettext convention, in particular in must contain one .po file for
|
gettext convention, in particular in must contain one \fI.po\fR file for
|
||||||
each language, and a LINGUAS file listing the available languages.
|
each language, and a LINGUAS file listing the available languages.
|
||||||
.TP
|
.TP
|
||||||
.B \-u
|
.B \-u
|
||||||
|
@ -74,19 +74,19 @@ Print version end exit.
|
||||||
Enable pedantic warnings.
|
Enable pedantic warnings.
|
||||||
.SH EXTENSIONS
|
.SH EXTENSIONS
|
||||||
The original syntax is extended to support codepages more smoothly. Normally,
|
The original syntax is extended to support codepages more smoothly. Normally,
|
||||||
codepages are based on the DOS\-codepage from the language setting. The
|
codepages are based on the DOS codepage from the language setting. The
|
||||||
original syntax only allows the destination codepage to be set. However, this
|
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.
|
is not enough for non\-DOS systems which do not use unicode source-files.
|
||||||
.PP
|
.PP
|
||||||
A new keyword \fICodepages\fR is introduced to set both input and output
|
A new keyword \fBCodepages\fR is introduced to set both input and output
|
||||||
codepages to anything one wants for each language. The syntax is similar to
|
codepages to anything one wants for each language. The syntax is similar to
|
||||||
the other constructs:
|
the other constructs:
|
||||||
.PP
|
.PP
|
||||||
Codepages '=' '(' language '=' cpin ':' cpout ... ')'
|
Codepages '=' '(' language '=' cpin ':' cpout ... ')'
|
||||||
.PP
|
.PP
|
||||||
The \fIlanguage\fR is the numerical language\-ID or the alias set with
|
The \fIlanguage\fR is the numerical language\-ID or the alias set with
|
||||||
LanguageNames. The input\-codepage \fIcpin\fR and output\-codepage
|
LanguageNames. The input codepage \fIcpin\fR and output codepage
|
||||||
\fIcpout\fR are the numerical codepage\-IDs. There can be multiple mapping
|
\fIcpout\fR are the numerical codepage IDs. There can be multiple mappings
|
||||||
within the definition and the definition may occur more than once.
|
within the definition and the definition may occur more than once.
|
||||||
.SH AUTHORS
|
.SH AUTHORS
|
||||||
.B wmc
|
.B wmc
|
||||||
|
@ -97,7 +97,7 @@ them into one outputfile. This would enable the splitting of languages into
|
||||||
separate files.
|
separate files.
|
||||||
.PP
|
.PP
|
||||||
Unicode detection of the input is suboptimal, to say the least. It should
|
Unicode detection of the input is suboptimal, to say the least. It should
|
||||||
recognize byte\-order\-marks (BOM) and decide what to do.
|
recognize byte order marks (BOM) and decide what to do.
|
||||||
.PP
|
.PP
|
||||||
Decimal output is completely lacking. Don't know whether it should be
|
Decimal output is completely lacking. Don't know whether it should be
|
||||||
implemented because it is a, well, non-informative format change. It is
|
implemented because it is a, well, non-informative format change. It is
|
||||||
|
|
Loading…
Reference in New Issue