Sync with latest script

1 files changed, 10 insertions, 10 deletions

diff --git a/src/kernel/qinputcontext.cpp b/src/kernel/qinputcontext.cpp
index 8e71552c..557ef38e 100644
--- a/src/kernel/qinputcontext.cpp
+++ b/src/kernel/qinputcontext.cpp
@@ -152,7 +152,7 @@ public:
     Any input context can be shared between several text widgets to
     reduce resource consumption. In ideal case, each text widgets
     should be allocated dedicated input context. But some complex
-    input contexts retquire slightly heavy resource such as 100
+    input contexts require slightly heavy resource such as 100
     kilobytes of memory. It prevents quite many text widgets from
     being used concurrently.
 
@@ -162,7 +162,7 @@ public:
     shared input context. Other text widgets access the input context
     via TQApplication::locateICHolderWidget(). But the access
     convention is transparently hidden into TQWidget, so developers are
-    not retquired to aware of it.
+    not required to aware of it.
 
     What developer should know is only the mapping function
     TQApplication::locateICHolderWidget(). It accepts a widget as
@@ -180,7 +180,7 @@ public:
     method. It is ranging from 2-3 keystrokes of sequence in
     deterministic input methods to hundreds of keystrokes with
     semantic text refinement in complex input methods such as ordinary
-    Japanese input method. The difference retquires the different reset
+    Japanese input method. The difference requires the different reset
     policies in losing input focus.
 
     The former simple input method case, users will prefer resetting
@@ -228,7 +228,7 @@ public:
 
     \endlist
 
-    In the case, there are the following two retquirements that
+    In the case, there are the following two requirements that
     contradicts each other. The input context sharing causes it.
 
     \list
@@ -242,7 +242,7 @@ public:
     \endlist
 
     A intrinsic feature named 'preedit relocation' is available to
-    compromise the retquirements. If the feature is enabled for the
+    compromise the requirements. If the feature is enabled for the
     input context, it is simply moved to the new text widget with the
     preedit string. The user continues the input on the new text
     widget, or relocate it to another text widget. The preedit of
@@ -258,7 +258,7 @@ public:
     occurred. The feature is mainly existing as safety.
 
     The feature properly works even if the focus is moved as
-    following. Input method developers are not retquired to be aware of
+    following. Input method developers are not required to be aware of
     the relocation protocol since TQInputContext transparently handles
     it.
 
@@ -266,7 +266,7 @@ public:
 
     To enable the preedit relocation feature, the input context class
     have to reimplement isPreeditRelocationEnabled() as returns TRUE.
-    The implementation retquires that the preedit preservation is also
+    The implementation requires that the preedit preservation is also
     enabled since preedit relocation is a special case of the preedit
     preservation. If the preedit relocation is disabled, the input
     context is simply reset in the relocation case.
@@ -463,13 +463,13 @@ bool TQInputContext::isComposing() const
     The filtering opportunity is always given to the input context as
     soon as possible. It has to be taken place before any other key
     event consumers such as eventfilters and accelerators because some
-    input methods retquire quite various key combination and
+    input methods require quite various key combination and
     sequences. It often conflicts with accelerators and so on, so we
     must give the input context the filtering opportunity first to
     ensure all input methods work properly regardless of application
     design.
 
-    Ordinary input methods retquire discrete key events to work
+    Ordinary input methods require discrete key events to work
     properly, so TQt's key compression is always disabled for any input
     contexts.
 
@@ -779,7 +779,7 @@ TQString TQInputContext::identifierName()
     consistent with TQInputContextPlugin::language().
 
     This information will be used by language tagging feature in
-    TQIMEvent. It is retquired to distinguish unified han characters
+    TQIMEvent. It is required to distinguish unified han characters
     correctly. It enables proper font and character code
     handling. Suppose CJK-awared multilingual web browser
     (that automatically modifies fonts in CJK-mixed text) and XML editor