Fix translation of WTForms strings - SUPERSEDED (by #13)

[mdxs]

This resolves the #6 "Strings that are in WTForms are not translated" issue; it currently builds on top of #8 "Updated Flask-WTF to 0.9.3" and #9 "Updated Flask-Babel to 0.9" (which are already merged in this pull request).

[lipis]

I'm quite confused with all these changes.. cause like I said.. I would rather wait with the version 2.0 of the WTForms before breaking backward compatibilities...

Also I remember playing around with the flask_ext, flaskext and flask.ext and I agree that we have to follow the latest and greatest standards, I'm just too careful with folder structure changes and would prefer to spend some time to check what's best.. but again it will all start on the parent project and then it will escalate here with the Babel specific only changes...! Let's just put it on hold for a while since most likely I'll be off in the coming days.. but I'll take everything in considerations and your findings! Thanks for your PR and the research behind it.. very helpful...

[mdxs]

Of course, feel free to postpone to a later date.

I would rather wait with the version 2.0 of the WTForms before breaking backward compatibilities

I know that's the plan... However, I needed to get this translation stuff working ASAP and thus pushed forward to make it happen with current stable releases of the libraries involved. Scratching my own itch...

but again it will all start on the parent project and then it will escalate here with the Babel specific only changes...

Understand, and no problem with that.

In fact, gae-init/gae-init#47 "Updated Flask-WTF to 0.9.3" (the PR for the gae-init parent project) will need to get some updates based on #8 here. I will push these updates there; based on what I learned here... I will do that just for completeness, knowing you will probably postpone merging (again: no problem).

The #9 "Updated Flask-Babel to 0.9" referenced here, is a gae-init-babel specific PR and IMO could be applied. Though you may want to postpone based on your analysis of:

Also I remember playing around with the flask_ext, flaskext and flask.ext and I agree that we have to follow the latest and greatest standards, I'm just too careful with folder structure changes and would prefer to spend some time to check what's best..

My current understanding (as reflected in the PRs) is based on http://flask.pocoo.org/docs/extensiondev/#anatomy-of-an-extension which IMO shows that the flask.ext. notation can be followed to find the extensions; and in recent incarnations of Flask the Extensions seem to be moving towards a more maintainable structure.

Let's just put it on hold for a while since most likely I'll be off in the coming days..

Sure, and if/when the PRs become obsolete due to WTForms 2.0 release, so be it; no hard feelings.

[mdxs]

Maybe the last commit above can work without updating Flask-WTF and Flask-Babel.

I'll try it now and report back here and/or in another PR, just to blow your mind :-)

[mdxs]

Closing this PR, as the new #12 "Fix translation of WTForms strings (simplified)" provides a much easier to understand solution.