Updated FSF's address
Updated Traditional Chinese translation(Hong Kong and Taiwan)
Remove trivial code to toggle an action.

GAction now does that for us in the default handler
Use dash in gaction names
Revert "gedit-app: use g_option_context_parse_strv()"

This reverts commit 0e82694a539de3017aa62e09cf32f4016f3df465.

It turns out that things are actually trickier and we rely on the
fact that the original array is left alone. For now we revert so
that "gedit foo.txt" works again, but we should revisit this once
https://bugzilla.gnome.org/show_bug.cgi?id=721977 lands in glib
I missed the accels when changing action names
Show a warning on remote docs if network goes down

Used GNetworkMonitor to show an info bar warning if using a remote
doc and network is down
Expand the preferences dialog tabs
ViewFrame: select text in the search entry

Steps:
- Ctrl+F and search for 'something', with a least one match
- the match becomes selected in the buffer
- press Enter to quit the search
- press Ctrl+F again
- the search takes the buffer selection to put it in the search entry

What the code did in this case is to put the cursor at the end of the
search text (in the search entry). Now it selects the text.

https://bugzilla.gnome.org/show_bug.cgi?id=723267
ViewFrame: down and up buttons always sensitive

With gedit 3.8, the down and up buttons were always sensitive. For 3.10
I wanted to improve the situation, but it was a bad idea, as described
in the bug:

https://bugzilla.gnome.org/show_bug.cgi?id=722965
Updated Hebrew translation.
Updated Brazilian Portuguese translation
Another missing _ to - conversion
Move the show-tabs-mode property to MultiNotebook

This is needed to make sure we always show the tabs when we have
more than one notebook
Allow plugins to extend the appmenu

Rename the API to just be extend_menu instead of extend_gear_menu
and look for the requested extension point in all the menus we have.
Plugins are updated for the API change and snippets and tools now
put their pref dialogs in the app menu.
We still need to rename all the extension points to something more
meaningful of "ext1" and we probably should add similar API to the
app-actiavatable.
updated kn.po
Updated Thai translation
Updated Scottish Gaelic translation
ViewFrame: fix search triggering

Trigger the search when the search text is new.

When gtk_text_buffer_select_range() is called, the selection in the
search entry is lost. gtk_text_buffer_select_range() is called when the
search is triggered (i.e. when the buffer is searched).

When the search text is the same, no need to trigger the search, and we
can select the text in the search entry, so the user can search for
something else. On the other hand, when the search text is new, we must
trigger the search, and we are not able to (easily) select the text in
the search entry. But it's not a problem, since the search text is new,
so the user doesn't want to search for something completely different,
he just perhaps wants to adjust a little the search text.
Move menu extension to the app-activatable

It is important that the menu-model for the gear menu is a single
instance shared among all the windows. This makes it consistent
with the app-menu model and plugins can extend them in the same
way without causing items to be added multiple times when there
is more than a window.
The extension API is thus moved to the app activatable interface
and the plugins are adapted to use the new api.