| Summary: | Implementation of a checkbox to choose the TM, if more than one present | ||
|---|---|---|---|
| Product: | [Applications] lokalize | Reporter: | Valter Mura <valtermura> |
| Component: | translation memory | Assignee: | Simon Depiets <sdepiets> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | aacid, adrian, fin-w, karl, mvillarino, shafff |
| Priority: | NOR | ||
| Version First Reported In: | 24.08.3 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Valter Mura
2024-12-18 17:16:23 UTC
So, are you thinking e.g. to uncheck a TM in the manager, and then no longer see results from that TM in the Translation Memory view in an editor? And to have the TM checked / unchecked statuses linked to the currently open Project? (In reply to fin-w from comment #1) > So, are you thinking e.g. to uncheck a TM in the manager, and then no longer > see results from that TM in the Translation Memory view in an editor? And to > have the TM checked / unchecked statuses linked to the currently open > Project? Yes, this is what I mean. For most projects, I would prefer too see results from *all* or *most of* my TMs, to ensure consistent translations *across* projects. But for a few, I would only want to see results from the project-specific TM(s). Remembering to enable all (new) TMs for each (small) project would be quite a lot of work. The following would work for my use case, and perhaps the bug reporter too: Have a list of checkable *default* TMs in the (not project-specific) Lokalize settings. By default, this would include all TMs, and when a new TM is added, it would automatically be added here. For each *project*, have a list of checkable/uncheckable TMs. One of them would be the ‘meta-TM’ called ‘Defult translation memories’, and would correspond to the Lokalize default TMs. *** Bug 322559 has been marked as a duplicate of this bug. *** *** Bug 257626 has been marked as a duplicate of this bug. *** |