From 49b822a14dbc9f8c05060f419f2d672fe2fce730 Mon Sep 17 00:00:00 2001 From: Klaus Schmidinger Date: Sat, 18 Dec 2004 12:42:41 +0100 Subject: =?UTF-8?q?Escaped=20the=20'-'=20and=20'=C3=B6'=20characters=20in?= =?UTF-8?q?=20the=20man=20pages?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- vdr.5 | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) (limited to 'vdr.5') diff --git a/vdr.5 b/vdr.5 index 311094ff..f1ce3c22 100644 --- a/vdr.5 +++ b/vdr.5 @@ -8,9 +8,9 @@ .\" License as specified in the file COPYING that comes with the .\" vdr distribution. .\" -.\" $Id: vdr.5 1.29 2004/10/31 12:13:43 kls Exp $ +.\" $Id: vdr.5 1.30 2004/12/18 12:40:47 kls Exp $ .\" -.TH vdr 5 "31 Oct 2004" "1.3.15" "Video Disk Recorder Files" +.TH vdr 5 "19 Dec 2004" "1.3.18" "Video Disk Recorder Files" .SH NAME vdr file formats - the Video Disk Recorder Files .SH DESCRIPTION @@ -174,12 +174,12 @@ NID, TID and SID are all equal). A particular channel can be uniquely identified by its \fBchannel\ ID\fR, which is a string that looks like this: -\fBS19.2E-1-1089-12003-0\fR +\fBS19.2E\-1\-1089\-12003\-0\fR The components of this string are the \fBSource\fR (S19.2E), \fBNID\fR (1), \fBTID\fR (1089), \fBSID\fR (12003) and \fBRID\fR (0) as defined above. The last part can be omitted if it is \fB0\fR, -so the above example could also be written as S19.2E-1-1089-12003). +so the above example could also be written as S19.2E\-1\-1089\-12003). .br The \fBchannel\ ID\fR is used in the \fItimers.conf\fR and \fIepg.data\fR files to properly identify the channels. @@ -195,7 +195,7 @@ The file \fItimers.conf\fR contains the timer setup. Each line contains one timer definition, with individual fields separated by ':' characters. Example: -\fB1:10:-T-----:2058:2150:50:5:Quarks & Co:\fR +\fB1:10:\-T\-\-\-\-\-:2058:2150:50:5:Quarks & Co:\fR The fields in a timer definition have the following meaning (from left to right): @@ -234,21 +234,21 @@ timer shall record. This must be in the range \fB1...31\fR. In case of a `repeating' timer this is a string consisting of exactly seven characters, where each character position corresponds to one day of the week -(with Monday being the first day). The character '-' at a certain position +(with Monday being the first day). The character '\-' at a certain position means that the timer shall not record on that day. Any other character will cause the timer to record on that day. Example: -.B MTWTF-- +.B MTWTF\-\- will define a timer that records on Monday thru Friday and does not record -on weekends. The same result could be achieved with \fBABCDE--\fR (this is +on weekends. The same result could be achieved with \fBABCDE\-\-\fR (this is used to allow setting the days with language specific characters). The day definition of a `repeating' timer may be followed by the date when that -timer shall hit for the first time. The format for this is \fB@YYYY-MM-DD\fR, +timer shall hit for the first time. The format for this is \fB@YYYY\-MM\-DD\fR, so a complete definition could look like this: -\fBMTWTF--@2002-02-18\fR +\fBMTWTF\-\-@2002\-02\-18\fR which would implement a timer that records Moday thru Friday, and will hit for the first time on or after February 18, 2002. @@ -416,7 +416,7 @@ and can be one of \fIRed\fR, \fIGreen\fR, \fIYellow\fR, \fIBlue\fR or keys, which will be executed just as if they had been pressed in the given sequence. The optional \fB@plugin\fR can be used to automatically select the given plugin from the main menu (provided that plugin has a main menu -entry). \fBplugin\fR is the name of the plugin, exactly as given in the -P +entry). \fBplugin\fR is the name of the plugin, exactly as given in the \-P option when starting VDR. There can be only one \fB@plugin\fR per key macro, and it implicitly adds an \fIOk\fR key to the macro definition (in order to actually select the plugins main menu entry), which counts against the total @@ -465,12 +465,12 @@ Check for new mail?: /usr/local/bin/checkmail 2>&1 .br CPU status: /usr/local/bin/cpustatus 2>&1 .br -Disk space: df -h | grep '/video' | awk '{ print 100 - $5 "% free"; }' +Disk space: df \-h | grep '/video' | awk '{ print 100 \- $5 "% free"; }' .br Calendar: date;echo;cal Note that the commands 'checkmail' and 'cpustatus' are only \fBexamples\fR! -Don't send emails to the author asking where to find these ;-) +Don't send emails to the author asking where to find these ;\-) .br The '?' at the end of the "Check for new mail?" entry will prompt the user whether this command shall really be executed. @@ -511,7 +511,7 @@ The file \fIsetup.conf\fR contains the basic configuration options for \fBvdr\fR Each line contains one option in the format "Name = Value". See the MANUAL file for a description of the available options. .SS THEMES -The files \fIthemes/-.theme\fR in the config directory contain the +The files \fIthemes/\-.theme\fR in the config directory contain the color theme definitions for the various skins. In the actual file names \fI\fR will be replaced by the name if the skin this theme belongs to, and \fI\fR will be the name of this theme. @@ -545,7 +545,7 @@ you can provide language specific descriptions as \fBDescription.eng = Shades of blue\fR .br -\fBDescription.ger = Blautöne\fR +\fBDescription.ger = Blaut\(:one\fR where the language code (as defined in VDR/i18n.c) is added to the keyword "Description", separated by a dot. You can enter as many language specific @@ -646,9 +646,9 @@ previous EPG scans. .SH AUTHOR Written by Klaus Schmidinger. .SH REPORTING BUGS -Report bugs to . +Report bugs to . .SH COPYRIGHT -Copyright \(co 2003 Klaus Schmidinger. +Copyright \(co 2004 Klaus Schmidinger. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -- cgit v1.2.3