[hugin-ptx] Re: Hugin's website rework (long term project)
Hello I have added translation branch to hugin-web site. Main script g.php is meant to be run offsite, to generate translated pages, it includes process documentation. For use, we will need to change some internal links (eg. from news.shtml to news.page ), maybe also some apache rewrite rules might come in place, but the basics are working. Each language can be translated independently and translate different set of pages. Content negotiation works on my server with default configuration, on sourceforge site it may behave differently. Vaclav -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Hugin's website rework (long term project)
While in the process I would also like to make the website translatable via gettext. I've never done this before so I will try to learn it during the process. I have some proof-of-concept gettext translation system for hugin web site (and i have been thinking about resurrecting it recently). I can share my code with you, or I can cooperate with you. Vaclav -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Hugin's website rework (long term project)
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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Repository acces in time between release candidates
Hello, I have seen, that some last Yuval's commits in 2011.2 branch was translation updates. I have also found, that my Czech translation update from default branch ( 723668d8c4cc ) wasn't one of them. 2011.2 with copy of file from default branch will be fully translated and compilable/ installable/runnable. I can commit it to 2011.2 branch, but I am not sure, if it is a right thing to bypass our release manager in time between release candidates. What's your opinion? Vaclav Cerny -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Repository acces in time between release candidates
Thanks. Commited.I am going to continue with bughunt. -- 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 hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
