[downloadable] fix filename in HTTP header (closes #2522325, #2522324) Before this changeset we use the `filename` header with utf8 encoded filename all the time. However RFC6266 says: The parameters "filename" and "filename*" differ only in that "filename*" uses the encoding defined in [RFC5987], allowing the use of characters not present in the ISO-8859-1 character set ([ISO-8859-1]). Therefore, we alter the code to: 1. Use `filename` and `ascii` encoding whenever possible, 2. use `filename*` with `utf8` encoding otherwise (with a filename fallback for old browser) We also switch the `content-disposition` value to attachement if filename is specified, this will result as a mandatory download according to RFC6266. This mandatory download is the expected behavior. We changes the filename encoding to RFC5987 which is simpler, supported by all and modern browser (including IE from version 6) and does not suffer from the continuation issue. (see ticket #2522324 for details)

     1

Once you have read the `RQL tutorial`_ and you know the application'`schema`_,

     2

you're ready to define your own views. Just type the RQL query retreiving data

     3

you're interested in in the search field. If the view used to display them

     4

doesn't fit your need, choose another one in the possible views box (this box

     5

isn't displayed by default, but you can activate it in your `user

     6

preferences`_). Once you're satified, add a `bookmark`_ if you want to reuse

     7

this view later.

     8

     9

.. _`RQL tutorial`: doc/tut_rql

    10

.. _`schema`: schema

    11

.. _`user preferences`: myprefs

    12

.. _`bookmark`: doc/bookmarks

    13

    14

    15

Below are some example of what can be acheived...

    16

    17

.. winclude:: custom_view_last_update

    18

.. winclude:: custom_view_rss