use intl's native normalizer_normalize() in case the module is available
Step one, open guest layout for different styles.

Conflicts:
	core/templates/layout.guest.php

Step one, open guest layout for different styles.
Do not double decode values

Fixes https://github.com/owncloud/core/issues/11012
remove icon styles from apps.css as they are in icons.css
use same shade of grey for active navigation items and hovering
Remove passing by reference to allow for proper GC

The garbage collector in PHP 5.3.10 does not properly release the file
handle when calling fclose() due to the fact that it is passed by
reference.
This has the side-effect of preventing file locks to be released as well
when the files_locking app is enabled.

This fix removes the useless passing by reference and now the file
handle and file lock are freed properly.
content size checks are not valid for LOCK
[tx-robot] updated from transifex
remove obsolete language files
Merge pull request #11054 from owncloud/fix-unit-tests-11041-master

content size checks are not valid for LOCK
[tx-robot] updated from transifex
Merge pull request #11050 from owncloud/enc-flockfix

Remove passing by reference to allow for proper GC
[tx-robot] updated from transifex
Merge pull request #11021 from owncloud/do-not-double-decode

Do not double decode values

* owncloud/do-not-double-decode:
  Do not double decode values
Merge pull request #10960 from owncloud/use-intl-module-master

use intl's native normalizer_normalize() in case the module is available
Merge pull request #11026 from owncloud/apps-styles-update

Apps styles update
Merge pull request #10109 from owncloud/issue_#9793_guestlayout

Step one, open guest layout for different styles.
Merge pull request #11060 from owncloud/rmobslang

remove obsolete language files
add function to invalidate one opcache file, use it if possible #9885

Issue #9885 appears to be triggered by ownCloud invalidating the entire
PHP opcache. Testing indicates it can be avoided by only invalidating the
single file that was written from the opcache, instead of clearing the
whole thing. In general it is more efficient to invalidate only the single
file that was changed, rather than the whole cache.

This adds a deleteFromOpcodeCache() function which invalidates a single
file from the opcache if possible, returning true if the underlying
function returns true (which may mean 'success', or 'file does not exist',
or 'file exists but is not in opcache', all of which are OK to treat as
good for our purposes). It also changes writeData() in config.php to try
using deleteFromOpcodeCache() and only fall back on clearOpcodeCache() if
that fails.