Currently there is no mechanism for custom translations of Javascript tra(), i.e. there is no "custom.js". And the GUI for managing custom translation only cares about custom.php (and then lacks the array_merge -> array_replace at the end of custom.php).
Also I propose to handle comments in the language files, such as are automatically generated by my extractor scripts (cf. my "Create a tool..." feature request) in order to give translations a structure. It's not a real substitute for context, but helps translators to write translations when they know WHERE a particular string came from. Although this could be some kind of context, unfortunately PHP's logic breaks this, because with two subsequent definitions of a string's translation the latter always wins... So final string definition can become a mixture of different origins...
Currently there is no mechanism for custom translations of Javascript tra(), i.e. there is no "custom.js". And the GUI for managing custom translation only cares about custom.php (and then lacks the array_merge -> array_replace at the end of custom.php).
Also I propose to handle comments in the language files, such as are automatically generated by my extractor scripts (cf. my "Create a tool..." feature request) in order to give translations a structure. It's not a real substitute for context, but helps translators to write translations when they know WHERE a particular string came from. Although this could be some kind of context, unfortunately PHP's logic breaks this, because with two subsequent definitions of a string's translation the latter always wins... So final string definition can become a mixture of different origins...