Slashdot Mirror

And if you look at a lot of them they are alpha/beta releases and not the 1.0 that you come to expect with proprietary software though.

What are the 2.5 and 2.6 releases of the Linux kernel then? Or take NeoOffice. While I have version 2.1 it's up to 2.2.3. NeoOffice, neither my version nor the new one is an alpha. I'm not sure about whether either one is a beta or not. My version of Firefox is 2.0.0.6, I don't know what's the current version for Macs. Look at Blender, I have version 2.44.

But there is a difference, the GIMP is not backed by any major corporation

CinePaint is backed by major corporations. It's called FilmGIMP because it's used by movies studios, it started as GIMP but a programmer added capabilities to it that photographers wanted, such as 24 bit colour depths per channel. The maintainers of GIMP did not accept them however some in the movie industry ran with it creating a fork. Here's a list of movie studios and movies that used it, two being Sean Connery's "League of Extraordinary Gentlemen" and Tom Cruise's "The Last Samurai".

So you would expect them to be a little less on features, another thing is, the GIMP developers focus on what means the most to them

That's right, businesses give users what they want whereas OS maintainers only do what they want, which takes us back to there being a place for both FOOS and proprietary software.

...already has support for it.

is a lot. However, if you can transition one little piece at a time, Windows is in trouble.

I don't think it's much of a shock to change the OS and the Office Suite used, it's not such a big deal. First off when most entities, whether people or businesses, get new computers more than likely the new system will have both a new OS, usually a new version of Windows, and a new version of MS Office. Secondly more entities are switch from MS Windows, to either Linux or OS X. For those who disagree with this, while the market itself is growing Macs and Linux are growing faster. After buying and using Windows since NT4 and 95 came out, about 20 months ago I switched to Linux and last summer I got the MacBook Pro I'm typing this on. For my office suite I use the native Mac port of OO.org, NeoOffice. It took me all of a week or two to adjust. Of course, just as I didn't use MS Office much, I don't use NeoOffice that much.

Have you never heard of Neooffice?

I'd just get the powerpc version of NeoOffice. It's not 3.0, but it works great.

losing out on the advantages of linux? by using OSX you lose out on the most important advantage of gnu/linux and free software: you actually own the software, you don't just license it.

Excuse me but I'm typing this in a Firefox tab on my MacBook Pro. As an office suite I use NeoOffice, the native Mac port of Open Office. I can install RPM packages with MacPorts and for Debian's dpkg and apt-get I can use Fink. Anything, well most maybe as I don't know for sure everything will, that runs in X on Linux I can install on my Mac.

In what way is Apple draconian?

The only people who don't consider Apple's practices to be tyrannical are Apple fanboys and people who don't know or care about anything beyond whether or not their computers gets them to Facebook/Myspace/whatever.

I am not an Apple fanboy. Nor do I use my MacBook Pro to get to either Facebook or Myspace though I do use it for the web. I also will be using it for photography and web development.

Oh, I also have a Linux PC and up until it died used a Windows PC. If the Amiga were alive today I'd probably using it as well.

In reality, though, Apple could never keep a dominant position for long, at least not with their current practices. The word "antitrust" comes to mind...

Antitrust hasn't stopped Microsoft yet, what makes you think it would stop Apple? And how could Apple become a case for antitrust? If I wanted to I could run not only Mac software but Linux and Microsoft software as well, actually I have installed and used Linux, FOSS, and cross platform software. For instance for my office suite I use NeoOffice, the native Mac port of Open Office.

When deciding to buy Office in order to get my business critical information I should have considered the optiona: a) Not buy office b) go out of busiess due to not being able to get the information that I need in order to operate.

I use NeoOffice, the native Mac port of OpenOffice.org, which is a couple of versions behind OO.org and I haven't had any trouble opening Office 2007 documents and I've opened up several of them. Now whether it can handle macros I don't know as I don't know if any the docs had scripts. If you're counting on being able to open docs and want to make sure anyone you send docs to can also open them them you all need to use the latest MS Office. And MS Windows version, as there are incompatibilities between Office for OS X and Office for Windows. You also ignore *nix users. It may not concern you if you're a closed shop, but for others can be.

On the other hand, Open Office still manages to choke on the minutae in Word, Excel, Powerpoint, etc. documents.

Though I haven't opened Powerpoint documents I have opened MS Word 2007's .docx and Excel documents with NeoOffice the native Mac port of Open Office without problems. The version I have is 2.1 yet 2.2.3 is available.

