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

List:       kde-commits
Subject:    KDE/kdenetwork/doc/kopete
From:       Burkhard Lück <lueck () hube-lueck ! de>
Date:       2008-09-30 20:31:13
Message-ID: 1222806673.794418.4962.nullmailer () svn ! kde ! org
[Download RAW message or body]

SVN commit 866429 by lueck:

typos and other bugs reported by Yuri Chornoivan, thanks

 M  +16 -16    chatstyle.docbook  
 M  +1 -1      index.docbook  
 M  +4 -4      menus.docbook  
 M  +2 -2      pipes.docbook  


--- trunk/KDE/kdenetwork/doc/kopete/chatstyle.docbook #866428:866429
@@ -9,16 +9,16 @@
 Beginning with &kopete; 0.12, we are now using <ulink
 url="http://www.adiumx.com/">Adium</ulink> format for our
 Chat Window style. The theme format is based on <acronym>HTML</acronym> templates \
                and <acronym>CSS</acronym>. They
-are easier to make and develop, only a knowledge of <acronym>HTML</acronym> and \
<acronym>CSS</acronym> is needed. Also, styles can have variants (defined as \
<acronym>CSS</acronym> file) which add more customisation value :). +are easier to \
make and develop, only a knowledge of <acronym>HTML</acronym> and \
<acronym>CSS</acronym> is needed. Also, styles can have variants (defined as \
<acronym>CSS</acronym> file) which add more customization value :).  </para>
 
 <sect2 id="chatstyle-reference-guide">
 	<title>Reference guide.</title>
 <para>
-Adium format consist of a directory structure, <acronym>HTML</acronym> templates, \
<acronym>CSS</acronym> files and keywords that are replaced each time the template is \
processed. The final conversation is a <acronym>XHTML</acronym> page where messages \
are added with <acronym>DOM</acronym> operations. The central element is a div \
element named <filename>Chat</filename>. Before and after this div element goes the \
Header and Footer template. Messages are childs of the <filename>Chat</filename> div \
element. +Adium format consist of a directory structure, <acronym>HTML</acronym> \
templates, <acronym>CSS</acronym> files and keywords that are replaced each time the \
template is processed. The final conversation is a <acronym>XHTML</acronym> page \
where messages are added with <acronym>DOM</acronym> operations. The central element \
is a div element named <filename>Chat</filename>. Before and after this div element \
goes the Header and Footer template. Messages are children of the \
<filename>Chat</filename> div element.  </para>
 
-<sect3 id="chatstyle-refrerence-directory">
+<sect3 id="chatstyle-reference-directory">
 	<title>Directory Structure</title>
 <para>A style must respect this directory structure. Code in &kopete; are thinking \
around this directory structure. When archiving the style, archive the \
<filename>styleName</filename> directory. The directory structure is a structure of a \
<application>Mac OS X</application> bundle for those familiar with that operating \
system. Also you must respect the case displayed here, because a \
<acronym>UNIX</acronym> system is case-sensitive.</para>  <programlisting>
@@ -55,7 +55,7 @@
 <varlistentry><term><filename>Header.html</filename> (Required)</term>
 <listitem>
 <para>
-Use the Header template to display a nice header to the conversation. This template \
is insered before <filename>Chat</filename> div element. If you don't use it, just \
put an empty file. +Use the Header template to display a nice header to the \
conversation. This template is inserted before <filename>Chat</filename> div element. \
If you don't use it, just put an empty file.  </para>
 </listitem>
 </varlistentry>
@@ -63,7 +63,7 @@
 <varlistentry><term><filename>Footer.html</filename> (Required)</term>
 <listitem>
 <para>
-This is mostly the same as Header but it is for the fotter of a conversation. This \
template is insered after <filename>Chat</filename> div element.  If you don't use \
it, just put an empty file. +This is mostly the same as Header but it is for the \
footer of a conversation. This template is inserted after <filename>Chat</filename> \
div element.  If you don't use it, just put an empty file.  </para>
 </listitem>
 </varlistentry>
