fb: translation - RU

I81a7473ca48eb5fd91263ec63c82957d8b3ad17b

PS2: added quotes
Now really add :-[

Change-Id: Ic781d1bbd7dd3f73eb7e5a3fb19fd8d8f79463d6
fb: translation - RU

I61ef5afa32c5ff883129b9362423af7f724c5ac1

Change-Id: Ia507b7e3c404d374e07662869318601373696c51
fb: translation - RU

Torch renamed for consistency
Thanks @zujasehet

Change-Id: I635d797d6a3bb3ba8ea3fec9a609935ecd1903d3
Frameworks: ES translations

PS2: Remove tabs

Change-Id: Iff57b01dc36e2d3b4b2e3bba9ee18cc407215687
Slim Heads up: change behaviour of back key

Currently back key hides the heads up. We change it that the back key is still
working for the app which has focus and not for the heads up at all.

Reasons:

1. A lot user requested this due that they often hide the heads up during they work
   on the phone, simply due that the back button is often pressed on a normal workflow.
   The results is indeed that a lot heads up windows are missed excidentaly.

2. First I thought to make it optional. But there is another big reason to do it this way. Current
   behaviour is that the heads up view gets focus...and that we dispatch the back key only. Thing is
   that other key events are still rooted to the heads up window. Well most things a user will not see.
   But eg on apps with input field some keys on the IME keyboard do not work during the heads up is showing
   which is a big no go when we assume that heads up needs to be as much non intrusive as possible.

That being said we remove the dispatch override and give the heads up window FLAG_NOT_FOCUSABLE flag
which will bypass any key events to the window behind which had focus before the heads up showed up.

FLAG_NOT_TOUCH_MODAL we can remove due that FLAG_NOT_FOCUSABLE automatically enables the FLAG_NOT_TOUCH_MODAL flag.

Change-Id: Ied4c7d2dd5b99f89af958f01db980a36d431bbc3
Merge "Slim Heads up: change behaviour of back key" into kk4.4-caf
Merge remote-tracking branch 'slim/kk4.4-caf' into kk4.4-caf