2011/5/25 Fabien Chéreau <[email protected]>: > This approach has several advantages: it will be much easier for > contributors to translate the website, it will be easier to manage > updates, the whole code will be stored in the main Stellarium bzr.
I would prefer not to load a website in the main repository of Stellarium's. > On the other hand they could be a number of issues: > 1 - We will loose the current translated php files content. I think > it's quite OK when I see the quite bad state of website translation. > We could also use this opportunity to update a bit the webpage > content. I agree with this position. > 2- There may be some security issues by allowing untrusted people to > edit the translated website content in launchpad (like injection of > javascipt etc..). A solution could be to allow only trusted people to > edit the translations on launchpad, but unfortunately the permissions > management for project translation in LP is unfortunately not very > flexible and as far as I understood, I don't think it's possible. This issue is being addressed through changes policy permissions for the translation project - but you can not specify different policies for different "domain's" within one project. > 3- Anything else? How to update translations on the site? -- With best regards, Alexander ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Stellarium-pubdevel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stellarium-pubdevel
