Moved kpilot from kdepim to applications, as the core Trinity libraries should not contain hardware-dependent software

git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdepim@1221127 283d02a7-25f6-0310-bc7c-ecb5cbfe19da

1 files changed, 3 insertions, 3 deletions

diff --git a/libkmime/kmime_codecs.h b/libkmime/kmime_codecs.h
index 3ff0c4a4..211867bc 100644
--- a/libkmime/kmime_codecs.h
+++ b/libkmime/kmime_codecs.h
@@ -87,7 +87,7 @@ public:
    * This function doesn't support chaining of blocks. The returned
    * block cannot be added to, but you don't need to finalize it, too.
    *
-   * Example usage (@p in contains the input data):
+   * Example usage (@p in tqcontains the input data):
    * <pre>
    * KMime::Codec * codec = KMime::Codec::codecForName( "base64" );
    * kdFatal( !codec ) << "no base64 codec found!?" << endl;
@@ -123,7 +123,7 @@ public:
    * This function doesn't support chaining of blocks. The returned
    * block cannot be added to, but you don't need to finalize it, too.
    *
-   * Example usage (@p in contains the input data):
+   * Example usage (@p in tqcontains the input data):
    * <pre>
    * KMime::Codec * codec = KMime::Codec::codecForName( "base64" );
    * kdFatal( !codec ) << "no base64 codec found!?" << endl;
@@ -230,7 +230,7 @@ public:
  * the output and then delete the decoder instance. If you want to
  * process another input block sequence, you create a new instance.
  *
- * Typical usage (@p in contains the (base64-encoded) input data),
+ * Typical usage (@p in tqcontains the (base64-encoded) input data),
  * taking into account all the conventions detailed above:
  *
  * <pre>