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

List:       squirrelmail-cvs
Subject:    [SM-CVS] CVS: squirrelmail/doc compose.txt,1.3,1.4 db-backend.txt,1.10,1.11 ie_ssl.txt,1.2,1.3 plugi
From:       Fredrik Jervfors <jervfors () users ! sourceforge ! net>
Date:       2004-12-29 15:06:51
Message-ID: E1CjfPX-0006r5-A6 () sc8-pr-cvs1 ! sourceforge ! net
[Download RAW message or body]

Update of /cvsroot/squirrelmail/squirrelmail/doc
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv25901/doc

Modified Files:
	compose.txt db-backend.txt ie_ssl.txt plugin.txt presets.txt 
Log Message:
Changing squirrelmail/Squirrelmail to SquirrelMail in some strings as well as other \
minor documentation fixes

Index: compose.txt
===================================================================
RCS file: /cvsroot/squirrelmail/squirrelmail/doc/compose.txt,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -w -r1.3 -r1.4
--- compose.txt	21 Nov 2003 11:35:59 -0000	1.3
+++ compose.txt	29 Dec 2004 15:05:44 -0000	1.4
@@ -14,7 +14,7 @@
 3) Print it:
    echo makeComposeLink($comp_uri, $disp);
 
-makeComposeLink() has been available since Squirrelmail 1.4.2.
+makeComposeLink() has been available since SquirrelMail 1.4.2.
 
 
 

Index: db-backend.txt
===================================================================
RCS file: /cvsroot/squirrelmail/squirrelmail/doc/db-backend.txt,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -w -r1.10 -r1.11

Index: ie_ssl.txt
===================================================================
RCS file: /cvsroot/squirrelmail/squirrelmail/doc/ie_ssl.txt,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -w -r1.2 -r1.3
--- ie_ssl.txt	29 Jan 2001 20:56:08 -0000	1.2
+++ ie_ssl.txt	29 Dec 2004 15:05:44 -0000	1.3
@@ -10,7 +10,7 @@
 
 Once we had figured out that it was sessions in PHP that was causing the
 problem, we tried turning the session management off in the download script
-in Squirrelmail.  This introduced another problem for us because we NEEDED
+in SquirrelMail.  This introduced another problem for us because we NEEDED
 sessions to decypher the key so we could log into the IMAP server and
 download the attachment.
 

Index: plugin.txt
===================================================================
RCS file: /cvsroot/squirrelmail/squirrelmail/doc/plugin.txt,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -w -r1.56 -r1.57
--- plugin.txt	24 Nov 2004 22:33:11 -0000	1.56
+++ plugin.txt	29 Dec 2004 15:05:44 -0000	1.57
@@ -1138,7 +1138,7 @@
 
       You should change the header to look something more like:
 
-         # Copyright (c) 1999-2003 The Squirrelmail Development Team
+         # Copyright (c) 1999-2003 The SquirrelMail Development Team
          # Roland Bauerschmidt <rb@debian.org>, 1999.
          # $Id$
          msgid ""
@@ -1147,7 +1147,7 @@
          "POT-Creation-Date: 2003-01-21 19:21+0100\n"
          "PO-Revision-Date: 2003-01-21 21:01+0100\n"
          "Last-Translator: Juergen Edner <juergen.edner@epost.de>\n"
-         "Language-Team: German <squirrelmail-i18n@lists.squirrelmail.net>\n"
+         "Language-Team: German <squirrelmail-i18n@lists.sourceforge.net>\n"
          "MIME-Version: 1.0\n"
          "Content-Type: text/plain; charset=ISO-8859-1\n"
          "Content-Transfer-Encoding: 8bit\n"
@@ -1182,9 +1182,9 @@
 If you wish, you can use phpdoc (Javadoc-style) comments, when documenting your
 code.
 
-If you follow the standards that are followed between Squirrelmail core &
+If you follow the standards that are followed between SquirrelMail core &
 plugin developers, the resulted documentation can be included with the rest of
-the Squirrelmail code & API documentation. Specifically, in the page-level
+the SquirrelMail code & API documentation. Specifically, in the page-level
 docblock, declare the package to be 'plugins', and the subpackage to be the
 name of your plugin. For instance:
 
@@ -1201,7 +1201,7 @@
 The rest is up to you. Try to follow some common sense and document what is
 really needed. Documenting the code properly can be a big help not only to
 yourself, but to those who will take a look at your code, fix the bugs and even
-improve it, in the true open-source spirit that Squirrelmail was built upon.
+improve it, in the true open-source spirit that SquirrelMail was built upon.
 
 For more information about phpdocumentor and how to write proper-tagged
 comments, you are directed at:

Index: presets.txt
===================================================================
RCS file: /cvsroot/squirrelmail/squirrelmail/doc/presets.txt,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -w -r1.3 -r1.4
--- presets.txt	26 Dec 2004 22:42:40 -0000	1.3
+++ presets.txt	29 Dec 2004 15:05:46 -0000	1.4
@@ -1,6 +1,6 @@
 $Date$
 
-This file lists squirrelmail options set by D option in conf.pl
+This file lists SquirrelMail options set by D option in conf.pl
 
 It can be used if user can't run conf.pl and changes options manually.
 Settings can be different if IMAP server uses shared folders.



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
--
squirrelmail-cvs mailing list
List Address: squirrelmail-cvs@lists.sourceforge.net
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-cvs
http://squirrelmail.org/cvs


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