Bug 329710 - Innacurate text on whatsThis strings
Summary: Innacurate text on whatsThis strings
Status: RESOLVED FIXED
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.4
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-08 03:05 UTC by André Marcelo Alvarenga
Modified: 2015-09-06 04:06 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description André Marcelo Alvarenga 2014-01-08 03:05:03 UTC
1)
#: src/irc/channellistpanelui.ui:186


"You can limit the channel list to those channels with a minimum number of "
"users here. Choosing 0 disables this criterion."

Should be:

"You can limit the channel list to those channels with a minimum number of "
"users here. Choosing 'No limit' disables this criterion."

or similar text, since I can't set '0'.

2)
#: src/irc/channellistpanelui.ui:205

"You can limit the channel list to those channels with a maximum number of "
"users here. Choosing 0 disables this criterion."

Should be:

"You can limit the channel list to those channels with a maximum number of "
"users here. Choosing 'No limit' disables this criterion."

or similar text, since I can't set '0'.


3) (minor change)

#: src/irc/channellistpanelui.ui:189 src/irc/channellistpanelui.ui:208

String: "No Limit"

The string on these spinboxs could be starting one or two pixels on the right, because they are very close to the left margin.

Reproducible: Always
Comment 1 argonel 2015-03-18 18:18:18 UTC
Git commit d9928962ee66a6320e6e6a86782e8545e0a6809c by eli mackenzie.
Committed on 13/03/2015 at 17:59.
Pushed by argonel into branch '1.6'.

Update limit strings in the channel list panel

The "whatsthis" help indicated 0 instead of
"No Limit".

M  +2    -2    src/irc/channellistpanelui.ui

http://commits.kde.org/konversation/d9928962ee66a6320e6e6a86782e8545e0a6809c
Comment 2 André Marcelo Alvarenga 2015-09-06 04:06:24 UTC
Already fixed in Konversation 1.6.