Documentation translations. Criticize the dictionary of terms?

Question

Machine translation from one language to another

Not so long ago, I started translating the AngularJS documentation and are slowly compiling a reference book of concepts . There are a few specific concepts in there, but mostly things that are found all over the place in design patterns and similar places. Criticize, please; offer your options, especially in concepts with question marks.
By the way, the simplest option is not to translate a complex concept, but then the document will be fake runglish , and we are still going the way of the samurai :-)
Working version:
angular - Angular|Angular'а|Angular'у (not translated. It is always written with a capital)
Angular application- angular application (if it is obvious from the text that we are not talking about any other application, then the word angular can be omitted)
callback - callback (callback function is too cumbersome)
CamelCase - Camel Case
collection - collection
compile function - compilation function
data binding - data binding. Another option is data binding. More common, but by linking, you can also translate concepts that include linking ???
deep-linking - external linking
deffered - debtor, debt. Those. the one who makes the promise becomes the debtor. In some contexts, it is acceptable to translate as deferred or deferred.
dependency injection
- end-to-end (E2E) test dependency injection - system testing (complex is a less common option, so you should replace it with a more common system test in all documentation).
evaluate - calculation ???
getter - a getter (I don't like the concept, but it seems to have settled down, but this is the recipient)
injector - an injector? is there a proper definition?
instantiates - create an instance, instantiate, etc.
interpolation - transformation? interpolation function - transforming function???
link - linking Another option: linking, but reproducing with binding ???
link function- linking function (Closer to the original and echoes the compilation function). Another option: the layout function, because its result is an entire entity: a directive. While binding only binds data.
locale - locale. Sometimes regional
settings are better . _ _ _ _ _ (The old version is optionally worth cutting out) polyfill - promise crutch - promise, promise, promised, depending on the context repeater






— repeater ??? Or better breeder. We need to think about
a round-trip application - a multi-page application
scope - scope (??? I think this is a good definition for scope in the context of angular? Since here we are talking more about a special object, and not about JavaScript scope ( maksimr ) Also in doubt. Moreover, there is the concept of scope object. Maybe it's better not to translate at all ( tamtakoe ))
see - see (abbreviate in notes, etc. That is, almost always.)
see for more details - see also
setter I don’t like the concept, but it seems to have settled down, and this is the installer)
single-page application - single-page
transclusion application- inclusion ???
unit test - unit testing (unit testing is not in Russian)
user experience - operating experience
view (a concept from the MCV template) - view. Sometimes the word representation is better, the main thing is to clarify that this is the same thing.
watches - observers ??? not good, because echoes with the observer. watch is an observer of a variable in scope.
widget - widget

Answer 1

It seems to me that terms that are not subject to translation should be written in the text not in transliteration, but in the original: I'm talking about callback (you did exactly that with angular), while the glossary of terms should contain an explanation of the meaning of this word.

Answer 2

With terms that you doubt the translation of, it would be nice to provide at least a little context. For example, evaluate , in addition to finding the value of a value, it can also mean evaluation (evaluate); data binding - after all, data binding, not binding.

Answer 3

CamelCase - Camel
Notation locale - also mock localization
, mock implementation - imitation, "stub"
deffered - also delayed
deep-linking - it seems to me deep linking, internal linking is possible
evaluate - calculation, in different contexts also execution

Answer 4

There is an error in deferred: there should be 2 "r" in the word instead of 2 "f". And "w" instead of "v" in lowerCamelCase.