Strange scope of the untranslated langvars
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