Improve the note about users translations rights for a template

[Adi Roiban]

This bug is about improving the bottom page notes from each PO file translation page.

A nice feature would be to make that info generic and also display it on other translation pages.
---------------

Right now if a user has not agreed with Launchpad translations license , that user will not be able to add translations.

Some users might not know about this requirement or don't know where they should „sign” the licence.

Even if a user is member of a TRANSLATION TEAM, that user will still not be able to translate and there is no warning that he/she needs to sing the license.. otherwise their membership is of not much use.

Right now the text describing translation permission does not mention anything about licensing.

Solution in screenshot 4

--------

If there is no reviewing team for a language inform translators who they can contact to set up a new team.

Solution in screenshot 2

-------

Even if the translations are on Open or Structured mode... if there is no team of reviewer provide a contact for creating a new team

Solution in screenshot 1

-------

If the translations needs to be reviewed by a team, provide a contact to that team in case the translator needs help or their translations are not reviewed

Solution in screenshot 3

[Adi Roiban (adiroiban)]

I tried to provide a solution.

Looking at bug 427319 i think we can make pofile-translate-access.pt more generic and also include it on serieslanguage-index.pt and productlanguage-index.pt

I have attached some screenshots.

Please let me know if the changes are ok and I will also add the required tests.

[Данило Шеган (danilo)]

Adi, thanks for working on this. In general, this bottom message is very hard to see, and I believe most of our users never read it. If we had a better page structure, we'd have a "What can I do?" pop-up near the top of the page instead. That should not stop one from implementing your improvements, but do note that with complex conditional renderings such as these, it's very, very easy to break stuff unless it's properly tested (but that's again hard, because there are 2^number_of_conditions cases): if it's broken, +translate page won't work for many users at all.

So, if you want to do this, do not try to overgeneralize it too much: just do it for the +translate page, and keep it limited to that.

[Adi Roiban (adiroiban)]

Since those TAL conditions are very fragile I will not touch them for now.