@@ -71,7 +71,7 @@
 <varlistentry><term><filename>Status.html</filename> (Required)</term>
 <listitem>
 <para>
-This template is used to display a internal message. Internal messages such as \
status change, message from Kopete(ex: Incoming File Transfert). When the style do \
not supply a Action template, it is used to display Action message. +This template is \
used to display a internal message. Internal messages such as status change, message \
from Kopete (&eg; Incoming File Transfert). When the style do not supply a Action \
template, it is used to display Action message.  </para>
 </listitem>
 </varlistentry>
@@ -80,7 +80,7 @@
               <term><filename>Outgoing/Content.html</filename> (Required)</term>
 <listitem>
 <para>
-The content template is the message core. Think it as a block that will hold \
messages.. Make sure it is ready to receive consecutive messages, don't design it to \
only display one message. Consecutive messages will be inserted at the div insert \
element. +The content template is the message core. Think it as a block that will \
hold messages. Make sure it is ready to receive consecutive messages, don't design it \
to only display one message. Consecutive messages will be inserted at the div insert \
element.  </para>
 </listitem>
 </varlistentry>
@@ -110,7 +110,7 @@
               <term><filename>Outgoing/NextContext.html</filename> (Optional)</term>
 <listitem>
 <para>
-These templates are not used in Kopete. In Adium, they are used to display history. \
It is mostly the same thing as Content and NextContent but with some differences to \
distinguist from normal messages. +These templates are not used in Kopete. In Adium, \
they are used to display history. It is mostly the same thing as Content and \
NextContent but with some differences to distinguish from normal messages.  </para>
 </listitem>
 </varlistentry>
@@ -121,12 +121,12 @@
 
 <sect3 id="chatstyle-reference-css">
 	<title>About CSS styles and Variants</title>
-	<para>HTML template are used to describe how the structure is made. But all the \
style is described in <acronym>CSS</acronym> files. <filename>main.css</filename> is \
the main style, where variants are just alterations of the main style. Examples of \
variants are differents colors, no display of user photo. Both \
<filename>main.css</filename> and variants and imported in final \
<acronym>XHTML</acronym> page.</para> +	<para>HTML template are used to describe how \
the structure is made. But all the style is described in <acronym>CSS</acronym> \
files. <filename>main.css</filename> is the main style, where variants are just \
alterations of the main style. Examples of variants are different colors, no display \
of user photo. Both <filename>main.css</filename> and variants and imported in final \
<acronym>XHTML</acronym> page.</para>  <sect4 id="chatstyle-reference-css-main">
 		<title>-<filename>main.css</filename></title>
 		<para>This is the main <acronym>CSS</acronym> file which is common for all \
variants. This file should contain all the main description of the style.</para>  \
                </sect4>
-	<sect4 id="chatstyle-refrence-css-variants">
+	<sect4 id="chatstyle-reference-css-variants">
 		<title>-Variants</title>
 		<para>Variants are <acronym>CSS</acronym> files located in \
<filename>Variants/</filename> directory. Each variant is a single \
<acronym>CSS</acronym> file that include the <filename>main.css</filename> and do \
alteration to the main style.</para>  </sect4>
@@ -153,7 +153,7 @@
 
 <sect2 id="chatstyle-reference-keywords">
 	<title>Keywords reference</title>
-	<para>Keywords are likes holes to fill with details. On each new message, they are \
replaced with the correct value corresponding to their context. To fully support all \
features of Kopete, we added some keywords extentions to the Adium. Also some \
keywords are only available in certain context.</para> +	<para>Keywords are likes \
holes to fill with details. On each new message, they are replaced with the correct \
value corresponding to their context. To fully support all features of Kopete, we \
added some keywords extensions to the Adium. Also some keywords are only available in \
certain context.</para>  
 <variablelist><title>Keywords list for Header and Footer templates. </title>
 <para>There keywords are processed at the beginning of the chat.</para>
