NEWS update for 3.13.5
Post-release version bump
Updated German translation
Bug 735311 - Adapt to new Google HTTP restriction

Google has recently imposed a limit on the number of unauthorized HTTP
requests to its OAuth2-based interfaces.

The normal operation of SoupSession is to issue the first HTTP request
unauthorized and see if the server issues a "401 Unauthorized" response
(since not all HTTP services require authorization).

On a "401 Unauthorized" response, SoupSession emits an "authenticate"
signal, which the application is supposed to handle.  Once credentials
are in hand, SoupSession resends the same HTTP request and subsequent
requests with an Authenticate header while the socket connection holds.

Google's unauthorized request limit breaks this logic flow.  Once the
limit is exceeded, the Google server issues a "403 Forbidden" response
instead of "401 Unauthorized" to an unauthorized HTTP request.  This
breaks error handling in the E-D-S CalDAV backend.

The workaround is to preload the SoupAuthManager with a pre-configured
SoupAuth when using OAuth 2.0 authentication.  This avoids the initial
unauthorized HTTP round-trip.

The backend implements the GInitable interface for this since obtaining
a valid access token is a failable step.
CamelDB: Allow nested transactions

There could happen a deadlock when the code tried to do nested transactions,
which might be observed in the ancient migration from mbox to maildir
for local folders sometimes, not talking that the BEGIN/COMMIT cannot be
nested in SQLite, thus this change allows nested transactions. A similar
deadlock could happen when the caller had a write lock on the database
and requested a read lock, which is covered by this change as well.
Bug 486018 - Implement IDNA (Internationalized Domain Names in Applications)
Bug 734853 - CamelNetworkService fails to connect to 'localhost'

A regression after a change for bug 731585.
Bug 694112 - Crash under e_book_backend_ldap_stop_book_view()
Bug 735523 - Migrate sync_data from EBookBackendSqliteDB to EBookSqlite

We migrated the is_populated field, but not sync_data. EWS will need that.
Bug 735191 - [IMAPx] Avoid storing server-disallowed message flags
Build libedbus-private.la as a shared library

This fixes an issue under Win32, where symbols from library are
linked multiple times into the final executable (like into
evolution-source-registry), which causes a runtime error about
registering EDBusObject type multiple times on start.
Bug 733733 - Crash due to write out of buffer in CamelMimeFilterToHTML
Do not add GTasks source when the GTasks backend is not built

It was causing an error "Unable to connect to 'Tasks': No backend
factory for hash key 'gtasks:VTODO'" when this source was selected
in UI, because the source was added unconditionally, while
the backend itself is built with libgdata 0.15.1+ only.
Bug 735523 - test-book-client-custom-summary: Add 'exists' tests

... for email and X509 certificates.
Bug 735523 - EBookSqlite: Support 'exists' queries from summary
Bug 735523 - EBookSqlite: Support boolean summary field for EContactCert

We don't actually care about summarising the *data*; merely indicating
the *presence* of the field is sufficient. With the new evolution-pkcs11
module, the 'exists(x509Cert)' query is going to get very hot...

This halves the time it takes to query the Intel global addressbook,
with almost quarter of a million entries of whom about 5% have
certificates listed.
Bug 735523 - EBookSqlite: Enable x509Cert summary field by default

Again, evolution-pkcs11 is going to make 'exists(x509Cert)' a *hot* query...
Bug 735200 - [IMAPx] Fails to handle QUOTA response with no quotas

The untagged QUOTA response includes a list containing quota usage and
limits for each quota resource for which a limit applies. Per RFC 2087
section 5.1, "The list contains zero or more triplets.".

Fix the parser to handle an empty list. Additionally, when the IMAP
server supports the quota extension but reports no quotas for a folder,
return G_IO_ERROR_NOT_SUPPORTED rather than G_IO_ERROR_NOT_FOUND, since
Evolution (and maybe other callers) special-cases the former error code.
Updated Assamese translation
Bug 735523 - Allow EBookSqlite to be used without transactions

If we use it without grouping changes into transactions by using
e_book_sqlite_lock(), and if we have a cancellation in the calls to
actually make the changes, then this warning triggers because the
new cancellation doesn't match the NULL that we have stored for the
non-existent overall transaction.

Yes, we probably ought to be using locking in EWS but we're not. It's
perfectly valid to make changes without a transaction lock. Shut up
about it.