[hugin-ptx] Re: Hugin's website rework (long term project)
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 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
Re: [hugin-ptx] Re: Hugin's website rework (long term project)
On August 18, 2011 05:12:31 AM cri wrote: 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. And how would such a system deal with incomplete translations? I understand your considerations and motives and support the idea of simplifying life for translators. I would like to see a prototype, or even better: real life examples (if they exist) before making up my mind (for whatever my opinion is worth - if you are determined to do something you will do it). My concern is not about gettext specifically. I have never seen it in action on a website and am open to consider it. My concern is about a viable multi-language platform for a website, something that I have a lot of experience with. I've lived most of my life in multi- lingual countries and I am a polyglott. I participated in different roles to projects that had multi-language websites, some of them of great complexity (on a trading platform each and every word needs to be signed off by a lawyer). I have implemented complete multi-language websites myself. I have seen gettext very successful in the app space but have yet to see it in web space. There are multiple factors and trade-offs at play. When Bruno developed the current Hugin website, he considdered them and this website has served us well. I am not saying that it can not change. I am saying that all of these factors will need to be weighted. You mention yourself that you have little experience. I would recommend small steps. If you make yourself dependent on gettext at this early stage, you risk making all other additions dependent on it. If it turns out not to work, your other additions will go with it as well and this would be sad. 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. As a provoking thought: why translating at all, then? Why not use Google Translator to generate automatic translations? You can be sure that it does not break the html code and that it is abreast of the latest changes, if these are the two most important factors to consider... Frankly: keeping up to date with the tracker is enough for a website like Hugin. This is not a news website changing every hour; and there is no need to keep an eye on the tracker unless you translate bleeding edge not yet released stuff. Frankly again: the occasional break in the html code of a single page is not critical either, especially since it concerns mostly bleeding edge pages not yet released / published. It's called work in progress. I will have some feedback to you about the recent changes you made to the Italian translation of the upcoming 2011.2.0 release. Have not got around to them because yesterday my workstation's HDD decided to quit. The SSD for the netbook is scheduled to arrive today and I hope to restore the backups and be back in full production mode this weekend. 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. Same consideration made here. You're faster than me. Instead of a tabbed text I was using a JOSN file with a client-side JavaScript lookup. Equally easy to edit; does not need server-side parsing (i.e. resource wasting). I've discussed the problem of information collection with Bruno a couple of weeks ago. Many if not most of the banner images up there belongs to him. And he suggested: why not starting from scratch? Would make sense to me. Then we can put up an appropriate process, and make sure that we have complete information for all the images used, including author and proper licensing. An advantage of keeping the website in an SCM is that we would find the history/documentation of this in the SCM itself. I tried to look for authors/credits/licenses in the SCM log, but this happened too long ago and so the information is incomplete. Yuv (heading out to wait for the postman with the SSD before also the HTPC quits on me) signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] Hugin-2011.2.0_rc4 released
The issue on OSX Lion has been identified and there is a work-around, but no fix yet. The openmp version of enblend that woks on Leopard and SnowLeopard no longer works on Lion. The old Tiger version of enblend, which is simply a non openmp version works. This Tiger enblend version is also packaged in the dmg together with a Readme how to use it. I will expand the Readme that Lion needs to use the non-openmp version as well for the time being. I will also modify the root folder Read Me First (Mac).pdf inside the dmg with this info. hoi, Harry -- 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-Publish to [Various Panorama Hosting Platforms] Suggestion
Thank you Emad ... Seems like an opportunity to add value to Hugin users by integrating as many Publish to ...[hosting service] solutions as possible. Since the Tour Wrist publishing API is free -- and it is free for Hugin users to Publish to Tour Wrist 360º virtual tour platform, this API might be a good test and learn experience for Hugin developers. ... Dan On Aug 13, 12:46 am, Emad ud din Bhatt xyzt...@gmail.com wrote: Its a very nice idea+offer. On Fri, Aug 12, 2011 at 10:00 PM, Dan Smigrod d...@greattv.com wrote: Hugin Team, If you decide to add Publish to [Various Panorama Hosting Platforms] as a Hugin user feature, the Tour Wrist Publishing API is free to developers: http://tools.tourwrist.com/developer Plus, if you include a Publish to Tour Wrist feature, Hugin users can publish unlimited number of 360º virtual tour scenes to Tour Wrist for * free*: http://tools.tourwrist.com/add_your_property On behalf of Tour Wrist, * Dan Smigrod CEO Chief Creative Officer GREAT! 3527 Knollhaven Drive, NE Atlanta, GA 30319-1908 USA Phone: 404-303-7311 SKYPE Video: dansmigrod Email: d...@greattv.com * -- 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 -- *Emaad*www.flickr.com/emaad -- 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
Re: [hugin-ptx] Hugin-2011.2.0_rc4 released
Hi Harry, I just notice an error with the latest installer for hugin-mac-2011.2.0-RC3 on Mac OS X 10.6: It doesn't ask me for a password (I almost always use a non-admin account) and so the installation fails. Carl Harry van der Wolf schrieb am 18.08.11 19:22: The issue on OSX Lion has been identified and there is a work-around, but no fix yet. The openmp version of enblend that woks on Leopard and SnowLeopard no longer works on Lion. The old Tiger version of enblend, which is simply a non openmp version works. This Tiger enblend version is also packaged in the dmg together with a Readme how to use it. I will expand the Readme that Lion needs to use the non-openmp version as well for the time being. I will also modify the root folder Read Me First (Mac).pdf inside the dmg with this info. hoi, Harry -- 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
Re: Python Windows (was Re: [hugin-ptx] Re: Hugin-2011.2.0_rc3 released)
The builds are not Python enabled as I have yet to devise a method of distribution that reliably works without a local Python install. Do I understand correctly that this is a purely packaging issue and that the code builds with Python? If this is the case, does it make sense to wait in RC status until you figure out how to distribute Python with Hugin? Correct: it is a packaging issue. I currently don't have time to work on the issue, so the release process should more along. I can, however, build and upload a separate binary with python support to drop into the installation that should work if a compatible version of python is installed on the target machine. Matthew -- 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
Re: [hugin-ptx] Mercurial browse disappeared from sourceforge site
Hullo All, On Wed, 17 Aug 2011 12:39:13 +1000, Tduell tdu...@iinet.net.au wrote: Hullo All, Has something been broken at the hugin sourceforge site? The 'code - mercurial browse' turns up an essentially blank page. This continues to appear broken here. Maybe I have a problem with my browser or somesuch. Can someone please try http://hugin.hg.sourceforge.net/hgweb/hugin/ and report if you get the normal page showing who committed what to which branch? I am assuming that is the correct URL, it is what is linked to the code - mercurial browse at the sourceforge hugin site. Cheers, -- Regards, Terry Duell -- 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
