all menu items should have a default SVG. Template authors then can
decide if they want to use them or not.

These are only the page tool SVGs. More need to be added.

This is an attempt to:

* get rid of the super long, complex functions in in/template.php
* make it easy for plugin authors to add their own items to any
  of our menus, regardless of the used template
* continue the progress to make use of SVG in the menues

This takes a similar approach as my actionrefactor branch. Originially
I thought both refactorings could be done in one, merging the
functionality of DokuWiki actions and the menu items. However I couldn't
make it work. So instead we have two separate but similar things.
Maybe they can converge later on.

I used svgo to strip all unneeded cruft from the svgs

Now any arbitrary attributes can be passed as 4th argument. This way
classes etc could be added by plugins.

This will open up the discussion from #236 again and I'm not sure how to
solve this best.

The TEMPLATE_PAGETOOLS_DISPLAY event is very specific to the dokuwiki
template in theory. In practice many other templates implemented not
only the same event but also use the same HTML (and often even the same
CSS). Which makes the event more like a core event.

This branch now changes the HTML the event expects back from handlers.
When merged it would immeadiately break all plugins implementing this
event (and by broken I mean the layout/design of the template breaks).

Since the expected data changes, I would argue this should be a new
event or at least be implemented in a way to not break the design by
installing an old plugin and by giving the plugin a chance to know if
it's running on the old or the new code.

This is what this commit does. By changing the view names, old plugins
should not display (because they hopefull do not handle those views) but
gives them an easy way to handle the old and new views in one plugin.

However, I'm not perfectly happy with it, yet.

The way I implemented the new SVG handling is by means of a new class
dokuwiki\template\dokuwiki\tpl which provides a pageToolAction() method.
Plugins could use this method to easily return the proper HTML for the
pagetool items and we could adjust this method later on to make
adjustments to the pagetools without breaking anything again.

However this method is template specific again. While it would possible
for plugins to use this method even when the wiki runs another plugin
emitting the event, it would be a bit weird.

A better way would be for the event to not expect HTML at all, but
instead a data structure of the data currently passed to
pageToolAction(). Templates could then decide to implement the event,
but still render the data in a completely different way...

OTOH this means plugins are no longer free to add whatever they want
into the pagetools. We once argued plugins might want to add submenus or
other fancy stuff there. But in fact no plugin ever did.

If we decide to go this new way of making the event more of a first
class citizen of template development, then we would probably have to
move parts or all of the tpl class back to the core.

* master:
  translation update
  fixed typo in function name
  translation update

Translation update (ja)

Translation update (zh)

The whole pagetool items are now build in an extra helper class that can
be reused by plugins.

* master:
  support autoloading for templates

similar to what is possible for plugins, templates can now autoload
namespaced classes, too. the namespace is
dokuwiki\template\<templatename>

todos:

* edit action (and maybe others) use different icons depending on state,
  we can't rely on passing $post
* media details screen not adjusted, yet
* no RTL styles
* no focus/active styles
* the event needs to be adjusted (maybe throw it away and do a new one)
* some icons are not good (create = edit)
* possibly more

This makes it more flexible to use on the expense of needing one echo
more.

$pagelog->getRevisions(-1, 1) cannot be passed to array_pop() as the
parameter $array expects a reference.

remove fullpath() call in pageinfo

 added rev number to most recent link in old revisions page

All script tags are now surrounded by conditional comments to tell
Internet Explorer 8 and lower to not even bother trying to load the
JavaScript.

* jqsplit:
  Restore smoothness.css using update.sh
  allow selecting the preferred CDN and add event
  load jquery via https always
  split off jquery from other JS and add CDN option #1766
  use external version file for jquery updates
  removed jQuery.browser calls
  replace deprecated bind() calls
  replace deprecated delegate() calls
  fixed radio options in media manager for new jQ-UI
  jQuery Updates

fix problems with header that look falsy. fixes #1770

Handle delayed writes gracefully

updated SimplePie and moved to composer based install. #1800

Admin Page refactoring

* use inline-block instead of flexbox
* fix RTL alignments

This reverts commit b8b60fdb.

The images are now to be seen as deprecated but will remain for a little
longer. They will be released in the future.

now comments and line breaks between tags are removed

Fix broken JS in xhtml

Add height: auto to video element css