diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/api/Doxyfile.pim | 2 | ||||
| -rw-r--r-- | doc/kalarm/index.docbook | 154 | ||||
| -rw-r--r-- | doc/karm/index.docbook | 12 | ||||
| -rw-r--r-- | doc/kmail/configure.docbook | 6 | ||||
| -rw-r--r-- | doc/kmail/using-kmail.docbook | 4 | ||||
| -rw-r--r-- | doc/knode/introduction.docbook | 2 | ||||
| -rw-r--r-- | doc/knode/journey.docbook | 4 | ||||
| -rw-r--r-- | doc/knode/using-morefeatures.docbook | 2 | ||||
| -rw-r--r-- | doc/kontact/index.docbook | 11 | ||||
| -rw-r--r-- | doc/korganizer/index.docbook | 8 |
10 files changed, 98 insertions, 107 deletions
diff --git a/doc/api/Doxyfile.pim b/doc/api/Doxyfile.pim index 62cf67904..2f2385026 100644 --- a/doc/api/Doxyfile.pim +++ b/doc/api/Doxyfile.pim @@ -930,7 +930,7 @@ INCLUDE_FILE_PATTERNS = PREDEFINED = TQT_VERSION=320 \ __cplusplus \ - Q_WS_X11 + TQ_WS_X11 # If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then # this tag can be used to specify a list of macro names that should be expanded. diff --git a/doc/kalarm/index.docbook b/doc/kalarm/index.docbook index 3362f18c4..a85022ff1 100644 --- a/doc/kalarm/index.docbook +++ b/doc/kalarm/index.docbook @@ -2700,8 +2700,8 @@ at some future date.</para></note> </refnamediv> <refsynopsisdiv> <synopsis> -void cancelEvent(const QString& <replaceable>calendarFile</replaceable>, - const QString& <replaceable>eventID</replaceable>) +void cancelEvent(const TQString& <replaceable>calendarFile</replaceable>, + const TQString& <replaceable>eventID</replaceable>) </synopsis> <refsect2> @@ -2751,8 +2751,8 @@ ignored.</para></note> </refnamediv> <refsynopsisdiv> <synopsis> -void triggerEvent(const QString& <replaceable>calendarFile</replaceable>, - const QString& <replaceable>eventID</replaceable>) +void triggerEvent(const TQString& <replaceable>calendarFile</replaceable>, + const TQString& <replaceable>eventID</replaceable>) </synopsis> <refsect2> @@ -2809,8 +2809,8 @@ ignored.</para></note> </refnamediv> <refsynopsisdiv> <synopsis> -void handleEvent(const QString& <replaceable>calendarFile</replaceable>, - const QString& <replaceable>eventID</replaceable>) +void handleEvent(const TQString& <replaceable>calendarFile</replaceable>, + const TQString& <replaceable>eventID</replaceable>) </synopsis> <refsect2> @@ -2876,26 +2876,26 @@ ignored.</para></note> </refnamediv> <refsynopsisdiv> <synopsis> -bool scheduleMessage(const QString& <replaceable>message</replaceable>, - const QString& <replaceable>dateTime</replaceable>, +bool scheduleMessage(const TQString& <replaceable>message</replaceable>, + const TQString& <replaceable>dateTime</replaceable>, int <replaceable>lateCancel</replaceable>, int <replaceable>flags</replaceable>, - const QString& <replaceable>bgColor</replaceable>, - const QString& <replaceable>fgColor</replaceable>, - const QString& <replaceable>font</replaceable>, + const TQString& <replaceable>bgColor</replaceable>, + const TQString& <replaceable>fgColor</replaceable>, + const TQString& <replaceable>font</replaceable>, const KURL& <replaceable>audioURL</replaceable>, int <replaceable>reminder</replaceable>, - const QString& <replaceable>recurrence</replaceable>, + const TQString& <replaceable>recurrence</replaceable>, int <replaceable>subRepeatInterval</replaceable>, int <replaceable>subRepeatCount</replaceable>) </synopsis> <synopsis> -bool scheduleMessage(const QString& <replaceable>message</replaceable>, - const QString& <replaceable>dateTime</replaceable>, +bool scheduleMessage(const TQString& <replaceable>message</replaceable>, + const TQString& <replaceable>dateTime</replaceable>, int <replaceable>lateCancel</replaceable>, int <replaceable>flags</replaceable>, - const QString& <replaceable>bgColor</replaceable>, - const QString& <replaceable>fgColor</replaceable>, - const QString& <replaceable>font</replaceable>, + const TQString& <replaceable>bgColor</replaceable>, + const TQString& <replaceable>fgColor</replaceable>, + const TQString& <replaceable>font</replaceable>, const KURL& <replaceable>audioURL</replaceable>, int <replaceable>reminder</replaceable>, int <replaceable>recurType</replaceable>, @@ -2903,18 +2903,18 @@ bool scheduleMessage(const QString& <replaceable>message</replaceable>, int <replaceable>recurCount</replaceable>) </synopsis> <synopsis> -bool scheduleMessage(const QString& <replaceable>message</replaceable>, - const QString& <replaceable>dateTime</replaceable>, +bool scheduleMessage(const TQString& <replaceable>message</replaceable>, + const TQString& <replaceable>dateTime</replaceable>, int <replaceable>lateCancel</replaceable>, int <replaceable>flags</replaceable>, - const QString& <replaceable>bgColor</replaceable>, - const QString& <replaceable>fgColor</replaceable>, - const QString& <replaceable>font</replaceable>, + const TQString& <replaceable>bgColor</replaceable>, + const TQString& <replaceable>fgColor</replaceable>, + const TQString& <replaceable>font</replaceable>, const KURL& <replaceable>audioURL</replaceable>, int <replaceable>reminder</replaceable>, int <replaceable>recurType</replaceable>, int <replaceable>recurInterval</replaceable>, - const QString& <replaceable>endDateTime</replaceable>) + const TQString& <replaceable>endDateTime</replaceable>) </synopsis> <refsect2> @@ -2933,12 +2933,12 @@ bool scheduleMessage(const QString& <replaceable>message</replaceable>, <para>Specifies the scheduled date, or date and time, at which the message should be displayed. For a date-only alarm, the string should be in the format <quote>YYYY-MM-DD</quote> (as returned by -<methodname>QDate::toString(Qt::ISODate)</methodname>). For an alarm +<methodname>QDate::toString(TQt::ISODate)</methodname>). For an alarm with a date and time, the string should be in the format <quote>YYYY-MM-DDTHH:MM[:SS]</quote> (as returned by -<methodname>QDateTime::toString(Qt::ISODate)</methodname>) or +<methodname>QDateTime::toString(TQt::ISODate)</methodname>) or <quote>HH:MM[:SS]</quote> (as returned by -<methodname>QTime::toString(Qt::ISODate)</methodname>). If no date is +<methodname>QTime::toString(TQt::ISODate)</methodname>). If no date is specified, today's date is used. Note that any seconds value is ignored.</para> </listitem> @@ -2969,10 +2969,10 @@ applicable to message alarms.</para> <listitem> <para>Specifies the background color for displaying the message. The string may be in the format <quote>#RRGGBB</quote> (as returned by -<methodname>QColor::name()</methodname>) where RR, GG and BB are +<methodname>TQColor::name()</methodname>) where RR, GG and BB are two-digit hexadecimal values for red, green and blue. Alternatively the string may be in any of the other formats accepted by -<methodname>QColor::setNamedColor()</methodname>, such as a name from +<methodname>TQColor::setNamedColor()</methodname>, such as a name from the X color database (⪚ <quote>red</quote> or <quote>steelblue</quote>). Set the string to null to specify the current default background color.</para> @@ -3124,22 +3124,22 @@ text or image file.</refpurpose> <refsynopsisdiv> <synopsis> bool scheduleFile(const KURL& <replaceable>URL</replaceable>, - const QString& <replaceable>dateTime</replaceable>, + const TQString& <replaceable>dateTime</replaceable>, int <replaceable>lateCancel</replaceable>, int <replaceable>flags</replaceable>, - const QString& <replaceable>bgColor</replaceable>, + const TQString& <replaceable>bgColor</replaceable>, const KURL& <replaceable>audioURL</replaceable>, int <replaceable>reminder</replaceable>, - const QString& <replaceable>recurrence</replaceable>, + const TQString& <replaceable>recurrence</replaceable>, int <replaceable>subRepeatInterval</replaceable>, int <replaceable>subRepeatCount</replaceable>) </synopsis> <synopsis> bool scheduleFile(const KURL& <replaceable>URL</replaceable>, - const QString& <replaceable>dateTime</replaceable>, + const TQString& <replaceable>dateTime</replaceable>, int <replaceable>lateCancel</replaceable>, int <replaceable>flags</replaceable>, - const QString& <replaceable>bgColor</replaceable>, + const TQString& <replaceable>bgColor</replaceable>, const KURL& <replaceable>audioURL</replaceable>, int <replaceable>reminder</replaceable>, int <replaceable>recurType</replaceable>, @@ -3148,15 +3148,15 @@ bool scheduleFile(const KURL& <replaceable>URL</replaceable>, </synopsis> <synopsis> bool scheduleFile(const KURL& <replaceable>URL</replaceable>, - const QString& <replaceable>dateTime</replaceable>, + const TQString& <replaceable>dateTime</replaceable>, int <replaceable>lateCancel</replaceable>, int <replaceable>flags</replaceable>, - const QString& <replaceable>bgColor</replaceable>, + const TQString& <replaceable>bgColor</replaceable>, const KURL& <replaceable>audioURL</replaceable>, int <replaceable>reminder</replaceable>, int <replaceable>recurType</replaceable>, int <replaceable>recurInterval</replaceable>, - const QString& <replaceable>endDateTime</replaceable>) + const TQString& <replaceable>endDateTime</replaceable>) </synopsis> <refsect2> @@ -3176,12 +3176,12 @@ displayed in the message to be scheduled.</para> <para>Specifies the scheduled date, or date and time, at which the file should be displayed. For a date-only alarm, the string should be in the format <quote>YYYY-MM-DD</quote> (as returned by -<methodname>QDate::toString(Qt::ISODate)</methodname>). For an alarm +<methodname>QDate::toString(TQt::ISODate)</methodname>). For an alarm with a date and time, the string should be in the format <quote>YYYY-MM-DDTHH:MM[:SS]</quote> (as returned by -<methodname>QDateTime::toString(Qt::ISODate)</methodname>) or +<methodname>QDateTime::toString(TQt::ISODate)</methodname>) or <quote>HH:MM[:SS]</quote> (as returned by -<methodname>QTime::toString(Qt::ISODate)</methodname>). If no date is +<methodname>QTime::toString(TQt::ISODate)</methodname>). If no date is specified, today's date is used. Note that any seconds value is ignored.</para> </listitem> @@ -3212,10 +3212,10 @@ applicable to file alarms.</para> <listitem> <para>Specifies the background color for displaying the file. The string may be in the format <quote>#RRGGBB</quote> (as returned by -<methodname>QColor::name()</methodname>) where RR, GG and BB are +<methodname>TQColor::name()</methodname>) where RR, GG and BB are two-digit hexadecimal values for red, green and blue. Alternatively the string may be in any of the other formats accepted by -<methodname>QColor::setNamedColor()</methodname>, such as a name from +<methodname>TQColor::setNamedColor()</methodname>, such as a name from the X color database (⪚ <quote>red</quote> or <quote>steelblue</quote>). Set the string to null to specify the current default background color.</para> @@ -3338,17 +3338,17 @@ command.</refpurpose> </refnamediv> <refsynopsisdiv> <synopsis> -bool scheduleCommand(const QString& <replaceable>commandLine</replaceable>, - const QString& <replaceable>dateTime</replaceable>, +bool scheduleCommand(const TQString& <replaceable>commandLine</replaceable>, + const TQString& <replaceable>dateTime</replaceable>, int <replaceable>lateCancel</replaceable>, int <replaceable>flags</replaceable>, - const QString& <replaceable>recurrence</replaceable>, + const TQString& <replaceable>recurrence</replaceable>, int <replaceable>subRepeatInterval</replaceable>, int <replaceable>subRepeatCount</replaceable>) </synopsis> <synopsis> -bool scheduleCommand(const QString& <replaceable>commandLine</replaceable>, - const QString& <replaceable>dateTime</replaceable>, +bool scheduleCommand(const TQString& <replaceable>commandLine</replaceable>, + const TQString& <replaceable>dateTime</replaceable>, int <replaceable>lateCancel</replaceable>, int <replaceable>flags</replaceable>, int <replaceable>recurType</replaceable>, @@ -3356,13 +3356,13 @@ bool scheduleCommand(const QString& <replaceable>commandLine</replaceable>, int <replaceable>recurCount</replaceable>) </synopsis> <synopsis> -bool scheduleCommand(const QString& <replaceable>commandLine</replaceable>, - const QString& <replaceable>dateTime</replaceable>, +bool scheduleCommand(const TQString& <replaceable>commandLine</replaceable>, + const TQString& <replaceable>dateTime</replaceable>, int <replaceable>lateCancel</replaceable>, int <replaceable>flags</replaceable>, int <replaceable>recurType</replaceable>, int <replaceable>recurInterval</replaceable>, - const QString& <replaceable>endDateTime</replaceable>) + const TQString& <replaceable>endDateTime</replaceable>) </synopsis> <refsect2> @@ -3383,12 +3383,12 @@ parameter contains a shell command line or a command script.</para> <para>Specifies the scheduled date, or date and time, at which the command should be executed. For a date-only alarm, the string should be in the format <quote>YYYY-MM-DD</quote> (as returned by -<methodname>QDate::toString(Qt::ISODate)</methodname>). For an alarm +<methodname>QDate::toString(TQt::ISODate)</methodname>). For an alarm with a date and time, the string should be in the format <quote>YYYY-MM-DDTHH:MM[:SS]</quote> (as returned by -<methodname>QDateTime::toString(Qt::ISODate)</methodname>) or +<methodname>QDateTime::toString(TQt::ISODate)</methodname>) or <quote>HH:MM[:SS]</quote> (as returned by -<methodname>QTime::toString(Qt::ISODate)</methodname>). If no date is +<methodname>QTime::toString(TQt::ISODate)</methodname>). If no date is specified, today's date is used. Note that any seconds value is ignored.</para> </listitem> @@ -3512,25 +3512,25 @@ parameters, its usage is identical to </refnamediv> <refsynopsisdiv> <synopsis> -bool scheduleEmail(const QString& <replaceable>fromID</replaceable>, - const QString& <replaceable>addresses</replaceable>, - const QString& <replaceable>subject</replaceable>, - const QString& <replaceable>message</replaceable>, - const QString& <replaceable>attachments</replaceable>, - const QString& <replaceable>dateTime</replaceable>, +bool scheduleEmail(const TQString& <replaceable>fromID</replaceable>, + const TQString& <replaceable>addresses</replaceable>, + const TQString& <replaceable>subject</replaceable>, + const TQString& <replaceable>message</replaceable>, + const TQString& <replaceable>attachments</replaceable>, + const TQString& <replaceable>dateTime</replaceable>, int <replaceable>lateCancel</replaceable>, int <replaceable>flags</replaceable>, - const QString& <replaceable>recurrence</replaceable>, + const TQString& <replaceable>recurrence</replaceable>, int <replaceable>subRepeatInterval</replaceable>, int <replaceable>subRepeatCount</replaceable>) </synopsis> <synopsis> -bool scheduleEmail(const QString& <replaceable>fromID</replaceable>, - const QString& <replaceable>addresses</replaceable>, - const QString& <replaceable>subject</replaceable>, - const QString& <replaceable>message</replaceable>, - const QString& <replaceable>attachments</replaceable>, - const QString& <replaceable>dateTime</replaceable>, +bool scheduleEmail(const TQString& <replaceable>fromID</replaceable>, + const TQString& <replaceable>addresses</replaceable>, + const TQString& <replaceable>subject</replaceable>, + const TQString& <replaceable>message</replaceable>, + const TQString& <replaceable>attachments</replaceable>, + const TQString& <replaceable>dateTime</replaceable>, int <replaceable>lateCancel</replaceable>, int <replaceable>flags</replaceable>, int <replaceable>recurType</replaceable>, @@ -3538,17 +3538,17 @@ bool scheduleEmail(const QString& <replaceable>fromID</replaceable>, int <replaceable>recurCount</replaceable>) </synopsis> <synopsis> -bool scheduleEmail(const QString& <replaceable>fromID</replaceable>, - const QString& <replaceable>addresses</replaceable>, - const QString& <replaceable>subject</replaceable>, - const QString& <replaceable>message</replaceable>, - const QString& <replaceable>attachments</replaceable>, - const QString& <replaceable>dateTime</replaceable>, +bool scheduleEmail(const TQString& <replaceable>fromID</replaceable>, + const TQString& <replaceable>addresses</replaceable>, + const TQString& <replaceable>subject</replaceable>, + const TQString& <replaceable>message</replaceable>, + const TQString& <replaceable>attachments</replaceable>, + const TQString& <replaceable>dateTime</replaceable>, int <replaceable>lateCancel</replaceable>, nt <replaceable>flags</replaceable>, int <replaceable>recurType</replaceable>, int <replaceable>recurInterval</replaceable>, - const QString& <replaceable>endTime</replaceable>) + const TQString& <replaceable>endTime</replaceable>) </synopsis> <refsect2> @@ -3599,12 +3599,12 @@ email attachments.</para> <para>Specifies the scheduled date, or date and time, at which the email should be sent. For a date-only alarm, the string should be in the format <quote>YYYY-MM-DD</quote> (as returned by -<methodname>QDate::toString(Qt::ISODate)</methodname>). For an alarm +<methodname>QDate::toString(TQt::ISODate)</methodname>). For an alarm with a date and time, the string should be in the format <quote>YYYY-MM-DDTHH:MM[:SS]</quote> (as returned by -<methodname>QDateTime::toString(Qt::ISODate)</methodname>) or +<methodname>QDateTime::toString(TQt::ISODate)</methodname>) or <quote>HH:MM[:SS]</quote> (as returned by -<methodname>QTime::toString(Qt::ISODate)</methodname>). If no date is +<methodname>QTime::toString(TQt::ISODate)</methodname>). If no date is specified, today's date is used. Note that any seconds value is ignored.</para> </listitem> @@ -3728,7 +3728,7 @@ dialog</link> to edit an alarm.</refpurpose> </refnamediv> <refsynopsisdiv> <synopsis> -bool edit(const QString& <replaceable>eventID</replaceable>) +bool edit(const TQString& <replaceable>eventID</replaceable>) </synopsis> <refsect2> @@ -3772,7 +3772,7 @@ dialog</link> to edit a new alarm.</refpurpose> </refnamediv> <refsynopsisdiv> <synopsis> -bool editNew(const QString& <replaceable>templateName</replaceable>) +bool editNew(const TQString& <replaceable>templateName</replaceable>) </synopsis> <refsect2> diff --git a/doc/karm/index.docbook b/doc/karm/index.docbook index 08de3cc40..e8d6495e3 100644 --- a/doc/karm/index.docbook +++ b/doc/karm/index.docbook @@ -1117,7 +1117,7 @@ times were reset.</para></glossdef> </glossentry> </refnamediv> <refsynopsisdiv> <synopsis> -QString version() +TQString version() </synopsis> </refsynopsisdiv> <refsect1> @@ -1138,7 +1138,7 @@ in the typical GNU format of major.minor.bugfix.</para> </refnamediv> <refsynopsisdiv> <synopsis> -QString quit() +TQString quit() </synopsis> </refsynopsisdiv> <refsect1> @@ -1159,7 +1159,7 @@ external program can gracefully shutdown &karm;. </refnamediv> <refsynopsisdiv> <synopsis> -QString hastodo(QString taskname) +TQString hastodo(TQString taskname) </synopsis> <refsect2> <title>Parameters</title> @@ -1175,7 +1175,7 @@ QString hastodo(QString taskname) </refsynopsisdiv> <refsect1> <title>Description</title> -<para><function>hastodo(QString taskname)</function> is a &DCOP; call that +<para><function>hastodo(TQString taskname)</function> is a &DCOP; call that looks for a of the given name. If found, it returns the iCalendar UID that identifies that todo. If not found, it returns an empty string. @@ -1196,7 +1196,7 @@ than one todo has a matching name, the first one found is returned.</para> </refnamediv> <refsynopsisdiv> <synopsis> -QString addtodo(QString todoname) +TQString addtodo(TQString todoname) </synopsis> <refsect2> <title>Parameters</title> @@ -1213,7 +1213,7 @@ QString addtodo(QString todoname) <refsect1> <title>Description</title> -<para><function>addtodo(QString todoname)</function> is a &DCOP; call that +<para><function>addtodo(TQString todoname)</function> is a &DCOP; call that adds a new top-level todo to the current storage. The UID of the new todo is returned. </para> diff --git a/doc/kmail/configure.docbook b/doc/kmail/configure.docbook index 7ca072621..b48c7150f 100644 --- a/doc/kmail/configure.docbook +++ b/doc/kmail/configure.docbook @@ -1053,7 +1053,7 @@ of key words can be modified.</para> <quote>read receipt</quote>. The message author requests a disposition notification to be sent and the receiver's mail program generates a reply from which the author can - learn what happened to his message. Common disposition + learn what happened to their message. Common disposition types include <quote>displayed</quote> (&ie; read), <quote>deleted</quote> and <quote>dispatched</quote> (⪚ forwarded). @@ -1099,7 +1099,7 @@ of key words can be modified.</para> notification. This is only <emphasis>slightly</emphasis> better than always sending &mdn;s. The author will still know that - the messages has been acted upon, he just cannot + the messages has been acted upon, they just cannot tell whether it was deleted or read &etc; </para> </listitem> @@ -1145,7 +1145,7 @@ of key words can be modified.</para> message-id and the original recipient is included in the &mdn; reply. This preserves enough information for the sender to find the message in - his sent messages for which this &mdn; was + their sent messages for which this &mdn; was generated. </para> </listitem> diff --git a/doc/kmail/using-kmail.docbook b/doc/kmail/using-kmail.docbook index 999bd6d96..8609f2e6a 100644 --- a/doc/kmail/using-kmail.docbook +++ b/doc/kmail/using-kmail.docbook @@ -344,7 +344,7 @@ choose from the list of common &MIME; types. You can also select an encoding method for your file from the list of encoding options (normally, the default value works fine). Check the <guilabel>Suggest automatic display</guilabel> option if you want to suggest to the recipient the automatic (inline) display of this attachment. Whether this works or not depends on the recipient's email client -and on his settings.</para> +and on their settings.</para> <para>You can also attach public keys to the message by using the appropriate options in the <menuchoice><guimenu>Attach</guimenu></menuchoice> menu. <application>PGP</application> @@ -2014,7 +2014,7 @@ defined for the current identity to the message. Now you can send the message.</ that the receiver will get the correct key: there can be a man-in-the-middle attack, as somebody can change the key and sign the message with that other key. That is why the recipient should verify the attached key by checking the -key's fingerprint against the one he received in a secure way from you; have a look +key's fingerprint against the one they received in a secure way from you; have a look at the <application>PGP</application> documentation for further details.</para> </sect2> diff --git a/doc/knode/introduction.docbook b/doc/knode/introduction.docbook index db14ec3a8..91cda1428 100644 --- a/doc/knode/introduction.docbook +++ b/doc/knode/introduction.docbook @@ -37,7 +37,7 @@ is not answered in this manual.</para> Usenet</link> chapter is recommended; it is not so much about &knode; as how to move about in the Usenet with its help. In general, it is not sufficient to just master a news reader for writing news -articles: imagine a car driver who masters his car perfectly but does +articles: imagine a car driver who masters a car perfectly but does not know about the traffic rules or signs; do you want to encounter such a driver when out in traffic? So please take your time to learn at least a little about the <quote>traffic rules</quote> of the diff --git a/doc/knode/journey.docbook b/doc/knode/journey.docbook index 54dc82a32..15a4905f5 100644 --- a/doc/knode/journey.docbook +++ b/doc/knode/journey.docbook @@ -158,7 +158,7 @@ newsgroup. It stands for: (R)ead (T)he (F)...ing <para>Wait, what is <acronym>BTW</acronym> now? Another often-seen acronym which means (B)y (T)he (W)ay. It is easy when you know it; to avoid you having to continuously speculate over the meaning of -acronyms there is table at he end of this section containing the +acronyms there is table at the end of this section containing the most-often-used acronyms.</para> <para>This table does not try to be complete and is based on a list by @@ -519,7 +519,7 @@ head and think of a face.</para> <title>PLONK!</title> <para>This PLONK! looks like some comic-sound, does it not? And that is -exactly what it is used for. The one who reads it knows he was just +exactly what it is used for. The one who reads it knows they were just added to the killfile of a newsreader; normally this means the recipient of the PLONK! annoyed the sender. The PLONK! is meant to play back the sound of the recipients name hitting the ground in the diff --git a/doc/knode/using-morefeatures.docbook b/doc/knode/using-morefeatures.docbook index 28d3142c2..62e769abc 100644 --- a/doc/knode/using-morefeatures.docbook +++ b/doc/knode/using-morefeatures.docbook @@ -688,7 +688,7 @@ examples.</para> Test; to do this choose the <guilabel>From</guilabel> header line from the first drop-down list, choose <guilabel>is exactly the same as</guilabel> from the second -drop-down list, and enter his name in the text field. +drop-down list, and enter their name in the text field. But, before doing this you should have a look at the <glossterm>header</glossterm> of one of Theodor's articles and see what is in the <quote>From</quote> line.</para> diff --git a/doc/kontact/index.docbook b/doc/kontact/index.docbook index 13fdb8159..447158997 100644 --- a/doc/kontact/index.docbook +++ b/doc/kontact/index.docbook @@ -7,7 +7,6 @@ <!ENTITY % addindex "IGNORE"> <!ENTITY % English "INCLUDE"> <!ENTITY akregator "<application>Akregator</application>"> - <!ENTITY kitchensync "<application>KitchenSync</application>"> ]> <book id="kontact" lang="&language;"> @@ -146,14 +145,6 @@ application. </para> </sect1> -<sect1 id="synchronization"> -<title>&kitchensync;</title> -<para> -<ulink url="help:kitchensync">&kitchensync;</ulink>, the &kde; synchronization -application. -</para> -</sect1> - <sect1 id="feeds"> <title>&akregator;</title> <para> @@ -972,7 +963,7 @@ The settings stored in the profile include typical Look&Feel related options <para> Two default profiles are provided by Kontact: "&kontact; Style", which contains the default &kontact; settings, and "Outlook Style", adapting &kontact; to Microsoft Outlook Look&Feel. -The user can adapt existing profiles, create new profiles from his current settings, and import and export profiles. +The user can adapt existing profiles, create new profiles from their current settings, and import and export profiles. </para> <para> diff --git a/doc/korganizer/index.docbook b/doc/korganizer/index.docbook index 39e0eee79..b9dcf2129 100644 --- a/doc/korganizer/index.docbook +++ b/doc/korganizer/index.docbook @@ -403,7 +403,7 @@ want to use another resource, especially if you use a supported groupware server. Please ask the server administrator for the information required to configure the groupware resource, including free/busy information publishing and retrieving. Access to free/busy information allows an event organizer to -take the attendee's calendar in consideration when adding him to the event's +take the attendee's calendar in consideration when adding them to the event's attendee list.</para> <note><para>Besides calendar storage, groupware servers typically offer contacts, @@ -694,7 +694,7 @@ and do not reload the file at regular intervals.</para> the same remote file at the same time, because the remote file resource does not offer a conflict resolution mechanism. For instance, if someone else changes (and saves) the remote file, after you loaded it, and a some time later you save -the file, his changes will be lost. +the file, their changes will be lost. </para></warning> </listitem> @@ -1734,7 +1734,7 @@ requested from the attendee.</para></listitem> <varlistentry> <term><guibutton>Select Addressee</guibutton></term> <listitem><para>If the attendee(s) are in your Address Book, you do not have to -remember or type his email address to add it to the attendee list. Just click +remember or type their email address to add it to the attendee list. Just click the <guibutton>Select Addressee...</guibutton> button and choose the attendee(s) from the list. Please note that this is the standard &kde; address book, which is also used by &kmail; and can also be called as a separate application @@ -1821,7 +1821,7 @@ by dragging it with the mouse, or resize it by moving the edges of the highlight area with the mouse.</para> <para>The free/busy information is only available if the -attendee publishes his free/busy schedule, and if &korganizer; is correctly +attendee publishes their free/busy schedule, and if &korganizer; is correctly configured to retrieve it. For more information about configuring &korganizer; to publish and retrieve free/busy information, please check the <xref linkend="config" />. Double-clicking on an attendee entry in the list |