aboutsummaryrefslogtreecommitdiffstats
path: root/src/modules/window
diff options
context:
space:
mode:
authorGravatar un1versal2015-12-09 16:03:50 +0000
committerGravatar un1versal2015-12-19 02:40:23 +0000
commitc74db9aba4814ccb4dc0ac1e4c7e4ef7589f50a9 (patch)
tree1be38d394b47be8408585a00b2c67819bcf37082 /src/modules/window
parentsrc/modules: typos, consistency capitalize, fomatting and indenting fixes (diff)
downloadKVIrc-c74db9aba4814ccb4dc0ac1e4c7e4ef7589f50a9.tar.gz
KVIrc-c74db9aba4814ccb4dc0ac1e4c7e4ef7589f50a9.tar.bz2
KVIrc-c74db9aba4814ccb4dc0ac1e4c7e4ef7589f50a9.zip
various files: typos/consistency and capitalization see notes below.
https://techbase.kde.org/Projects/Usability/HIG/Capitalization This was just done last minute over some notes I had made during earlier similar fixes. * dont capitalize prepositions/conjunctions with less than 5 letters + fix wrong plural. * freenode is all lowercase instance only. * tooltips are not Camel Case capitalization style either. * some centered text on a dialog when all the etxt is left aligned looks off, tootips we can give a pass to. * Tree items are Camel Case * Typos in Unknow channel modes * more tooltips in the Channel Mode/Ban Masks/Invite but flawed design on these The tooltips text doubles up as title one isnt capitalized and the other is... So now none are in this area only since unlike toolbars thers no test display here and its passable. Alternative is to fix these dialogs and toolbars and tbh I cant do it. * cannot vs can't : these are consistency fixes for strings and debug messages only. * about dialog group titles "Runtime Info" "Build Info" are Camel Cased as per capitalization guidelines, but label are like all other labels. s spaces tyyt
Diffstat (limited to 'src/modules/window')
-rw-r--r--src/modules/window/libkviwindow.cpp20
1 files changed, 10 insertions, 10 deletions
diff --git a/src/modules/window/libkviwindow.cpp b/src/modules/window/libkviwindow.cpp
index 97cdc276f..6879b4287 100644
--- a/src/modules/window/libkviwindow.cpp
+++ b/src/modules/window/libkviwindow.cpp
@@ -232,7 +232,7 @@ static bool window_kvs_cmd_undock(KviKvsModuleCommandCall * c)
the current window is activated. If the specified window
does not exist a warning is printed unless the -q switch is used.
Please note that if the window is currently docked to a frame then this
- command will NOT raise the frame window. If you're interested in
+ command will [b]not[/b] raise the frame window. If you're interested in
the user's attention then you might be interested in [cmd]window.demandAttention[/cmd].
@seealso:
[cmd]window.demandAttention[/cmd]
@@ -747,7 +747,7 @@ static bool window_kvs_cmd_listtypes(KviKvsModuleCommandCall * c)
@syntax:
$window.list(<type>[,<irc_context_id>])
@description:
- Returns an array of window identifiers with a speficied type and eventually belonging to a specified
+ Returns an array of window identifiers with a specified type and eventually belonging to a specified
irc context.[br]
<type> is a window type such as 'query' or 'channel'.[br]
See [cmd]window.listtypes[/cmd] for a list of available window types in this KVIrc release.[br]
@@ -972,9 +972,9 @@ static bool window_kvs_fnc_list(KviKvsModuleFunctionCall * c)
to any context) and will exist until it is closed by the GUI, by a [cmd]window.close[/cmd]
call or until KVIrc terminates. When <irc_context> is given but is not valid
then a warning is printed (unless the q flag is used) and the created window is context free.[br]
- You will generally use the [fnc]$context[/fnc] function to retrieve the current IRC context id.[br]
+ You will generally use the [fnc]$context[/fnc] function to retrieve the current IRC context ID.[br]
[br]
- <icon> is intepreted as the index of the internal icon to be used
+ <icon> is interpreted as the index of the internal icon to be used
for the window. If <icon> is omitted then a default icon is used.[br]
@examples:
[example]
@@ -1282,7 +1282,7 @@ static bool window_kvs_cmd_setBackground(KviKvsModuleCommandCall * c)
window.savePropertiesAsDefault [window_id]
@description:
Saves the window properties of the specified window as default for every window
- of the same type (eg: all queries, all channels, ..).
+ of the same type (e.g. all queries, all channels, ..).
If window_id is missing then the current window properties are used.
*/
@@ -1358,7 +1358,7 @@ static bool initializeCryptEngine(KviCryptEngine * eng,KviCString &szEncryptKey,
then any current encryption engine is removed (i.e. encrypting is disabled).
The must be both expressed in hexadecimal notation and are internally transformed in bytes.
If only the encrypt key is specified then it will be used for both encrypting and
- decrypting. This command works only if crypt support is compiled in.
+ decrypting. This command works only if cryptography support is compiled in.
@examples:
[example]
[comment]# This is a really lame example :D[/comment]
@@ -1434,11 +1434,11 @@ static bool window_kvs_cmd_setCryptEngine(KviKvsModuleCommandCall * c)
if(szError.isEmpty())szError = __tr2qs("Unknown engine error");
g_pCryptEngineManager->deallocateEngine(e);
if(!c->hasSwitch('q',"quiet"))
- c->warning(__tr2qs("Failed to initialize the specified crypt engine: %Q"),&szError);
+ c->warning(__tr2qs("Failed to initialize the specified encryption engine: %Q"),&szError);
}
} else {
if(!c->hasSwitch('q',"quiet"))
- c->warning(__tr2qs("The crypt engine \"%Q\" doesn't exist"),&szEngine);
+ c->warning(__tr2qs("The encryption engine \"%Q\" doesn't exist"),&szEngine);
}
}
#else
@@ -1455,11 +1455,11 @@ static bool window_kvs_cmd_setCryptEngine(KviKvsModuleCommandCall * c)
@title:
$window.cryptEngine
@short:
- Returns the name of the crypt engine currently set in a window
+ Returns the name of the encryption engine currently set in a window
@syntax:
$window.cryptEngine(<window_id:integer>)
@description:
- Returns the name of the crypt engine set in the current window.
+ Returns the name of the encryption engine set in the current window.
If no current engine is set then empty string is returned.
@seealso:
[cmd]window.setCryptEngine[/cmd]