https://bugs.kde.org/show_bug.cgi?id=491111
Bug ID: 491111
Summary: Feature request: Quick search/lookup in translation
units
Classification: Applications
Product: lokalize
Version: unspecified
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: editor
Assignee: sdepi...@gmail.com
Reporter: k...@huftis.org
CC: aa...@kde.org, sha...@ukr.net
Target Milestone: ---
SUMMARY
When translating, I often want to look up how I have translated a word or a
phrase in *other* messages in the same .po file. For this, I usually use the
filter in the ‘Translation Units’. However, this has two problems:
1. It filters the list of ‘active’ messages, so ‘Page Up’/‘Page Down’ will move
to the next filtered message. This means that I have to manually reset the
filter after looking up each word/phrase.
2. It only shows the first few words of the source/translation strings, which
will often not contain the text I have searched for. To see the complete
translation, I have to click on the entry (thus leaving the entry I’m currently
translating), read the translation and then navigate back to the original.
This is a feature request for a new ‘Quick Lookup’ pane which should work like
the ’Translation Units’ pane, but with the following changes:
1. It should not change the list of ‘active’ messages.
2. Its content should not change when moving between messages.
3. It should have a *multi-line* view for each entry, so that we can see the
entire messages.
4. The search text should preferably be highlighted in the source/translation
texts (e.g., in bold).
5. By default, it should only have the ‘Source’, ‘Target’ and ‘Translation
status’ columns visible, as these are the most useful ones. (And I think by
default it should only show non-fuzzy translations.)
Some possible additional features (not required, at least not in initial
implementation, but could be nice improvements):
6. Not strictly necessary, but perhaps it would be nice if there were *two*
search fields, one for ‘Source’ and one for ’Target’? One usually only wants to
search in one of them.
7. At the bottom of the filtered list, show entries from the glossary too (but
clearly marked as such, e.g., with a ‘Glossary’ heading). This is useful when
there are *few* matching entries in the current file.
8. At the bottom of the filtered list (after the glossary entries), show
entries from the translation memory (with a ‘Translation Memory’ heading).
If the last two features were implemented, there should be an option to disable
them. I think a good solution would be to have a ‘Lookup Sources’ submenu under
the ‘Options’ button with checkboxes for ‘Translation Units’, ‘Glossary’ and
‘Translation Memory’. (Then some people can choose to use the ‘Quick Lookup’
feature to search *only* in the glossary or *only* in the TM.)
--
You are receiving this mail because:
You are watching all bug changes.
