templates should never use ``/mgoblin_static/`` but use
``request.staticdirect()`` instead, which uses the proper paths
from the config.

This is relevant when running mediagoblin not on / but on a subpath
like /mediagoblin/.

I have fixed the current templates (git branch will be pushed
tomorrow).

The interesting question is, if the test suite should test for
this?
If so, here's an idea on how to do it:


1. in ``test_mgoblin_app.ini`` set ``direct_remote_path`` to
   something else than /mgoblib\_static/
2. While testing: add a special "middleware" to the main App, that
   greps the rendered html for mgoblin\_static and errors out.

That way all tested paths will at least also get tested for wrong
references. At least, that's my idea on this.

When running mediagoblin in a subpath, like /mediagoblin/, then
some things are a little complex.

For ``/mediagoblin/u/elrond/`` ``request.path_info`` becomes
``/u/elrond/``.


-  This is good, when trying to match routes. Simple, fine, job
   done.
-  This is BAD, when generating URLs like "request.path\_info +
   foo" for the browser, because the browser will only see
   ``/u/elrond/foo``. Which is wrong. Problem.

I know, that the environ has SCRIPT\_NAME ("``/mediagoblin``" in
this case), but it's not entirely clear, on how to procede from
here.

Assigning to Chris, as he created most of the base infrastructure
and surely has comments.

When I am trying to translate spanish version:

Translation must start with a newline ()

With:

Create a free account?
or?
Set up MediaGoblin on your own server?