Hello,
In making the Debian package lintian found some spelling errors in
both the man page and some binaries. Patch attached.
Additionally a Debian user noticed that the manpage under ClickTime
did not specify this also configures time for double clicks. The
second patch just adds a small note to this.
jaimos
Description: Add double click time info to ClickTime in manpage.
Author: Jaimos Skriletz <jaimosskril...@gmail.com>
Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567387
--- a/doc/commands/ClickTime.xml
+++ b/doc/commands/ClickTime.xml
@@ -26,4 +26,6 @@ is 150 milliseconds. Omitting the delay
<emphasis remap='B'>ClickTime</emphasis>
to the default.</para>
+<para><emphasis remap='B'>ClickTime</emphasis> also specifies the delay
+between two clicks to be interpreted as a double-click.</para>
</section>
Description: Spelling Errors.
Fixes spelling errors found by lintian.
Author: Jaimos Skriletz <jaimosskril...@gmail.com>
Last-Update: 2016-12-05
--- a/modules/FvwmCommand/FvwmCommand.c
+++ b/modules/FvwmCommand/FvwmCommand.c
@@ -532,7 +532,7 @@ void usage(void)
fprintf (stderr,
" -v print version number\n");
fprintf (stderr,
- " -w <micro sec> waiting time for the reponse from fvwm\n");
+ " -w <micro sec> waiting time for the response from fvwm\n");
fprintf (stderr, "\nDefault fifo names are ~/.%sC and ~/.%sM\n",
MYNAME, MYNAME);
fprintf (stderr, "Default waiting time is 500,000 us\n");
--- a/fvwm/events.c
+++ b/fvwm/events.c
@@ -4213,7 +4213,7 @@ void InitEventHandlerJumpTable(void)
{
/* should never happen */
fvwm_msg(ERR, "InitEventHandlerJumpTable",
- "Faild to initialize event handlers");
+ "Failed to initialize event handlers");
exit(1);
}
if (FShapesSupported)
@@ -4231,7 +4231,7 @@ void InitEventHandlerJumpTable(void)
shape_jump_table))
{
fvwm_msg(ERR, "InitEventHandlerJumpTable",
- "Faild to init Shape event handler");
+ "Failed to init Shape event handler");
}
}
--- a/fvwm/builtins.c
+++ b/fvwm/builtins.c
@@ -611,7 +611,7 @@ static char *ReadMultiPixmapDecor(char *
{
fvwm_msg(
ERR, "ReadMultiPixmapDecor",
- "Colorset shoule take one or two "
+ "Colorset should take one or two "
"positive integers as argument");
}
else
--- a/modules/FvwmScript/Instructions.c
+++ b/modules/FvwmScript/Instructions.c
@@ -794,7 +794,7 @@ static char *FuncSendMsgAndGet(int *NbAr
FILE *f;
struct timeval timeout;
- /* comunication name */
+ /* communication name */
(*NbArg)++;
com_name=CalcArg(TabArg,NbArg);
/* the command send to the receiver */
@@ -851,7 +851,7 @@ static char *FuncSendMsgAndGet(int *NbAr
if (i > IN_FIFO_NBR_OF_TRY)
{
fprintf(stderr,
- "[%s][GetMsgAndGet]: <<WARNING>> No in fifo %s for comunication %s\n",
+ "[%s][GetMsgAndGet]: <<WARNING>> No in fifo %s for communication %s\n",
ScriptName,in_fifo,com_name);
close(filedes);
err = 1;
@@ -908,7 +908,7 @@ static char *FuncSendMsgAndGet(int *NbAr
if (i > OUT_FIFO_NBR_OF_TRY)
{
fprintf(stderr,
- "[%s][GetMsgAndGet]: <<WARNING>>: No out fifo %s for comunication %s\n",
+ "[%s][GetMsgAndGet]: <<WARNING>>: No out fifo %s for communication %s\n",
ScriptName,out_fifo,com_name);
err = 1;
break;
--- a/modules/FvwmBacker/FvwmBacker.1.in
+++ b/modules/FvwmBacker/FvwmBacker.1.in
@@ -101,7 +101,7 @@ Cancels the effect of the previous optio
It it possible to replace FvwmBacker's configuration at run-time,
although it is not yet possible to remove existing configuration
lines. This is done by simply removing the old configuration from
-withing fvwm and then read a new one. This can be done in many
+within fvwm and then read a new one. This can be done in many
ways, for example by using an fvwm function or one of the modules
.BR FvwmCommand " or " FvwmConsole .
--- a/modules/FvwmButtons/FvwmButtons.1.in
+++ b/modules/FvwmButtons/FvwmButtons.1.in
@@ -988,7 +988,7 @@ inside the relief and padding.
.SH DYNAMICAL ACTIONS
A running FvwmButtons instance may receive some commands at run time.
-This is achived using the fvwm command
+This is achieved using the fvwm command
.nf
.sp
SendToModule FvwmButtons-Alias <action> <params>
--- a/modules/FvwmPerl/FvwmPerl.1
+++ b/modules/FvwmPerl/FvwmPerl.1
@@ -204,7 +204,7 @@ The following 5 options are only valid t
If \fB\-\-nolock\fR is added here, \fBModuleSynchronous\fR returns immediately. Note that \fBModule\fR returns immediately regardless of this option.
.SH "USING ALIAS"
.IX Header "USING ALIAS"
-Aliases allow to have several module invocations and work separately with all invocations, here is an example:
+Aliases allow one to have several module invocations and work separately with all invocations, here is an example:
.PP
.Vb 4
\& ModuleSynchronous FvwmPerl FvwmPerl\-JustTest
@@ -214,7 +214,7 @@ Aliases allow to have several module inv
.Ve
.SH "PREPROCESSING EXAMPLE"
.IX Header "PREPROCESSING EXAMPLE"
-One of the effective proprocessing solutions is to pass the whole fvwm configuration with embeded perl code to \*(L"FvwmPerl \-\-preprocess\*(R". An alternative approach is to write a perl script that produces fvwm commands and sends them for execution, this script may be loaded using \*(L"FvwmPerl \-\-load\*(R". There are hovewer intermediate solutions that preprocess only separate configuration lines (or alternatively, execute separate perl commands that produce fvwm commands).
+One of the effective proprocessing solutions is to pass the whole fvwm configuration with embedded perl code to \*(L"FvwmPerl \-\-preprocess\*(R". An alternative approach is to write a perl script that produces fvwm commands and sends them for execution, this script may be loaded using \*(L"FvwmPerl \-\-load\*(R". There are however intermediate solutions that preprocess only separate configuration lines (or alternatively, execute separate perl commands that produce fvwm commands).
.PP
The following code snippet adds ability of arithmetics and string scripting to certain lines that need this. To use this, you want to start FvwmPerl as your first command so that other commands may be asked to be preprosessed.
.PP
--- a/modules/FvwmProxy/FvwmProxy.1.in
+++ b/modules/FvwmProxy/FvwmProxy.1.in
@@ -61,7 +61,7 @@ If this text exceeds the width of the pr
If no Font is specified, a default is used.
.IP "*FvwmProxy: SmallFont \fIfont\fP"
-Specifies the font used for the auxillary proxy window text.
+Specifies the font used for the auxiliary proxy window text.
This usually contains the title bar string, but is omitted if it
is identical to the icon string and that text was not cropped.
The text is drawn close to the bottom of the proxy and should
--- a/doc/commands/Style.xml
+++ b/doc/commands/Style.xml
@@ -352,14 +352,14 @@ The latter is the default for
<para>The styles
<fvwmopt cmd="Style" opt="FPClickRaisesFocused"/>, <fvwmopt cmd="Style" opt="FPClickDecorRaisesFocused"/> and
<fvwmopt cmd="Style" opt="FPClickIconRaisesFocused"/>
-allow to raise the window when the interior or the decorations or
+allow one to raise the window when the interior or the decorations or
the icon of the window is clicked while the window is already
focused.</para>
<para>The styles
<fvwmopt cmd="Style" opt="FPClickRaisesUnfocused"/>, <fvwmopt cmd="Style" opt="FPClickDecorRaisesUnfocused"/> and
<fvwmopt cmd="Style" opt="FPClickIconRaisesUnfocused"/>
-allow to raise the window when the interior or the decorations or
+allow one to raise the window when the interior or the decorations or
the icon of the window is clicked while the window is not yet
focused.</para>
@@ -943,7 +943,7 @@ Style * IconBox -80 240 -1 -1, \
<para>A Style command with the IconBox option replaces any icon box
defined previously by another Style command for the same style.
-Thats why the backslash in the previous example is required.</para>
+That's why the backslash in the previous example is required.</para>
<para>Note: The geometry for the icon box command takes the additional
screen specifier "@w" in case a Xinerama setup is used. This
--- a/doc/commands/TitleStyle.xml
+++ b/doc/commands/TitleStyle.xml
@@ -46,7 +46,7 @@ argument after the
<emphasis remap='I'>Height</emphasis>
keyword. The
<emphasis remap='I'>MinHeight</emphasis>
-height is reseted by
+height is reset by
<emphasis remap='I'>Height</emphasis>
or if given with no argument.
Example:</para>
--- a/doc/commands/BugOpts.xml
+++ b/doc/commands/BugOpts.xml
@@ -135,7 +135,7 @@ option.</para>
enables transliteration during conversions from utf-8 strings. By
default fvwm will not transliterate during conversion, but will fall
back to alternate strings provided by the clients if conversion from
-utf-8 fails due to characters which have no direct correspondance in
+utf-8 fails due to characters which have no direct correspondence in
the target charecter set. Some clients however neglect to set non utf-8
properties correctly in which case this option may help.</para>
--- a/doc/fvwm/images.xml
+++ b/doc/fvwm/images.xml
@@ -60,7 +60,7 @@ might look something like this:</para>
By default, SVG images are rendered as the image creator intended
them to. But since SVG is a vector graphics format, the images can
be rendered at any chosen size and rotation, e.g. making it possible
-to use the same icon file rendered at diffrent sizes for the
+to use the same icon file rendered at different sizes for the
<fvwmref cmd="Style" opt="Icon"/> and <fvwmref cmd="Style" opt="MiniIcon"/>
styles.</para>
@@ -301,7 +301,7 @@ image.svg:@57.3
<para>
<replaceable>factor</replaceable> specifes a scaling of the actual
image (not the rendering area). Scaling it up results in a cropped
-image. Floting point values are recognized. Division by zero is
+image. Floating point values are recognized. Division by zero is
ignored. If <replaceable>factor</replaceable> is directly followed
by a '<literal>x</literal>' or a '<literal>y</literal>', the scaling
is horizontal or vertical respectively. Otherwise the scaling is
--- a/modules/FvwmScript/Widgets/Widget.c
+++ b/modules/FvwmScript/Widgets/Widget.c
@@ -300,7 +300,7 @@ void ChooseFunction(struct XObj *xobj,ch
}
else
{
- fprintf(stderr,"Item %s unknow\n",type);
+ fprintf(stderr,"Item %s unknown\n",type);
exit(1);
}
}