There's always NeoOffice, which is a much more mature OSX port of OpenOffice. Not used it much myself but I've heard it's pretty good.

FWIW, NeoOffice, a Mac Os X port of OpenOffice.org just had a new release last week. It's based on the 2.2.1 code and adds Quicktime video support, import from scanners and cameras, Mac OS grammar checking in Leopard, and some more stuff. Details here. Don't forget if you download it to grab the latest patch too.

The insane thing is NeoOffice only has two code developers.

FWIW, NeoOffice, a Mac Os X port of OpenOffice.org just had a new release last week. It's based on the 2.2.1 code and adds Quicktime video support, import from scanners and cameras, Mac OS grammar checking in Leopard, and some more stuff. Details here. Don't forget if you download it to grab the latest patch too.

The insane thing is NeoOffice only has two code developers.

FWIW, NeoOffice, a Mac Os X port of OpenOffice.org just had a new release last week. It's based on the 2.2.1 code and adds Quicktime video support, import from scanners and cameras, Mac OS grammar checking in Leopard, and some more stuff. Details here. Don't forget if you download it to grab the latest patch too.

The insane thing is NeoOffice only has two code developers.

I don't know, I think given Sun's wishy-washy support of OS X for OO.org in the past it's worth it to support NeoOffice at least in the short term. I haven't looked at Sun's work in a few months, but this thread gives some good detail as to the previous deficiencies of Sun's work for OS X support.

Until 2007, I was absolutely 100% for OO.o. Since using 2007, though, they've definitely passed OO.o back up. It's much faster (that was the main reason I went to OO.o) and Word has an absolutely perfect interface. They've finally done something right in the 2007 release.

You still have to pay a lot for Office 2007, unless you get the education version. I'm using native Mac port of OO.o NeoOffice. And though I haven't created a 2007 .docx document, though there is an option to save in that format, with it I have downloaded and read Office 2007 documents with NeoOffice without a problem.

one of my courses require it (meh) which means not only using office, but having to boot into windows to do it. its better than OO, for certain, but i just write essays and basic research papers, why its required is beyond me.

First MS Office also runs on OS X. Then with Crossover MS Office, up to 2003, Office for Window will run on both Linux and OS X. However I don't use MS Office at all, on my Mac with 10.4 I use the Mac native port of OO.org, NeoOffice I have had no problem opening even MS Office 2007 documents. When I download a .doc document NeoOffice handles it with no problems.

OpenOffice doesn't support Mac Users, so it's unlikely they'll support OpenOffice. NeoOffice is doing a pretty good job, though, and I recommend it to people who still want that "Office" feel. As for Microsoft office, most of the researchers I support use Microsoft Word for one reason: EndNote.

As Microsoft drops support for older Office file formats, it looks like Visual Basic for Applications is also going soon

Unless... what if there were only some alternative, open-source project that already supports it on Mac and a similar ongoing Windows/Linux project...

Oh well, I can dream.

W

As Microsoft drops support for older Office file formats, it looks like Visual Basic for Applications is also going soon

Unless... what if there were only some alternative, open-source project that already supports it on Mac and a similar ongoing Windows/Linux project...

Oh well, I can dream.

W

