summaryrefslogtreecommitdiffstats
path: root/qtools
diff options
context:
space:
mode:
authorluzpaz <kunda@scribus.net>2017-12-23 16:50:49 (GMT)
committerluzpaz <kunda@scribus.net>2017-12-23 16:52:14 (GMT)
commit9fd7f3aeb4c2e78bda669bf4ef6fff1c12c062a4 (patch)
tree998cae2d5a219eb49b12903500d5692fe5fbe3c3 /qtools
parent4f45bd20d4da7d40c793ec4c4c13558581e995ac (diff)
downloadDoxygen-9fd7f3aeb4c2e78bda669bf4ef6fff1c12c062a4.zip
Doxygen-9fd7f3aeb4c2e78bda669bf4ef6fff1c12c062a4.tar.gz
Doxygen-9fd7f3aeb4c2e78bda669bf4ef6fff1c12c062a4.tar.bz2
Misc. typos
Super trivial typos Some are in qtools/ which I know is a 3rd party dependency but as we know is now obsolete upstream. I reckon it wouldn't be much of an issue to merge neverthless Tacked on several more commits
Diffstat (limited to 'qtools')
-rw-r--r--qtools/qdatastream.cpp2
-rw-r--r--qtools/qdict.doc2
-rw-r--r--qtools/qstring.cpp2
-rw-r--r--qtools/qtextcodec.cpp2
-rw-r--r--qtools/qvaluelist.doc32
-rw-r--r--qtools/qwaitcondition_unix.cpp2
-rw-r--r--qtools/qxml.cpp18
7 files changed, 30 insertions, 30 deletions
diff --git a/qtools/qdatastream.cpp b/qtools/qdatastream.cpp
index 8505dd4..70bcab1 100644
--- a/qtools/qdatastream.cpp
+++ b/qtools/qdatastream.cpp
@@ -381,7 +381,7 @@ void QDataStream::setByteOrder( int bo )
\fn void QDataStream::setVersion( int v )
Sets the version number of the data serialization format.
- In order to accomodate for new functionality, the datastream
+ In order to accommodate for new functionality, the datastream
serialization format of some Qt classes has changed in some versions of
Qt. If you want to read data that was created by an earlier version of
Qt, or write data that can be read by a program that was compiled with
diff --git a/qtools/qdict.doc b/qtools/qdict.doc
index d9f6ca5..d2e26c0 100644
--- a/qtools/qdict.doc
+++ b/qtools/qdict.doc
@@ -52,7 +52,7 @@
The key is used for inserting and looking up an item. QDict has
\l QString keys, which are Unicode strings. If you want to use
non-Unicode, plain 8-bit \c char* keys, use the QAsciiDict template.
- A QDict has the same performace as a QAsciiDict.
+ A QDict has the same performance as a QAsciiDict.
The dictionary has very fast insertion and lookup.
diff --git a/qtools/qstring.cpp b/qtools/qstring.cpp
index d831cb1..e04a852 100644
--- a/qtools/qstring.cpp
+++ b/qtools/qstring.cpp
@@ -13670,7 +13670,7 @@ QString &QString::replace( uint index, uint len, const QString &s )
/*!
Replaces \a len characters starting at position \a index by
- \a slen units ot QChar data from \a s, and returns a reference to the string.
+ \a slen units to QChar data from \a s, and returns a reference to the string.
\sa insert(), remove()
*/
diff --git a/qtools/qtextcodec.cpp b/qtools/qtextcodec.cpp
index bd874bb..842a72d 100644
--- a/qtools/qtextcodec.cpp
+++ b/qtools/qtextcodec.cpp
@@ -488,7 +488,7 @@ static bool try_locale_list( const char * const locale[], const char * lang )
}
// For the probably_koi8_locales we have to look. the standard says
-// these are 8859-5, but almsot all Russion users uses KOI8-R and
+// these are 8859-5, but almost all Russian users uses KOI8-R and
// incorrectly set $LANG to ru_RU. We'll check tolower() to see what
// tolower() thinks ru_RU means.
diff --git a/qtools/qvaluelist.doc b/qtools/qvaluelist.doc
index e4621d5..918d08e 100644
--- a/qtools/qvaluelist.doc
+++ b/qtools/qvaluelist.doc
@@ -139,7 +139,7 @@
In addition you can search items in the list with the find() function. It exists in a const
and a non const version. It starts searching from the beginning of the list, but another
flavor of the find() function allows you to specify where searching should start.
- If you just want to know wether a certain item is at least once in the list, then you
+ If you just want to know whether a certain item is at least once in the list, then you
can use the contains() function.
Since QValueList is value based there is no need to care about deleting elements in the
@@ -201,7 +201,7 @@
of this list become invalidated. Since QValueList is highly tuned for performance
you wont see warnings if you use invalid iterators,
because it is impossible for
- an iterator to check wether it is valid or not.
+ an iterator to check whether it is valid or not.
*/
/*!
@@ -258,16 +258,16 @@
/*!
\fn const T& QValueList::operator[] ( uint i ) const
Returns a const reference to the item with index \e i in the list.
- It is up to you to check wether this item really exists. You can do that easily
- with the count() function. However this operator does not check wether \e i
+ It is up to you to check whether this item really exists. You can do that easily
+ with the count() function. However this operator does not check whether \e i
is in range and will deliver undefined results if it does not exist.
*/
/*!
\fn T& QValueList::operator[] ( uint i )
Returns a reference to the item with index \e i in the list.
- It is up to you to check wether this item really exists. You can do that easily
- with the count() function. However this operator does not check wether \e i
+ It is up to you to check whether this item really exists. You can do that easily
+ with the count() function. However this operator does not check whether \e i
is in range and will deliver undefined results if it does not exist.
In contrast to the const operator[] you may manipulate the value returned by this
operator.
@@ -566,7 +566,7 @@
QValueList is highly optimized for performance and memory usage.
On the other hand that means that you have to be a bit more careful
by what you are doing. QValueList does not know about all its iterators
- and the iterators dont even know to which list they belong. That makes
+ and the iterators don't even know to which list they belong. That makes
things fast and slim but a bit dangerous because it is up to you to make
sure that iterators you are using are still valid. QListIterator will be able
to give warnings while QValueListIterator may end up in an undefined state.
@@ -627,7 +627,7 @@
\fn QValueListIterator<T>& QValueListIterator::operator++()
Prefix ++ makes the succeeding item current and returns
an iterator pointing to the new current item.
- The iterator can not check wether it reached the end of the list. Incrementing
+ The iterator can not check whether it reached the end of the list. Incrementing
the iterator as returned by end() causes undefined results.
*/
@@ -635,7 +635,7 @@
\fn QValueListIterator<T> QValueListIterator::operator++(int)
Postfix ++ makes the succeeding item current and returns
an iterator pointing to the new current item.
- The iterator can not check wether it reached the end of the list. Incrementing
+ The iterator can not check whether it reached the end of the list. Incrementing
the iterator as returned by end() causes undefined results.
*/
@@ -643,7 +643,7 @@
\fn QValueListIterator<T>& QValueListIterator::operator--()
Prefix -- makes the previous item current and returns
an iterator pointing to the new current item.
- The iterator can not check wether it reached the beginning of the list. Decrementing
+ The iterator can not check whether it reached the beginning of the list. Decrementing
the iterator as returned by begin() causes undefined results.
*/
@@ -651,7 +651,7 @@
\fn QValueListIterator<T> QValueListIterator::operator--(int)
Postfix -- makes the previous item current and returns
an iterator pointing to the new current item.
- The iterator can not check wether it reached the beginning of the list. Decrementing
+ The iterator can not check whether it reached the beginning of the list. Decrementing
the iterator as returned by begin() causes undefined results.
*/
@@ -680,7 +680,7 @@
list. It does not allow to modify the values of the list since this would
break the const semantics.
- For more informations on QValueList iterators see QValueListIterator.
+ For more information on QValueList iterators see QValueListIterator.
\sa QValueListIterator, QValueList
*/
@@ -733,7 +733,7 @@
\fn QValueListConstIterator<T>& QValueListConstIterator::operator++()
Prefix ++ makes the succeeding item current and returns
an iterator pointing to the new current item.
- The iterator can not check wether it reached the end of the list. Incrementing
+ The iterator can not check whether it reached the end of the list. Incrementing
the iterator as returned by end() causes undefined results.
*/
@@ -741,7 +741,7 @@
\fn QValueListConstIterator<T> QValueListConstIterator::operator++(int)
Postfix ++ makes the succeeding item current and returns
an iterator pointing to the new current item.
- The iterator can not check wether it reached the end of the list. Incrementing
+ The iterator can not check whether it reached the end of the list. Incrementing
the iterator as returned by end() causes undefined results.
*/
@@ -749,7 +749,7 @@
\fn QValueListConstIterator<T>& QValueListConstIterator::operator--()
Prefix -- makes the previous item current and returns
an iterator pointing to the new current item.
- The iterator can not check wether it reached the beginning of the list. Decrementing
+ The iterator can not check whether it reached the beginning of the list. Decrementing
the iterator as returned by begin() causes undefined results.
*/
@@ -757,7 +757,7 @@
\fn QValueListConstIterator<T> QValueListConstIterator::operator--(int)
Postfix -- makes the previous item current and returns
an iterator pointing to the new current item.
- The iterator can not check wether it reached the beginning of the list. Decrementing
+ The iterator can not check whether it reached the beginning of the list. Decrementing
the iterator as returned by begin() causes undefined results.
*/
diff --git a/qtools/qwaitcondition_unix.cpp b/qtools/qwaitcondition_unix.cpp
index d1ff27e..0a6a09b 100644
--- a/qtools/qwaitcondition_unix.cpp
+++ b/qtools/qwaitcondition_unix.cpp
@@ -67,7 +67,7 @@ class QWaitConditionPrivate
code = pthread_cond_wait(&cond, &mutex);
if (code == 0 && wakeups == 0)
{
- // many vendors warn of spurios wakeups from
+ // many vendors warn of spurious wakeups from
// pthread_cond_wait(), especially after signal delivery,
// even though POSIX doesn't allow for it... sigh
continue;
diff --git a/qtools/qxml.cpp b/qtools/qxml.cpp
index 806bd42..072997e 100644
--- a/qtools/qxml.cpp
+++ b/qtools/qxml.cpp
@@ -44,7 +44,7 @@
// NOT REVISED
// Error strings for the XML reader
-#define XMLERR_OK "no error occured"
+#define XMLERR_OK "no error occurred"
#define XMLERR_TAGMISMATCH "tag mismatch"
#define XMLERR_UNEXPECTEDEOF "unexpected end of file"
#define XMLERR_FINISHEDPARSINGWHILENOTEOF "parsing is finished but end of file is not reached"
@@ -226,28 +226,28 @@ QString QXmlParseException::message() const
return msg;
}
/*!
- Returns the column number the error occured.
+ Returns the column number the error occurred.
*/
int QXmlParseException::columnNumber() const
{
return column;
}
/*!
- Returns the line number the error occured.
+ Returns the line number the error occurred.
*/
int QXmlParseException::lineNumber() const
{
return line;
}
/*!
- Returns the public identifier the error occured.
+ Returns the public identifier the error occurred.
*/
QString QXmlParseException::publicId() const
{
return pub;
}
/*!
- Returns the system identifier the error occured.
+ Returns the system identifier the error occurred.
*/
QString QXmlParseException::systemId() const
{
@@ -403,7 +403,7 @@ void QXmlNamespaceSupport::splitName( const QString& qname,
and looking it up among the prefixes currently declared.
First parameter is the raw XML 1.0 name to be processed. The second parameter
- is a flag wheter the name is the name of an attribute (TRUE) or not (FALSE).
+ is a flag whether the name is the name of an attribute (TRUE) or not (FALSE).
The return values will be stored in the last two parameters as follows:
<ul>
@@ -1079,7 +1079,7 @@ finished:
\fn bool QXmlErrorHandler::error( const QXmlParseException& exception )
A reader might use this function to report a recoverable error. A recoverable
- error corresponds to the definiton of "error" in section 1.2 of the XML 1.0
+ error corresponds to the definition of "error" in section 1.2 of the XML 1.0
specification.
The reader must continue to provide normal parsing events after invoking this
@@ -5652,7 +5652,7 @@ parseError:
head stands on the first character after the reference.
charDataRead is set to FALSE if the reference must be parsed. The
- charachter(s) which the reference mapped to are inserted at the reference
+ character(s) which the reference mapped to are inserted at the reference
position. The head stands on the first character of the replacement).
*/
bool QXmlSimpleReader::parseReference( bool &charDataRead, EntityRecognitionContext context )
@@ -5943,7 +5943,7 @@ bool QXmlSimpleReader::processReference( bool &charDataRead, EntityRecognitionCo
}
} else {
// "Unparsed"
- // ### notify for "Occurs as Attribute Value" missing (but this is no refence, anyway)
+ // ### notify for "Occurs as Attribute Value" missing (but this is no reference, anyway)
// Forbidden
d->error = XMLERR_UNPARSEDENTITYREFERENCE;
charDataRead = FALSE;