Spelling and grammar fixes in help (#2603)
* Edit Help array to make it match others below. This should not affect the results * Misc. grammer and spelling fixes along with removing some duplicated words. This should not affect compilation. * More grammer and spelling errors * Replace Javascript with ZoneMinder because it did not make sense there. * More spelling and grammar edits
This commit is contained in:
parent
22c5d46c65
commit
74d9f4f1aa
|
@ -198,7 +198,7 @@ our @options = (
|
|||
default => 'high',
|
||||
description => 'Default setting for bandwidth profile used by web interface',
|
||||
help => q`The classic skin for ZoneMinder has different
|
||||
profiles to use for low medium or high bandwidth connections.
|
||||
profiles to use for low, medium, or high bandwidth connections.
|
||||
`,
|
||||
type => $types{string},
|
||||
category => 'system',
|
||||
|
@ -547,7 +547,7 @@ our @options = (
|
|||
higher quality setting than the ordinary file setting. If set
|
||||
to a lower value then it is ignored. Thus leaving it at the
|
||||
default of 0 effectively means to use the regular file quality
|
||||
setting for all saved images. This is to prevent acccidentally
|
||||
setting for all saved images. This is to prevent accidentally
|
||||
saving important images at a worse quality setting.
|
||||
`,
|
||||
type => $types{integer},
|
||||
|
@ -1065,12 +1065,12 @@ our @options = (
|
|||
default => '0',
|
||||
description => 'Save logging output to the system log',
|
||||
help => q`
|
||||
ZoneMinder logging is now more more integrated between
|
||||
ZoneMinder logging is now more integrated between
|
||||
components and allows you to specify the destination for
|
||||
logging output and the individual levels for each. This option
|
||||
lets you control the level of logging output that goes to the
|
||||
system log. ZoneMinder binaries have always logged to the
|
||||
system log but now scripts and web logging is also included. To
|
||||
system log but script and web logging is now included. To
|
||||
preserve the previous behaviour you should ensure this value is
|
||||
set to Info or Warning. This option controls the maximum level
|
||||
of logging that will be written, so Info includes Warnings and
|
||||
|
@ -1092,7 +1092,7 @@ our @options = (
|
|||
default => '-5',
|
||||
description => 'Save logging output to component files',
|
||||
help => q`
|
||||
ZoneMinder logging is now more more integrated between
|
||||
ZoneMinder logging is now more integrated between
|
||||
components and allows you to specify the destination for
|
||||
logging output and the individual levels for each. This option
|
||||
lets you control the level of logging output that goes to
|
||||
|
@ -1122,7 +1122,7 @@ our @options = (
|
|||
default => '-5',
|
||||
description => 'Save logging output to the weblog',
|
||||
help => q`
|
||||
ZoneMinder logging is now more more integrated between
|
||||
ZoneMinder logging is now more integrated between
|
||||
components and allows you to specify the destination for
|
||||
logging output and the individual levels for each. This option
|
||||
lets you control the level of logging output from the web
|
||||
|
@ -1149,7 +1149,7 @@ our @options = (
|
|||
default => '0',
|
||||
description => 'Save logging output to the database',
|
||||
help => q`
|
||||
ZoneMinder logging is now more more integrated between
|
||||
ZoneMinder logging is now more integrated between
|
||||
components and allows you to specify the destination for
|
||||
logging output and the individual levels for each. This option
|
||||
lets you control the level of logging output that is written to
|
||||
|
@ -1219,7 +1219,7 @@ our @options = (
|
|||
ZoneMinder components usually support debug logging available
|
||||
to help with diagnosing problems. Binary components have
|
||||
several levels of debug whereas more other components have only
|
||||
one. Normally this is disabled to minimise performance
|
||||
one. Normally this is disabled to minimize performance
|
||||
penalties and avoid filling logs too quickly. This option lets
|
||||
you switch on other options that allow you to configure
|
||||
additional debug information to be output. Components will pick
|
||||
|
@ -1538,7 +1538,8 @@ our @options = (
|
|||
name => 'ZM_WEB_EVENT_DISK_SPACE',
|
||||
default => 'no',
|
||||
description => 'Whether to show disk space used by each event.',
|
||||
help => q`Adds another column to the listing of events
|
||||
help => q`
|
||||
Adds another column to the listing of events
|
||||
showing the disk space used by the event. This will impart a small
|
||||
overhead as it will call du on the event directory. In practice
|
||||
this overhead is fairly small but may be noticeable on IO-constrained
|
||||
|
@ -1555,7 +1556,7 @@ our @options = (
|
|||
Traditionally the main ZoneMinder web console window has
|
||||
resized itself to shrink to a size small enough to list only
|
||||
the monitors that are actually present. This is intended to
|
||||
make the window more unobtrusize but may not be to everyones
|
||||
make the window more unobtrusize but may not be to everyone's
|
||||
tastes, especially if opened in a tab in browsers which support
|
||||
this kind if layout. Switch this option off to have the console
|
||||
window size left to the users preference
|
||||
|
@ -2105,7 +2106,7 @@ our @options = (
|
|||
a remote ftp server. This option indicates that ftp transfers
|
||||
should be done in passive mode. This uses a single connection
|
||||
for all ftp activity and, whilst slower than active transfers,
|
||||
is more robust and likely to work from behind filewalls. This
|
||||
is more robust and likely to work from behind firewalls. This
|
||||
option is ignored for SFTP transfers.
|
||||
`,
|
||||
requires => [ { name => 'ZM_OPT_UPLOAD', value => 'yes' } ],
|
||||
|
@ -2631,7 +2632,7 @@ our @options = (
|
|||
help => q`
|
||||
As event images are captured they are stored to the filesystem
|
||||
with a numerical index. By default this index has three digits
|
||||
so the numbers start 001, 002 etc. This works works for most
|
||||
so the numbers start 001, 002 etc. This works for most
|
||||
scenarios as events with more than 999 frames are rarely
|
||||
captured. However if you have extremely long events and use
|
||||
external applications then you may wish to increase this to
|
||||
|
@ -2728,7 +2729,7 @@ our @options = (
|
|||
it to the ZoneMinder development team. This data will be used to
|
||||
determine things like who and where our customers are, how big their
|
||||
systems are, the underlying hardware and operating system, etc.
|
||||
This is being done for the sole purpoase of creating a better
|
||||
This is being done for the sole purpose of creating a better
|
||||
product for our target audience. This script is intended to be
|
||||
completely transparent to the end user, and can be disabled from
|
||||
the web console under Options. For more details on what information
|
||||
|
@ -2752,7 +2753,7 @@ our @options = (
|
|||
{
|
||||
name => 'ZM_TELEMETRY_LAST_UPLOAD',
|
||||
default => '',
|
||||
description => 'When the last ZoneMinder telemetry upload ocurred',
|
||||
description => 'When the last ZoneMinder telemetry upload occurred',
|
||||
help => '',
|
||||
type => $types{integer},
|
||||
readonly => 1,
|
||||
|
@ -2810,7 +2811,7 @@ our @options = (
|
|||
default => 'javascript',
|
||||
description => 'What method windows should use to refresh themselves',
|
||||
help => q`
|
||||
Many windows in Javascript need to refresh themselves to keep
|
||||
Many windows in ZoneMinder need to refresh themselves to keep
|
||||
their information current. This option determines what method
|
||||
they should use to do this. Choosing 'javascript' means that
|
||||
each window will have a short JavaScript statement in with a
|
||||
|
@ -2944,7 +2945,7 @@ our @options = (
|
|||
some indication of the type of content. However this is not a
|
||||
standard part of HTML. The official method is to use OBJECT
|
||||
tags which are able to give more information allowing the
|
||||
correct media viewers etc to be loaded. However these are less
|
||||
correct media viewers etc. to be loaded. However these are less
|
||||
widely supported and content may be specifically tailored to a
|
||||
particular platform or player. This option controls whether
|
||||
media content is enclosed in EMBED tags only or whether, where
|
||||
|
@ -2968,7 +2969,7 @@ our @options = (
|
|||
browsers. When this condition occurs, ZoneMinder will write a
|
||||
warning to the log file. To get around this, one can install a browser
|
||||
plugin or extension to ignore X-Frame headers, and then the page will
|
||||
display properly. Once the plugin or extenstion has ben installed,
|
||||
display properly. Once the plugin or extension has ben installed,
|
||||
the end user may choose to turn this warning off.
|
||||
`,
|
||||
type => $types{boolean},
|
||||
|
@ -3082,7 +3083,7 @@ our @options = (
|
|||
description => 'How often (in seconds) the event listing is refreshed in the watch window',
|
||||
help => q`
|
||||
The monitor window is actually made from several frames. The
|
||||
lower framme contains a listing of the last few events for easy
|
||||
lower frame contains a listing of the last few events for easy
|
||||
access. This option determines how often this is refreshed.
|
||||
`,
|
||||
type => $types{integer},
|
||||
|
@ -3212,12 +3213,12 @@ our @options = (
|
|||
{
|
||||
name => 'ZM_WEB_H_SCALE_THUMBS',
|
||||
default => 'no',
|
||||
description => 'Scale thumbnails in events, bandwidth versus cpu in rescaling',
|
||||
description => 'Scale thumbnails in events, bandwidth versus CPU in rescaling',
|
||||
help => q`
|
||||
If unset, this option sends the whole image to the browser
|
||||
which resizes it in the window. If set the image is scaled down
|
||||
on the server before sending a reduced size image to the
|
||||
browser to conserve bandwidth at the cost of cpu on the server.
|
||||
browser to conserve bandwidth at the cost of CPU on the server.
|
||||
Note that ZM can only perform the resizing if the appropriate
|
||||
PHP graphics functionality is installed. This is usually
|
||||
available in the php-gd package.
|
||||
|
@ -3251,7 +3252,7 @@ our @options = (
|
|||
help => q`
|
||||
When viewing events an event navigation panel and progress bar
|
||||
is shown below the event itself. This allows you to jump to
|
||||
specific points in the event, but can can also dynamically
|
||||
specific points in the event, but can also dynamically
|
||||
update to display the current progress of the event replay
|
||||
itself. This progress is calculated from the actual event
|
||||
duration and is not directly linked to the replay itself, so on
|
||||
|
@ -3355,7 +3356,7 @@ our @options = (
|
|||
description => 'How often (in seconds) the event listing is refreshed in the watch window',
|
||||
help => q`
|
||||
The monitor window is actually made from several frames. The
|
||||
lower framme contains a listing of the last few events for easy
|
||||
lower frame contains a listing of the last few events for easy
|
||||
access. This option determines how often this is refreshed.
|
||||
`,
|
||||
type => $types{integer},
|
||||
|
@ -3485,12 +3486,12 @@ our @options = (
|
|||
{
|
||||
name => 'ZM_WEB_M_SCALE_THUMBS',
|
||||
default => 'yes',
|
||||
description => 'Scale thumbnails in events, bandwidth versus cpu in rescaling',
|
||||
description => 'Scale thumbnails in events, bandwidth versus CPU in rescaling',
|
||||
help => q`
|
||||
If unset, this option sends the whole image to the browser
|
||||
which resizes it in the window. If set the image is scaled down
|
||||
on the server before sending a reduced size image to the
|
||||
browser to conserve bandwidth at the cost of cpu on the server.
|
||||
browser to conserve bandwidth at the cost of CPU on the server.
|
||||
Note that ZM can only perform the resizing if the appropriate
|
||||
PHP graphics functionality is installed. This is usually
|
||||
available in the php-gd package.
|
||||
|
@ -3524,7 +3525,7 @@ our @options = (
|
|||
help => q`
|
||||
When viewing events an event navigation panel and progress bar
|
||||
is shown below the event itself. This allows you to jump to
|
||||
specific points in the event, but can can also dynamically
|
||||
specific points in the event, but can also dynamically
|
||||
update to display the current progress of the event replay
|
||||
itself. This progress is calculated from the actual event
|
||||
duration and is not directly linked to the replay itself, so on
|
||||
|
@ -3628,7 +3629,7 @@ our @options = (
|
|||
description => 'How often (in seconds) the event listing is refreshed in the watch window',
|
||||
help => q`
|
||||
The monitor window is actually made from several frames. The
|
||||
lower framme contains a listing of the last few events for easy
|
||||
lower frame contains a listing of the last few events for easy
|
||||
access. This option determines how often this is refreshed.
|
||||
`,
|
||||
type => $types{integer},
|
||||
|
@ -3757,12 +3758,12 @@ our @options = (
|
|||
{
|
||||
name => 'ZM_WEB_L_SCALE_THUMBS',
|
||||
default => 'yes',
|
||||
description => 'Scale thumbnails in events, bandwidth versus cpu in rescaling',
|
||||
description => 'Scale thumbnails in events, bandwidth versus CPU in rescaling',
|
||||
help => q`
|
||||
If unset, this option sends the whole image to the browser
|
||||
which resizes it in the window. If set the image is scaled down
|
||||
on the server before sending a reduced size image to the
|
||||
browser to conserve bandwidth at the cost of cpu on the server.
|
||||
browser to conserve bandwidth at the cost of CPU on the server.
|
||||
Note that ZM can only perform the resizing if the appropriate
|
||||
PHP graphics functionality is installed. This is usually
|
||||
available in the php-gd package.
|
||||
|
@ -3796,7 +3797,7 @@ our @options = (
|
|||
help => q`
|
||||
When viewing events an event navigation panel and progress bar
|
||||
is shown below the event itself. This allows you to jump to
|
||||
specific points in the event, but can can also dynamically
|
||||
specific points in the event, but can also dynamically
|
||||
update to display the current progress of the event replay
|
||||
itself. This progress is calculated from the actual event
|
||||
duration and is not directly linked to the replay itself, so on
|
||||
|
@ -3988,7 +3989,7 @@ saveConfigToDB();
|
|||
|
||||
The ZoneMinder:ConfigData module contains the master definition of the
|
||||
ZoneMinder configuration options as well as helper methods. This module is
|
||||
intended for specialist confguration management and would not normally be
|
||||
intended for specialist configuration management and would not normally be
|
||||
used by end users.
|
||||
|
||||
The configuration held in this module, which was previously in zmconfig.pl,
|
||||
|
|
Loading…
Reference in New Issue