Many open source apps I use are not well supported (Openoffice, Amarok, Gimp, Inkscape, k3b.

NeoOffice is a good Mac port of Open Office. And MacGIMP is also a Mac port. However if it's like GIMP it only has an 8 bit colour depth per channel. While that may be fine for the web, it's seriously lacking for print media. For print CinePaint aka Film GIMP is better. How well it's supported on OS X I don't know but I've be finding out rsn. If it doesn't do what I want though I may end up getting Photoshop CS3, which you can't get running on Linux without jumping through hoops. I'll also try Inkscape and Blender. The others I don't know about.

the OS X interface is awful

I guess it depends on your taste. Neither I nor many other Mac users have a problem with it. Of course my favorite OS was Amiga.

MacPorts packages didn't compile 50% of the time.

I haven't tried it yet but I'll go through to see what's available. If I find some good software I'll go ahead and try it.

OS X is usable for open source web frameworks, but for desktop apps, I find it better to either stick with the OS X specific commercial stuff or just use Linux.

I use NeoOffice, the Mac centric version of Open Office, and it's great.

I did in the native port of Open Office for Macs, NeoOffice, without a problem. As for whether it can handle Office macros good I don't know.

for the Mac

I use NeoOffice, a native Mac port of Open Office. No X11 needed.

The fact of the matter is that if you are using Macs you will likely have compatibility issues every once in a while.

In the 5 months of using my MacBook Pro I have not had a problem with NeoOffice. While I haven't created or edited any docs with it yet, NeoOffice has opened Office 2007 .doc and .docx files I've downloaded from the net without a problem.

Microsoft could very well decide in the near future that it no longer wants to support MS Office on the Mac.

Though MS can threaten Apple to withdraw the Mac version of MS Office, I think MS would have to think long and hard before actually doing so. Courts, in the EU and US, may look at it as another example of how MS uses it's majority market position as a noncompetitive monopolistic practice.

I didn't try it, but there is neoOffice at:

http://www.neooffice.org/

I like and use both Linux and Mac OS, but I'm having trouble understanding one class of complaints you have.

First, the shortcuts are not consistent from program to program. Firefox, for example, uses Ctrl-D to deny cookies, while Safari uses Command-D to deny.

Are there two browsers on Linux that have the same keyboard shortcuts? I haven't found any yet.

Microsoft Word for Mac uses Windows-style shortcuts (end/home etc).

Where did you get your copy of Microsoft Word for Linux for this comparison?

I realize that this is not an OS X problem, but in a way it is -- these keys are not enforced like they are on other OSes (yes, linux has good shortcuts).

How? Is there a file in /etc I can edit to get "good shortcuts"? I've got a lot of programs here with horrible shortcuts -- who do I go to go "enforce" good ones?

These impede my flow of thought when I have to fish for the right keys to move from word to word, use the delete key (on a laptop), show the desktop (F11? wtf).

So go to the control panel (uh, I mean "system preferences") and change it to some other key -- exactly the same thing I do in Linux if I don't like its default (control-alt-D, which is even worse, but still, easy to change). BTW, on the newest Apple keyboards, show-desktop actually has its own key.

I could go on and on about bad shortcut keys, but I think I have gotten my point across.

Indeed. You're using two third-party apps which are inconsistent (and hated by many Mac users for it) and you don't like the default for show-desktop.

Oh, and using Open Office is not feasible in OS X. I'm sorry, but it plain sucks (slow, inconsistent, requires X11...)

No, it doesn't.

P.S. Sorry to have to post as AC, but I don't want to go to Karma hell. It's not my intention to start a flame war anyway, just giving you an honest answer to your question, from my point of view.

Have I been trolled? Is this another case of somebody flaming on a forum to get free tech support? Beats me. It doesn't seem much easier than going to the control panel and typing "keyboard shortcuts" in the search box, so I suspect it's a troll.

The preferred OpenOffice.org implementation on OS X is NeoOffice, which doesn't require X11 and has many benefits over vanilla OO.o.

Disclaimer: I am one of the founders of NeoOffice.

Being based on OOo 1.x, IBM does not need to release the source code for Symphony. OOo was originally dual licensed both under LGPL and the SISSL license. SISSL allows companies to make completely closed source forks, only providing notice of the original vendor and SISSL license. This license was one of the primary motivating factors for why we forked and created NeoOffice, to prevent companies from making a commercial product whose improvements couldn't be shared back with all the volunteers that had worked to create it.

Closed source forking is also our reason for using full GPL since it guarantees everyone's freedom to access the code. Not even LGPL provides that ability since commercial closed source proprietary code can still be incorporated provided it's in a shared library. Only the full GPL provides enough protections to ensure that everyone must cooperate and that no one can make key parts of the project rely on closed source solutions.

ed

Disclaimer: I am a founder of the NeoOffice project.

ooo-build has long been much more than build fixes. For many years it has been the public face of the work Ximian and Novell have poured into the OpenOffice.org source base. It has a long history of features that Ximian/Novell have helped develop, including (but not limited to):

• OpenXML import/export support via odf-converter
• Kohei's solver optimization extension
• Native widget framework and GNOME integration (from back in 1.1.x)
• Visual Basic suport for Calc
• Alpha-blending and enhanced alpha blended icons
• A redesigned GNOME-like icon set
• Microsoft Works importer
• Evolution integration
• And more...

ooo-build is about functionality and features. Despite the name, it has never been about "build fixes" as indicated in the article. The additional functionality is so awesome that, at NeoOffice, we have been using ooo-build in NeoOffice since March and have been donating back bug fixes and Mac-specific support patches to the ooo-build project. Years ago the Ximian work on OOo 1.0.3 was so promising that I put together a Mac OS X port back in 2003 which folks used for a long time. OxygenOffice also is based off of the ooo-build project (although I do not know if the OOOP team coordinates with ooo-build).

The ooo-build team has done amazing work. It is sad to see their work go unrecognized by so many and be outright rejected or stalled by Sun. NeoOffice users have loved having the functionality ooo-build brings currently and continues to bring in the future, and much of the work pioneered by ooo-build is critical to maintaining the Mac platform as a viable office solution (read VBA). Sun's lack of acknowledgement and incorporation of ooo-build features does nothing but hurt users. Having received a "you're welcome to join us" response similar to Kohei, I am glad I do not consider myself part of OOo any longer. The freedom of forking has allowed NeoOffice to incorporate all good code without all of these politics and marketing games. Forking has allowed NeoOffice to deliver to Mac users the features they wanted yesterday regardless of where those features came from. Sun has a history of a "not invented here" syndrome at times when it comes to code within their "open" source projects.

I'm glad to see that ooo-build is getting some recognition. I hope more users start seeing some of the great functionality they can get today on Windows and Linux, and once again I thank ooo-build, Ximian, and Novell for their continued dedication to improving OOo.

ed

Disclaimer: I am a founder of the NeoOffice project.

ooo-build has long been much more than build fixes. For many years it has been the public face of the work Ximian and Novell have poured into the OpenOffice.org source base. It has a long history of features that Ximian/Novell have helped develop, including (but not limited to):

• OpenXML import/export support via odf-converter
• Kohei's solver optimization extension
• Native widget framework and GNOME integration (from back in 1.1.x)
• Visual Basic suport for Calc
• Alpha-blending and enhanced alpha blended icons
• A redesigned GNOME-like icon set
• Microsoft Works importer
• Evolution integration
• And more...

ooo-build is about functionality and features. Despite the name, it has never been about "build fixes" as indicated in the article. The additional functionality is so awesome that, at NeoOffice, we have been using ooo-build in NeoOffice since March and have been donating back bug fixes and Mac-specific support patches to the ooo-build project. Years ago the Ximian work on OOo 1.0.3 was so promising that I put together a Mac OS X port back in 2003 which folks used for a long time. OxygenOffice also is based off of the ooo-build project (although I do not know if the OOOP team coordinates with ooo-build).

The ooo-build team has done amazing work. It is sad to see their work go unrecognized by so many and be outright rejected or stalled by Sun. NeoOffice users have loved having the functionality ooo-build brings currently and continues to bring in the future, and much of the work pioneered by ooo-build is critical to maintaining the Mac platform as a viable office solution (read VBA). Sun's lack of acknowledgement and incorporation of ooo-build features does nothing but hurt users. Having received a "you're welcome to join us" response similar to Kohei, I am glad I do not consider myself part of OOo any longer. The freedom of forking has allowed NeoOffice to incorporate all good code without all of these politics and marketing games. Forking has allowed NeoOffice to deliver to Mac users the features they wanted yesterday regardless of where those features came from. Sun has a history of a "not invented here" syndrome at times when it comes to code within their "open" source projects.

I'm glad to see that ooo-build is getting some recognition. I hope more users start seeing some of the great functionality they can get today on Windows and Linux, and once again I thank ooo-build, Ximian, and Novell for their continued dedication to improving OOo.

ed

Disclaimer: I am a founder of the NeoOffice project.

ooo-build has long been much more than build fixes. For many years it has been the public face of the work Ximian and Novell have poured into the OpenOffice.org source base. It has a long history of features that Ximian/Novell have helped develop, including (but not limited to):

• OpenXML import/export support via odf-converter
• Kohei's solver optimization extension
• Native widget framework and GNOME integration (from back in 1.1.x)
• Visual Basic suport for Calc
• Alpha-blending and enhanced alpha blended icons
• A redesigned GNOME-like icon set
• Microsoft Works importer
• Evolution integration
• And more...

ooo-build is about functionality and features. Despite the name, it has never been about "build fixes" as indicated in the article. The additional functionality is so awesome that, at NeoOffice, we have been using ooo-build in NeoOffice since March and have been donating back bug fixes and Mac-specific support patches to the ooo-build project. Years ago the Ximian work on OOo 1.0.3 was so promising that I put together a Mac OS X port back in 2003 which folks used for a long time. OxygenOffice also is based off of the ooo-build project (although I do not know if the OOOP team coordinates with ooo-build).

The ooo-build team has done amazing work. It is sad to see their work go unrecognized by so many and be outright rejected or stalled by Sun. NeoOffice users have loved having the functionality ooo-build brings currently and continues to bring in the future, and much of the work pioneered by ooo-build is critical to maintaining the Mac platform as a viable office solution (read VBA). Sun's lack of acknowledgement and incorporation of ooo-build features does nothing but hurt users. Having received a "you're welcome to join us" response similar to Kohei, I am glad I do not consider myself part of OOo any longer. The freedom of forking has allowed NeoOffice to incorporate all good code without all of these politics and marketing games. Forking has allowed NeoOffice to deliver to Mac users the features they wanted yesterday regardless of where those features came from. Sun has a history of a "not invented here" syndrome at times when it comes to code within their "open" source projects.

I'm glad to see that ooo-build is getting some recognition. I hope more users start seeing some of the great functionality they can get today on Windows and Linux, and once again I thank ooo-build, Ximian, and Novell for their continued dedication to improving OOo.

ed

Sure, not everybody can or will. But some people do. And that's the point. Folks didn't like how OpenOffice looked on MacOS, and created a version that looked good.

These guys NeoOffice are still waiting.

Disclaimer: I am one of the founders of NeoOffice.

I think there's already interesting proof that forks can provide a very viable alternative to the overhead of the OOo project. Although the reasons are many, one of the big problems I historically had as a Mac OOo engineer was trying to get patches approved by Sun engineering. It has proven to be more efficient to have engineering freedom, allowing us to implement things that might never be approved by Hamburg. Being independent also has allowed us to implement a binary patching system so our bug fixes can be delivered quickly and independently if any marketing driven release schedules. Being outside the politics has also allowed us to integrate other open source technologies into the application that are important to Mac users, such as VBA support as well as OpenXML import and export. Yes, OpenXML import and export could be integrated into OOo today but engineering politics and Sun's manipulation of the project to foment a document format war have kept this functionality out of OOo, doing nothing except harm users that need to seamlessly integrate with MS Office environments.

NeoOffice has been shipping a solid, native, GPL licensed Mac product for over 2 whole years. We have shown forking is successful. Dropping the politics of the OOo organization has made us more efficient and resulted in a better product that users appreciate. We have had a free software solution for Mac for years, and all OOo has done is exorcise all reference to us from their website. Perhaps it is just banishment for daring to do things differently and not helping to propogate the name of OOo (which Jonathan Schwartz has publicly said is Sun's second most valuable brand after Java). Seems a bit like Sun wants control to me. It will be interesting to see if Sun has the stones to snub IBM for its Lotus Symphony brand in the same fashion.

ed

There is a version of OpenOffice.org ("OO") that uses the beautiful graphic elements of the Mac interface called Neo Office. I don't have a Mac, but I use OO on both Windows and Linux (with less and less taking place on Windows).

I've been using OpenOffice.org since version 1, and I'm quite happy with it. More importantly, very few people seem to notice that I'm using it so the compatibility isn't as big a deal as they want you to believe.

Just give it a try, it's not like it costs anything :-).

Have you tried NeoOffice on Mac?

Disclaimer: I am a founder of the NeoOffice project.

The reason to include the source code is both moral and practical.

From a practical standpoint, it ensures that everyone providing NeoOffice needs to take no special action to comply with the GPL. According to our interpretation, anyone who provides a binary that is licensed under GPL is also obligated to provide the source code for that program. By placing the source code package within our disk images, anyone and everyone who provides the disk images is automatically providing source code. Everyone is fully compliant with even the strictist interpretation of the GPL without needing to do any extra work. This removes a lot of potential hassles and liability for our mirrors and other distributors.

From a moral standpoint, the origin of freedom within free software is the code. The GPL applies to the code, not the binaries; you can't license a binary under GPL without licensing the code. The source code is the freedom. It is worth a few extra bits to give everyone their freedom, even if they choose never to exercise it. Even if our servers go dark, everyone automatically has the source. Anyone can always exercise their rights, guaranteed. No one can ever take that freedom away from them besides themselves.

I think removing some of the pointless drivel on YouTube might be a better way to spare bandwidth and be "kinder to the Internet" rather than removing the guarantee of people's freedom. Perhaps I am just a purist.

ed

I am usually an opponent for the use of OpenOffice stating it is a sub-par replacement for office...

Even if it's true that OOo is a sub-par replacement for MS Office, it's still "good enough" for most people. So given the choice, would you rather get a good Office suite for free, or spend hundreds of dollars for an Office suite with extra features that you won't use. Further, in some cases, OOo has better support for MSO files than MSO does.

In my office, we were having trouble opening a .docx file, and no one could get the "Office Genuine Advantage" to verify their copy as legitimate, even though they're entirely legal copies. Because OGA wasn't working, they couldn't install the patch to allow Office 2003 to read .docx files. The solution? I had NeoOffice on my Mac (a OSX port of OpenOffice), and that was able to open the .docx file and save it as a .odt and .doc for everyone else.

I understand that that still might not be convincing. Some people just absolutely need a feature that in Excel that OpenOffice doesn't have (I hear people get hung up more on Excel or Outlook features than on Word features). Still, OOo is quite a lot better than Works.

"Open Office (which is awful on the Mac)"

Use NeoOffice instead. It's has a more native look/feel version of OOo for OSX and it's getting better all the time.

I'm pretty happy with Vim ;)

Seriously, I've found NeoOffice enough to manage the daily flow of doc/xls/ppt files. I mostly view those files, the exception being Excel spreadsheets I routinely send to other departments. The spreadsheets are dumps of SQL queries, which I can produce as CSV and later import in OO Calc, or run under Parallels a Windows 2000 instance (pretty snappy in my Macbook) and EMS SQL Manager for MySQL to get the report straight as an Excel file (and character encoding issues are handled better).

Except you also say you use MS Word on Windows. Any particular reason why you completely reject the Mac version, other than the demo's watermark? Oh, BTW, the italics problem in NeoOffice can be solved with 10 seconds googling: http://neowiki.neooffice.org/index.php/Accessing_H elvetica_Oblique_and_Courier_Oblique And the Canon scanner drivers? As it says on the download page: Double-click the " ScanGear CS Installer " file in the folder. Installation starts automatically.

If you need stability, Neooffice is pretty solid. (It's based on the OOo codebase but using OS/X's Java to provide the UI; it's nicer than the X11 version on OS/X, but relatively slow on pre-intel kit. I've written -- and sold -- a couple of novels using NeoOffice, although I'm currently Switching to Linux (again) ...)

Just wanted to give a thanks to the folks behind neooffice (http://www.neooffice.org/) before all the bashing starts...

Meanwhile, if you want a fully functioning, free, office suite, just use NeoOffice (an OpenOffice.org fork).

http://www.neooffice.org/

A port of OpenOffice to Mac OS X that uses Java as a compatibility layer.

It _is_ production ready (I use it every day).
Why the OpenOffice people are hostile to this project is something I've stopped
wondering about... today's announcement of the "first" port of OOO to Mac not
using X11 just shows how badly a project hurts itself when it refuses to work
with others

"I haven't been to the NeoOffice website in a very long time .. least friendly .. their social skills .. feature set and bugs of NeoOffice as compared with Open Office, Microsoft Office, or iWork? ...

What did they say exactly that got you so upset. Personally I find Emacs more than adequate, as long as you don't want rich text, and frames and bullets and a spell checker that obscures the word it asks if you want to change :)

"NeoOffice is a .. Based on the OpenOffice.org office suite"

was Re:They exaggerate

NeoOffice is based on OpenOffice ... but more Mac-looking and Mac-friendly

see http://www.neooffice.org/neojava/en/index.php

But seriously... Why didnt they choose Open Office? It is the OBVIOUS choice.

Well, they sort of DID choose Open Office, except that they chose the native MacOS X port of it instead of the "plain" version.

http://www.neooffice.org/neojava/es/index.php

An open letter to Jonathan Schwartz, CEO of Sun Microsystems, Inc. regarding the official Sun Microsystems Mac OS X participation announcement of May, 2007.

attn: Jonathan Schwartz
c/o Sun Microsystems, Inc.
4150 Network Circle
Santa Clara, CA 95054
Return Receipt Requested

Mr. Schwartz:

Send beer.

Sincerely,
Edward Peterlin
Chief Visionary, NeoOffice.org
and The Undersigned