Noissue - Improve documentation for linkify filter

README.md

 # CMS #
 
 We use this CMS for [adblockplus.org](https://github.com/adblockplus/web.adblockplus.org/)
 and related websites. It converts a directory with content data into static
 files. You are free to use it for other projects but please keep in mind that we
 make no stability guarantees whatsoever and might change functionality any time.
 
 ## How to use ##
 
 ### Running the test server ###
@@ skipping 251 matching lines @@
 * `locale`: Locale code of the page language
 * `available_locales`: Locale codes of all languages available for this page
 
 Following custom filters can be used:
 
 * `translate(default, name, comment=None)`: translates the given default string
    and string name for the current page and locale. The string name should be
    unique for the page but otherwise is only seen by the translators. Optionally
    a comment (description) can be specified to help provide the translators with
    additional context.
-* `linkify(url)`: generates an `<a href="...">` tag for the URL. If the URL is
-  a page name it will be converted into a link to the most appropriate page
-  language.
+* `linkify(url, locale=None, **attrs)`: generates an `<a href="...">` tag for
+   the URL. If the URL is a page name it will be converted into a link to the
+   most appropriate page language. The language used can also be specified

[Sebastian Noack, 2016/01/09 00:09:19]

"most appreciate language" sounds rather vague. It is the language of the page
the link points to, which is the language of the current page if generated, or
the default language if translations are too incomplete. However, since this
phrasing didn't change, LGTM. Up to you whether you want to address it though.

+   manually with the locale parameter. Any further keyword arguments passed
+   are turned into additional HTML attributes for the tag.
 * `toclist(html)`: extracts a list of headings from HTML code, this can be used
   to generate a table of contents.
 
 The following global functions can be used:
 
 * `get_string(name, page=None)`: retrieves a string from a locale file.
   Unless a page is specified the locale file matching the name of the current
   page is used.
 * `get_page_content(page, locale=None)`: returns a dictionary of the content
   and params for the given page and locale. Locale defaults to the current one
@@ skipping 29 matching lines @@
 filter is invoked. For more information on Jinja2 filters see
 [official documentation](http://jinja.pocoo.org/docs/dev/api/#writing-filters).
 
 ### Custom functions and variables ###
 
 The `globals` directory can define custom Jinja2 globals which will be available
 in all Jinja2 templates. Typically, this is used for custom functions. The file
 name should match the name of the function or variable to be defined, and export
 a variable with that name. E.g. `globals/myfunction.py` can define a function
 called `myfunction` that will become available to all Jinja2 templates.