Op Do, 2009-10-01 om 19:26 +0930 skryf Clytie Siddall: ...
> The question is: are Pootle and Rosetta serving the same audience? > If > so, how can we be more useful to that audience, now Rosetta has > caught > up with some of our key advantages? I have not seen anybody use Rosetta yet, so for the time being I'm considering this purely theoretical. Last time somebody told me, it wasn't even easy to get the source code for it. > It occurred to me in the night watches that Rosetta's main advantage > in this situation is its integration with projects. That's certainly > what I have heard, and continue to hear on my project lists. If > you're > running a project on Launchpad, and you need translations, you don't > need to install anything, create any procedures or setup anything > much. Rosetta is integrated in Launchpad. Your translation teams can > devolve from your development team. > > I still think the capability to install anywhere is important to > Pootle, but I think we need to lower the barrier there (cf. the > regular appearance on this list of frustrated and confused posts > from > people trying to install Pootle). We need to provide installers, and > work with the package-management systems. I guess people who don't struggle to install it just don't write to the mailing list :-) We have a growing list of people who seem to have managed quite well to install Pootle: http://translate.sourceforge.net/wiki/pootle/live_servers As Julen mentioned, Pootle is packaged for several Linux distributions. But of course, we should keep working on improving the state of packaging where we can. > I also suggest for your discussion the possibility of integrating > Pootle with another project-development platform, e.g. SourceForge > or > GForge. > > The Translate project is already (still?) based at SourceForge. The > SF > people have been rabbitting on for months now about extended > infrastructure and providing more services for projects. They could > also provide a Pootle. It would be integrated with SF, available > just > as the source-control repos and other services are. It would > integrate > with their source-control system and wiki. It would have the > resources > to host large numbers of projects (thus fulfilling another need we > have seen expressed regularly on this list). It would take a lot of > the headaches out of i18n for projects. > > I myself translate for several SF projects, including Fontforge, > Inkscape and Mailman. I think Mailman, as an SF project, might well > have decided in favour of Pootle if it had been available as part of > the SF infrastructure. Inkscape and Fontforge AFAIK are still > struggling without a translation interface. I believe they would > both > be interested in having a Pootle available. And there are so many > projects running on SF, even if only 1% chose to use Pootle, it > would > be a success. Gforge is another possibility: it hosts po4a (GPL), > which has a number of doc format PO conversion filters which we > could > combine with Pootle (there or elsewhere). > > For those who prefer to roll their own, we need to take some of the > pain out of trying to start and run your own Pootle, by providing > installers and timely and effective package-management versions. For > the rest, we can take virtually all of the pain out of localization > by > providing an integrated Pootle. What do you think? I think it is important that we all continue to help and inspire software projects to improve things for localisers. Everything you mention will definitely be a great help. Integration with something like SourceForge or GForge is a great idea, and I think we should take it up. I actually think there was already a request with SourceForge some time ago. I hope that the upcoming version of Pootle will make all of this much easier. Keep well Friedel -- Recently on my blog: http://translate.org.za/blogs/friedel/en/content/support-afrikaans-google-translate ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
