IBM Lotus Symphony, which is build on OOo + new UI - http://symphony.lotus.com/
Go-OO aka Your OpenOffice.org, is the Novell fork - http://go-oo.org/ StarOffice, the proprietary OOo - http://sun.com/staroffice NeoOffice for Mac - http://www.neooffice.org As I said earlier this month [1], in the office ubiquity world it doesn't matter what kind of office you're using, if it will be online or offline, with major features or smaller ones. It's all about interoperability, and MSFT knows it. That's why they want OOXML to succeed over ODF (and they will eventually). With office ubiquity upon his door, OOo shifted their next features [2] to PIM, such as a new Outlook replacement (wtf?), but also some new 2.0 features like code versioning (forget the weblog creation!). For me, I find quite annoying the extensions features, where OOo is on a small step for the Firefox bloat extension fame. The only real advantage that OOo could sustain until the real office ubiquity arrives, will be the fact that's cross platform. Also, it's rather amusing that for the five years that I was in charge of OOoPortugal, the builds were done by the portuguese team and it was only a file to download. Now, with the new team, it's 4 files away and it's not build locally. I suppose that's fine for most people, mainly the ones don't know OOo and found it complicated to install the dictionary after the suite - and that's why we've built the OOoPT with dictionary included. [1] - http://lists.paradigma.pt/pipermail/tce/2007-October/000118.html [2] - http://marketing.openoffice.org/ooocon2007/programme/wednesday_186.pdf -- //VD _______________________________________________ tce mailing list [email protected] http://lists.paradigma.pt/mailman/listinfo/tce
