Bug 42196

Summary: Improve usability of context view on kbabel
Product: [Unmaintained] kbabel Reporter: dwayne
Component: KBabel editorAssignee: Stanislav Visnovsky <visnovsky>
Status: RESOLVED UNMAINTAINED    
Severity: wishlist CC: cfeck
Priority: NOR    
Version First Reported In: 0.9.5   
Target Milestone: ---   
Platform: RedHat Enterprise Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description dwayne 2002-05-05 13:53:41 UTC 
(*** This bug was imported into bugs.kde.org ***)

Package:           kbabel
Version:           0.9.5 (using KDE 2.2.2 -1)
Severity:          wishlist
Installed from:    Red Hat Linux 7.2
Compiler:          gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)
OS:                Linux (i686) release 2.4.7-10
OS/Compiler notes: 

I woul dlove to see the context view play a more important role in kbabel.

I would like to see colours added to indicate translated untranslated fuzzy strings and error strings.

Users could filter the window to show only messages with errors fuzzy untranslated or a combination.  This would help in that a combined next button would take them to the strings they are interested instead of the current multiple complicated combinations to jump between strings.

Eventually this window might be used to show strings in all PO files and allow users to move quickly to them.

Another added advantage woul be if you could select all strings <= 4 words and focus only on those.  This is usefull when bringing a language into KDE as you can make rapid progress on areas that are probably more visible to the end user.

Other filters could be all strings that contain accelerators all strings that do not contain <html> or <qt> tags.

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)
Comment 1 Stanislav Visnovsky 2002-09-26 11:53:41 UTC 
Moved to KBabel component in Bugzilla
Comment 2 Christoph Feck 2011-06-26 14:10:11 UTC 
KBabel is no longer maintained, please use the KDE 4 translator's tool called
"Lokalize" instead. For more information, please visit
http://userbase.kde.org/Lokalize

If this is a request for a feature which is also missing in Lokalize, please add a comment so that I can reassign the request to the Lokalize authors. You could also file a new request for Lokalize.