Project

General

Profile

Bug #672

Strange scope of the untranslated langvars

Added by Marko Kastelic over 9 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Start date:
07/03/2010
Due date:
% Done:

0%

Estimated time:
Complexity:
Normal

Description

The scope is not limited to the language file previously selected but is extended to all language files of all the branches.
If this was an intention, please remove this post.
To test: select language, filter branch: select 1.8, use untranslated strings icon from the rightmost column, start translating ...
when you come to the last variable within selected language file, translate and select next untranslated /save and go to the next ... just watch breadcrumb where language file is displayed. If (alfabeticaly) the first language file with untranslated string is from 2.0 branch, variables from this file will be offered to translate .... i noticed that after i already translated about 10 langvars from admin/branch2.0 (started from exercise/branch1.8

History

#1

Updated by Stefaan Vanbillemont over 8 years ago

  • Target version set to 2.1.0
#2

Updated by Stefaan Vanbillemont over 7 years ago

  • Target version changed from 2.1.0 to Backlog (default)

Also available in: Atom PDF