> IIRC we are more or less maxed-out on our webspace use on SF but we can look > for an alternative to sync your development branch with an alternate webspace > to show work in progress until it is deemed fit to replace the current > website. If I am not mistaken, you get some user website space with your > SourceForge account (/home/project-web/<USER>.u/), but I have never tried to > use it.
I can allocate enough space & subdomain on my hosting with some custom hgcheckout scripts. > Why via gettext? I am not familiar with the use of gettext for translating > website and am interested to hear the pros and cons. > What is wrong with static translations of > HTML documents? Hugin translators are familiar with gettext translation, there are many easy to use applications. Reuse of already translated text (like the text in release notes.) One English version and many translations. > Given SF's limited > resources, I would not want to introduce more server-side dynamics (PHP) than > strictly necessary and since the texts are static we do not need to waste CPU > cycles on looking up and replacing strings dynamically, which is my > understanding of how gettext works. Translation might be part of "Bruno's upload-to-web" script or generated on first access and then cached on server. -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
