[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    doc for ksirc
From:       Eric Bischoff <eric () boson ! caldera ! de>
Date:       2001-08-23 11:22:29
[Download RAW message or body]

Hi all,

Just to inform you that I did a few fixes in ksirc's doc. The details
follow.

--------------------------------------------------------------------
RCS file: /home/kde/kdenetwork/doc/ksirc/index.docbook,v
retrieving revision 1.12
diff -u -r1.12 index.docbook
--- index.docbook	2001/08/02 10:38:38	1.12
+++ index.docbook	2001/08/23 10:57:26
@@ -25,7 +25,7 @@
 
 <!-- TRANS:ROLES_OF_TRANSLATORS -->
 </authorgroup>
-<date>2001-07-25</date>
+<date>2001-08-23</date>
 <releaseinfo>1.10.00</releaseinfo>
 
 <legalnotice>&FDLNotice;</legalnotice>
@@ -335,7 +335,7 @@
 <para><userinput>&tilde;i</userinput> sets italics</para>
 </listitem>
 <listitem>
-<para><userinput>&tilde;r</userinput> sets underline</para>
+<para><userinput>&tilde;r</userinput> sets reverse video</para>
 </listitem>
 </itemizedlist>
 
@@ -619,7 +619,7 @@
 to deal with them one bit at a time.  You could do it in less rules, but
 it'll show you the basic rule structure, in nice steps, and how to use
 multiple rules to parse a message.  The first step is to remove the
-Path: portion of the message, and will be example 4.</para>
+Path: portion of the message:</para>
 
 <screen>Match: ^\*\*\*.* KILL message for.*
 From:  Path: \S+
@@ -630,7 +630,7 @@
 the <literal>*</literal>'s have to be quoted with <literal>\</literal>
 since by themselves they mean 0 or more of the prior character.
 <literal>.*</literal> means: match anything until you find <literal>
-"KILL message for"</literal>.  This allows us to avoid typing in
+KILL message for</literal>.  This allows us to avoid typing in
 <literal>-- Received...</literal> &etc; The trailing
 <literal>.*</literal> means: match anything to the end of the line. (not
 needed, I think)</para>
@@ -659,8 +659,8 @@
 
 <para>Match rule searches for the KILL message and makes sure it's from
 NickServ.  Notice the <literal>\(</literal> and <literal>\)</literal>
-both <literal>()</literal> and used in regex, therefore we have to quote
-them.  This is very similar to example 3.</para>
+are both used in regex, therefore we have to quote
+them.  This is very similar to what we said two examples before.</para>
 
 </listitem>
 <listitem>
@@ -668,21 +668,22 @@
 still pretty hard to read by simply glancing at it.  So let's reorder it
 to something like:</para>
 
-<screen>*** [KILL] &lt;KILLER&gt; killed &lt;KILLED&gt; (reason)
-Match: \*\*\*.*KILL message
+<screen>*** [KILL] <replaceable>KILLER</replaceable>; killed 
<replaceable>KILLED</replaceable>; 
(<replaceable>REASON</replaceable>)</screen>
+
+<screen>Match: \*\*\*.*KILL message
 From: \*\*\*.*for (.*?) from (.*?)\. \((.*?)\).*
 To: *** [KILL] $$2 killed $$1 ($$3)
 </screen>
 
 <para>Ok, the match looks for
-<literal>***<replaceable>something</replaceable></literal> KILL message.
+<literal>***<replaceable>something</replaceable> KILL message</literal>.
 We can't use <literal>&circ;</literal> since we may have just appended
 <literal>&tilde;&lt;window&gt;&tilde;</literal>.</para>
 
-<para>The from line get's a little more interesting.  The <literal>"for
+<para>The from line gets a little more interesting.  The <literal>"for
 (.*?) "</literal> looks for the word "for" then some text.
 <literal>.*?</literal> means: match zero or more of anything except
-newline, but isn't greedy. Stop when the first terminating condition is
+newline, but isn't greedy. The rule is to stop when the first terminating 
condition is
 found, not the last.  In other words it matches anything until a space is 
encountered.
 The surrounding <literal>()</literal> means: save the contents.  Each
 () saves the matched data in <literal>$&num;</literal> where
@@ -696,7 +697,9 @@
 
 </listitem>
 <listitem>
-<para>How to colorize your life. Ok, you want to add some color to
+<para>How to colorize your life.</para>
+
+<para>Ok, you want to add some color to
 &ksirc;.  See the <link linkend="sectcolors">Colors section</link> for
 color info, but here's a filter rule to highlight the nick between
 <literal>&lt;NICK&gt;</literal> on each line: </para>
@@ -706,7 +709,7 @@
 To: &lt;&tilde;4$$1&tilde;c&gt;</screen>
 
 <para>Takes the nick and adds color &num;4 between the two
-<literal>&lt;&gt; &tilde;c</literal> clears the color.</para>
+<literal>&lt;&gt;</literal>. <literal>&tilde;c</literal> clears the 
color.</para>
 
 </listitem>
 </orderedlist>
@@ -764,7 +767,7 @@
 <row>
 <entry><keycombo
 action="simul">&Ctrl;<keycap>X</keycap></keycombo></entry>
-<entry>Cut Window</entry>
+<entry>Cut</entry>
 </row>
 
 <row>
--------------------------------------------------------------------------------------

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic