I agree with Vaclav considerations about gettext. I also want to add that with a gettext infrastructure the updates on webpages text can be more easily tracked by any translator simply by updating the po file. Otherwise you need to keep continuously an eye to the tracker in order to see what changes have been made to a webpage's text. Plus, with gettext, there is less possibility to break the html code of the webpage.
Talking about the header I really want to see photographers credited by showing their images done with Hugin. So I've already experimented a newer solution using the already available panos on the hugin-web repo. The solution consists of a tabbed text file with data about image, all in a row, like title, author, and a link to a webpage. What is really needed in that case are all those informations for any pano. -- 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
