Bug 257626

Summary:	several Translation Memories at one time: priorities, tm tab
Product:	[Applications] lokalize	Reporter:	mvillarino <mvillarino>
Component:	translation memory	Assignee:	Nick Shaforostoff <shafff>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	fin-w, lpapp
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description mvillarino 2010-11-22 18:44:44 UTC

Version:           unspecified (using KDE 4.4.5) 
OS:                Linux

Currently, you can only use a single translation memory (TM) at a time, furthermore. What I ask for is the possibility of using several concomitantly.
Say, for instance, one taken from a client or another software project and the "working TM" from the current project.
Furthermore, the results should be ordered according to the memory they came from, and the one with priority should be selectable.

Reproducible: Didn't try

Comment 1 Nick Shaforostoff 2011-01-16 19:24:40 UTC

currently the priority of TMs is taken into account only when comparing suggestions with otherwise equal similarity. you want this to be changed?

Comment 2 mvillarino 2011-01-17 08:10:39 UTC

As per now this is enough.
What version of Lokalize will include this functionallity?

2011/1/16, Nick Shaforostoff <shafff@ukr.net>:
> https://bugs.kde.org/show_bug.cgi?id=257626
>
>
>
>
>
> --- Comment #1 from Nick Shaforostoff <shafff ukr net>  2011-01-16 19:24:40
> ---
> currently the priority of TMs is taken into account only when comparing
> suggestions with otherwise equal similarity. you want this to be changed?
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>

Comment 3 Nick Shaforostoff 2011-01-17 11:52:52 UTC

4.5 (the previous) 100% has it

Comment 4 Nick Shaforostoff 2011-01-17 11:57:35 UTC

but the priorities thing is to be made explicit...

Comment 5 Finley Watson 2025-12-10 02:11:57 UTC


*** This bug has been marked as a duplicate of bug 497653 ***