@@ -252,7 +252,7 @@
 </para>
 <para>
 <filename>%senderColor{N}%</filename> where N is a positive number. If N is greater \
                than 100, it represent a lighter color than the contact's color.
-If N equal 150 it is a color which is 50% brighter. If N is less than 100 then it is \
a darker color.  Usefull for having a background coloured differently for each \
contact. +If N equal 150 it is a color which is 50% brighter. If N is less than 100 \
then it is a darker color.  Useful for having a background coloured differently for \
each contact.  </para>
 <para>
 If you want to use theses colors in a variant, but not in the main style, you have \
to workaround. @@ -261,7 +261,7 @@
 <div style="color:%senderColor%;border:none;border-color:%senderColor{40}%;"><p \
class="message">...</p></div>  ]]>
 </programlisting>
-you can apply color ro the p.message element in your <filename>main.css</filename> \
file, and in your varient put something like +you can apply color to the p.message \
element in your <filename>main.css</filename> file, and in your variant put something \
like  <programlisting>
 	p.message { color:inherit; border-color:inherit; }
 </programlisting>
@@ -305,10 +305,10 @@
 
 <sect1 id="chatstyle-guideline">
 	<title>&kopete; Chat Window Style Guideline</title>
-<para>The &kopete; Chat Window Style Guideline is a set of things that your Chat \
Window style must support to be compilant with Kopete.</para> +<para>The &kopete; \
Chat Window Style Guideline is a set of things that your Chat Window style must \
support to be compliant with Kopete.</para>  <sect2 \
id="chatstyle-guideline-highlight">  <title>Support highlight</title>
-	<para>Your style must show hightlight. In Kopete and Adium, the \
<filename>%textbackgroundcolor{}%</filename> is replaced with the hightlight color. \
Add this style attribute: <userinput>background-color: \
%textbackgroundcolor{}%</userinput> to the HTML element that display the \
message.</para> +	<para>Your style must show highlight. In Kopete and Adium, the \
<filename>%textbackgroundcolor{}%</filename> is replaced with the highlight color. \
Add this style attribute: <userinput>background-color: \
%textbackgroundcolor{}%</userinput> to the HTML element that display the \
message.</para>  </sect2>
 <sect2 id="chatstyle-guideline-consecutive">
 	<title>Consecutive message templates are required.</title>
@@ -357,7 +357,7 @@
 
 <sect2 id="chatstyle-guideline-direction">
 	<title>Support right-to-left languages with <filename>%messageDirection%</filename> \
                keyword.</title>
-	<para><filename>%messageDirection%</filename> keyword is present for languages in \
the world that write right-to-left. It define the message direction, if it is \
"rtl"(right-to-left) or "ltr"(left-to-right). Add this style attribute to the HTML \
element that display the message: <userinput>direction: \
%messageDirection%</userinput>. Style preview in appearance config include a \
right-to-left to check if your style display it correctly. It should begin the string \
from the right.</para> +	<para><filename>%messageDirection%</filename> keyword is \
present for languages in the world that write right-to-left. It define the message \
direction, if it is "rtl" (right-to-left) or "ltr" (left-to-right). Add this style \
attribute to the HTML element that display the message: <userinput>direction: \
%messageDirection%</userinput>. Style preview in appearance config include a \
right-to-left to check if your style display it correctly. It should begin the string \
from the right.</para>  </sect2>
 </sect1>
 </appendix>
--- trunk/KDE/kdenetwork/doc/kopete/index.docbook #866428:866429
@@ -460,7 +460,7 @@
 </sect2>
 <sect2 id="global-identity">
 <title>Global Identity</title>
-<para>&kopete;'s Global Identity lets you set your own nickname and photo once for \
all your &im; accounts.  You can read these details from the &kde; address book entry \
for yourself, from a single one of your contacts, or add a completely new nickname or \
photo.  If you have an exciting dual life, you can create multiple identites and \
switch between them in the <guilabel>Identity</guilabel> section.</para> \
+<para>&kopete;'s Global Identity lets you set your own nickname and photo once for \
all your &im; accounts.  You can read these details from the &kde; address book entry \
for yourself, from a single one of your contacts, or add a completely new nickname or \
photo.  If you have an exciting dual life, you can create multiple identities and \
switch between them in the <guilabel>Identity</guilabel> section.</para>  </sect2>
 <sect2 id="configuring-behavior">
 <title>Behavior</title>
