Settings: HU translation

Change-Id: I8bb82b003486674caaaaca80e3cef3f2989e1815
Settings: RU translation

Change-Id: I45b12b4e7d42f571f6ef5b9f05f1f874c02d01cb
Merge "Settings: HU translation" into cm-10.1
merge changes from remotes/github/cm-10.1 into master
Squash Dark UI commits from Slim

Settings: Add new configuration qualifier for UI change on the fly (3/3)

last night I got an idea after 5 weeks of breaking stuff and
doing to much complicated things. Together with mnazim we tried
today to realize this idea. So another absolut new unique SlimBean
feature is born.

The aim we wanted at the end was to give a simple and resource friendly
way to change the complete UI of a rom on the fly. So why not use
the great fallback mechanism of AOSP and change/add a new
qualifier into the AOSP core. To explain how it works.....if you want
to add a new UI just add in /res folder of any app or framework you want
folders with the qualifier "inverted". Eg. drawable-inverted-xhdpi
or values-inverted or layout-port-inverted or whatever you want. Put in
only the files you want to modify thats it.

All qualifier in AOSP are following strict rules. You can read here.
Do not forget the order of qualifier is important. The new "inverted"
qualifier we added to the UIMode qualifier. To get more information
about read here

http://developer.android.com/guide/topics/resources/providing-resources.html

So what this commit does:
- add new qualifier "inverted"
- support for API level 13 and higher
- change the custom UI on the fly
- control default UI Mode over config.xml
- working for all apps. They just need to include folders
  with the new qualifier name
- resource friendly....no resource wasting either programmticaly
  then source blow, because you just need to put in the files you
  want to change
- cause of the qualifier structure compatible with every phone,
  language or whatever qualifier you want to use on top
- 100% compatible to theme manager. If a theme misses drawables
  they are replaced with them from the current UIMode which is set.

What is the benefit why not use just a theme? We started half year
ago TRDS which was inverted gapps system base themed....means we
morphed directly the changes into the framework. This methoed was
on of the reasons why trds got so popular. Points for that are easy
first the system is themed, means each theme you activate over
theme engine works on top the themed system. So you have a base
style and can modify more if you want. The other reason is easy
a lot faster and resource friendly. Now this idea went to the
rom to provide two core system based themes and user
can do on top what they want or not without, like you have

This commit just adds the support for this

cheers

mnazim and kufikugel

Change-Id: I401dabcb3691446aa7886c8601245f2cd2db71b8

Conflicts:
	res/values/strings.xml
	res/xml/settings_headers.xml
	src/com/android/settings/Settings.java
	src/com/android/settings/slim/UserInterface.java

Settings: Kill specific apps on TRDS toggle change

to take 100% effect on the new style

Gmail, email, Playstore and contacts

Patchset:
- cleanup

Change-Id: I563307ecffe47087d19145b90b15dd58438520d8

Settings: Add to be sure also some other apps for TRDS toggle

cheers

Change-Id: I20eafdcf38bf8031d6e6d69c7403fa44bfd220b9

Conflicts:
	res/values/strings.xml
	res/xml/settings_headers.xml
	src/com/android/settings/Settings.java
Settings: TRDS 2.0 (3/3)

After testing with huge success we discovered here
and there small problems (like NFC beam animation is broken,
TRDS was disabled on cardock etc) which mainly was caused
due that we used the already from AOSP introduced uiModes
qualifier which could cause in special conditions this
conflicts. Beside that we want a bit more flexibility.
Result: This commit introduces the inverted qualifier as
complete own qualifier undependent of the already AOSP
used ones.

Beside that it fixes all known issues......features:

- it is now completly working over the AOSP Configuration classes
  Means every app get notice of a change trough onConfiguratioChange
  and restarts it's activity if change was detected.
- app can disable that like some other configuration values
  over AndroidMainfest.xml
- beside "inverted" folder another "notinverted" folder is introduced
  for another themeing (eg white)
- qualifier order is direct before the official uiMode qualifiers
  (see AOSP docs)
- All usual Configuration actions can be used with the inverted
  qualifiers....like BroadcastChange, direct read out from every
  app etc. etc. Note: Only system can change the uiInvertedMode

So as you see a real own qualifier now

NOTE: Apktool as well aapt need to be changed to fit the "new
qualifier"....which means that we need to recompile our gapps
that they react as well on this new behaviour. Think we will get them ready
next 2 or 3 days

Change-Id: I6ac22062e32be902ca834fc7ac2b12fd24e47d44

Conflicts:
	src/com/android/settings/TRDSEnabler.java
Settings: refactor TRDS toggle and add some apps

cheers

Change-Id: I9b0a9b527fd0c2cac20d2b5475c8709a9fda1936
Fix Derp

Change-Id: Id5bbd278116b59a73263357a837b3e8ce8a5c345
Restore original TRDS icons from Slim

Change-Id: I24a083c3639895fdc591ad2adef0c4e1a320a663
Fix not functional recents button after toggling TRDS by sending device into sleep

Change-Id: I6a578c206c072a0c0622519c5de8795f5befc49f
Name TRDS as Dark UI

Change-Id: I17a2342d16acc06fcb1e1c71de5e6401f53d078a
Fix Derp

Change-Id: Iaa298deac0b733ab5d3f1da4b1f54b0b9607f20e