WeblateOrg / WeblateOrg/weblate
Ability to cycle through all search results (multiple components/languages) in translation view
- Dominant language
- Python
- Stars
- 6.1k
- Forks
- 1.4k
- Avg merge
- 9h 53m
- Merged PRs (30d)
- 395
Description
### Describe the problem
**Problem**
When searching for strings Weblate shows results in all components and languages in a single table, which is nice. However, when the user clicks on a source/target string on the search result table, the link goes to component+language scoped translation view where the user can cycle through only the results in the selected component+language. I.e. there is no way for the user/translator to cycle through all results found with the search filter if the search contains matches from multiple components and/or languages, and has to jump back and forth between searching and translation views. This makes translating cumbersome especially in projects where the project is divided into multiple components for technical reasons, but the strings/translations should be consistent across the whole project, like there would be only one component.
### Solution brainstorm
**Proposed solution**
Make the translation view inherit the cycle scope from the search. I.e: make translation links cycle through all results found with the current search filter.
- if the user searches on a project level and the search filter does not restrict component/language, by default the translation views should cycle through results found in all components and all languages.
- if the user searches on a component level, by default the translation views should cycle through results in all languages within that component
- if the user searches on a language level, by default the translation views should cycle through results in all components within that language
This way the cycle through is consistent with the search filter and the user knows what they are cycling through.
### Describe alternatives you have considered
_No response_
### Screenshots
_No response_
### Additional context
_No response_
Contributor guide
Assessment
This issue has not been assessed yet.