--- trunk/KDE/kdenetwork/doc/kopete/menus.docbook #866428:866429
@@ -653,7 +653,7 @@
 <term>
 <menuchoice>
 <guimenu>Tabs</guimenu>
-<guisubmenu>Move Chat to Window</guisubmenu>
+<guisubmenu>Move Tab to Window</guisubmenu>
 </menuchoice>
 </term>
 <listitem>
@@ -689,7 +689,7 @@
 <menuchoice>
 <guimenu>Settings</guimenu>
 <guisubmenu>Toolbars</guisubmenu>
-<guimenuitem>Show Main Toolbar (Kopete)</guimenuitem></menuchoice>
+<guimenuitem>Main Toolbar (Kopete)</guimenuitem></menuchoice>
 </term>
 <listitem>
 <para>Shows/hides the main toolbar.</para>
@@ -701,7 +701,7 @@
 <menuchoice>
 <guimenu>Settings</guimenu>
 <guisubmenu>Toolbars</guisubmenu>
-<guimenuitem>Show Status (Kopete)</guimenuitem></menuchoice>
+<guimenuitem>Status (Kopete)</guimenuitem></menuchoice>
 </term>
 <listitem>
 <para>Shows/hides &kopete;'s status bar.  This is where buddy pictures \
appear.</para> @@ -713,7 +713,7 @@
 <menuchoice>
 <guimenu>Settings</guimenu>
 <guisubmenu>Toolbars</guisubmenu>
-<guimenuitem>Show Format Toolbar (Kopete)</guimenuitem></menuchoice>
+<guimenuitem>Format Toolbar (Kopete)</guimenuitem></menuchoice>
 </term>
 <listitem>
 <para>Shows/hides the text formatting toolbar.</para>
--- trunk/KDE/kdenetwork/doc/kopete/pipes.docbook #866428:866429
@@ -4,7 +4,7 @@
 <appendix id="pipes">
 <title>&kopete; Pipes Plugin Implementation Guide</title>
 <para>
-Beginning with &kopete; 1.0, &kopete; ships with a plugin called Pipes. Pipes allows \
you to pipe incoming or outgoing messages through an external script or executable. \
An incoming message will be piped through the executable before it reaches your chat \
window, while outgoing messages will be piped through the executable before they are \
sent over the internet. Pipes can recieve text in one of three forms: +Beginning with \
&kopete; 1.0, &kopete; ships with a plugin called Pipes. Pipes allows you to pipe \
incoming or outgoing messages through an external script or executable. An incoming \
message will be piped through the executable before it reaches your chat window, \
while outgoing messages will be piped through the executable before they are sent \
over the internet. Pipes can receive text in one of three forms:  <variablelist>
 <varlistentry>
 <term>Plain text body</term>
@@ -79,7 +79,7 @@
 <sect1 id="xml-input">
 <title>&xml; Input</title>
 <para>
-Your program will recieve &xml; in its standard input stream, it will have the \
oppurtunity to modify it, and then it must hand it back to &kopete; by way of its \
standard ouput stream. If your program modifies the following elements, the internal \
knowledge that &kopete; has of the message will be modified to reflect your changes. \
+Your program will recieve &xml; in its standard input stream, it will have the \
opportunity to modify it, and then it must hand it back to &kopete; by way of its \
standard output stream. If your program modifies the following elements, the internal \
knowledge that &kopete; has of the message will be modified to reflect your changes.  \
<itemizedlist>  <listitem><para>"message" attribute "timestamp" but not other time \
attributes</para></listitem>  <listitem><para>"message" attribute \
"subject"</para></listitem>


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