* create initial bits for plugin writer's guide
* move siteadmin stuff to site administrator's guide
* rework index.rst to support multiple guides
* tweak some text
* move files into subdirectories
I verified that this still works with html and texinfo build targets.
There's still a lot of work to do, but this is a good start.
None of these tools really work anymore in the SQL world, and possibly
aren't as necessary either. In the meanwhile, just disabling them to
reduce confusion.
Okay, this is a long story.
There are two ways to translate validation error messages:
1) Let wtforms do it. You give wtforms a translation thingy
and it calls it for the message to be translated. Good
idea maybe. Except: The translation function is only
called for the builtin messages of wtforms. It's not
called for any handcrafted messages in the constructor.
And we can't translate the message there! Because the
message needs to be translated when the form is
rendered, for each user's locale.
This does not work for us.
2) Translate the message while it gets rendered.
Luckily we render the message completely by hand. So we
can just translate it there also!
Simple, easy, works!
This all does not cover translating the builtin messages of
wtforms. They're currently not extracted in any way, so our
translators can't translate them.
But that's another issue!
Okay, so if you run git master of kombu, this works. And if you run
the older kombu + kombu-sqlalchemy, this also worked. In the last
release of kombu (2.1.5) there's a bug, and sqlalchemy+sqlite://
worked for processes consuming tasks but not ones publishing tasks.
Aye aye aye.
I guess we might have to move our setup.py back to the old kombu +
kombu-sqlalchemy setup until they put out a new kombu release? :(
Previously we were using kombu-sqlalchemy the library for sqlalchemy
support. Newer kombu has support for this internally, so we're using
that. Requires changing a celery setting and also removing
kombu-sqlalchemy from your path.
I hope the process of removing kombu-sqlalchemy from one's path
doesn't confuse too many people...!
We're seeing somewhat inconsistent data in tx pull.
My theory is: The server needs longer to process the
uploaded new template and work that into the translations.
* Nixed some of the mongodb references--pretty sure we're done with that.
* Fixed some awkward language.
* Fixed : :: stuff. Sphinx lets you do :: so you don't need the additional
colon.
* Turned a paragraph into a .. note:: section. That makes it easier to
notice and read.
