Sun ODF Plugin 1.1 for Microsoft Office available now!

The newest version of our ODF Plugin for Microsoft Office is available, you can find it here.

We have fixed the installation problem that occurred on some systems, and have made many improvements to the filters.

The biggest difference compared to 1.0 is that we have support for different languages now!

It's still just one package to download and install, but the Plugin will detect the languages from your MS Office and your Windows installation. When support for that language is available, the Plugin UI within MS Office will use you current MS Office language, while the menus and dialogs in the system tray use the language from your operating system. If your language is not supported, the fall back is English.



I like it! And Hungarian is supported :o)))

A must have utility for every MS Office user.

Is the Office 2007 incompatibility solved? I know it is not depending on you, but are there any news?

Posted by Kami on October 02, 2007 at 01:34 PM CEST #

No news on Office 2007, since we still hope that Microsoft will fix that with SP1...

Posted by Malte on October 02, 2007 at 01:46 PM CEST #

I have the plugin ver 1.0 installed and when i check for updates it says "No new update available".

Posted by Gopal on October 04, 2007 at 11:03 AM CEST #

What I'm curious about is why on earth Sun is supporting Microsoft MSOffice to the detriment of less monopolistic solutions? The one feature that is going to kill MS Office domination in the future is its continuing lack of support for truly open and accessible standards (OOXML doesn't count as "open and accessible"). By providing such a plugin (for free!) Sun is basically helping Microsoft maintain their monopoly position. Which is bad for Sun in the long run, as MSWindows and variants depend on MSOffice for the necessary lockin..

At the moment, I can't think of any valid, reasonable or logical arguments as to why Sun would do this. I can only conclude then that money was involved. Lots of it.

Posted by Marc on October 04, 2007 at 01:33 PM CEST #

Gopal, I don't agree.
There are valid reasons:
- Ease migration path to ODF, people can change office suite later
- Windows Assistive Technology works only well with MS Office, so companies can switch to ODF, but at least some people stay with MS Office

Posted by Malte on October 04, 2007 at 01:37 PM CEST #

I just have to ask this to brighten everyone's day: When are you going to make an ODF plugin version that runs on Linux, Solaris, or Sun OS?

Posted by A little humor? on October 04, 2007 at 03:01 PM CEST #

Mmmm - ODF plugin version that runs on Linux, Solaris, or Sun OS...

Plugin for WHAT PRODUCT?

If you simply want just ODF, use StarOffice or

Posted by Malte on October 04, 2007 at 03:14 PM CEST #

I meant for the MS Office product. :-)

Posted by A little humor? on October 04, 2007 at 03:47 PM CEST #

Gopal: I will give you an example of why this is a very good thing; a friend of mine works in a small office where some computers run and the others run MS Office (possibly more than one version; some people are resistant to change and don't want to switch to OOo). They were saving files in DOC format to share but a file produced on one computer might not open right (or even open at all!) on another. I suggested the plugin and that problem is now solved :)

Allowing MS Office to save as ODF is NOT what MS wants as it helps prevent vendor lock-in. I really do thank Sun for this as it will definitely provide a bridge from proprietary to libre software, just like dual-booting and Wine have their place.

A little humor?: Malte was making a joke :)

Posted by Limulus on October 04, 2007 at 04:06 PM CEST #

Thanks for all the replies to my comment. Makes a little more sense now. One thing: poor Gopal didn't post the question of "why it's good", "Marc" did. The format of this comments page is a little odd though.

Posted by Marc on October 04, 2007 at 05:03 PM CEST #

Marc: whoops! I see that now; sorry Gopal! \^_\^;

Posted by Limulus on October 04, 2007 at 05:18 PM CEST #

Reposting my query - I have the plugin ver 1.0 installed and when i check for updates it says "No new update available".

Posted by Gopal on October 04, 2007 at 07:24 PM CEST #

Gopal - we are working on configuring the update server correctly...

Posted by guest on October 05, 2007 at 01:41 AM CEST #

When we install the ver1.1 will it uninstall the prev version or do we have to do it manually ?

Posted by Gopal on October 05, 2007 at 08:57 AM CEST #

Gopal, the 1.1 installer will automatically remove the old installation.

Posted by guest on October 05, 2007 at 09:24 AM CEST #

"..some people are resistant to change and don't want to switch to OOo"

I know how that goes, but with the end of availability of 2003. What does one do when you need to find an office suite to add in to the new PC purchase?

We made up a simple analysis comparing upgrading everyone ~35 stations to Office 2007 vs. everyone just going to OOo. When we showed them it would cost the company $15K to upgrade vs. just rolling everyone over and spending 15 minutes, along with handing them a OOo cheat sheet, it was far cheaper. Over paying for the upgrade licenses, along with training for the newer 2007 environment, remember which ever way you go people will need training, your just save money not having to purchase licenses.

If you look in Google you can find free training online.


Posted by DOUGman on October 05, 2007 at 11:14 PM CEST #

One observation ......
When I initially installed plugin ver 1.0, the installer changed the ODT file association from Writer to MSWord. When I installed OO2.3 the ODT file assoc was reset to Writer.
Now on installing the plugin ver1.1 the file association for ODT format was lost. Probably the installer while uninstalling the prev version removed this too. I had to manually reassociate this. Pls check this out.

Posted by Gopal on October 06, 2007 at 01:19 AM CEST #

One minor issue in Excel - The addin does not load, instead gives an error stating the file is not found. The program is looking for the file in the old path ie ver1.0. I then went to Tools-Addins , deleted the odfaddin entry, relaunched excel, pointed the odfaddin to the correct path. The odfaddin now launches properly.
No issues in powerpoint so far.

Posted by Gopal on October 06, 2007 at 05:20 AM CEST #

DOUGman: Thanks for helpfing people with the search URL :)

Gopal, #1: The registration in 1.0 was done by accident, and of course the deinstallation will reset it - standard MSI stuff...

Gopal, #2: The Excel problem seems to be in Excel, not in the Plugin. Word/PowerPoint don't have that problem, and for Excel we stated it in the readme. You know, that file that is located in the installation of different products and that normally nobody is ever using ;)

Posted by guest on October 06, 2007 at 06:13 AM CEST #

On the SUN website an overview of what is new in the version 1.1. is listed.

Among the improved language support, a somewhat vague 'what's new' item is also listed:

"The accuracy of document import and export has also been improved in this release."

I was wondering if there is a more verbose list available of what has been improved/resolved?
I am currently checking the conversion quality of the plugin on a set of ODF documents and most of the formatting issues that I discovered using version 1.0. still seem to be present in version 1.1.

Posted by Karl vom Berge on October 09, 2007 at 09:48 AM CEST #

The ODF Plugin is nice, but incompatible with certain features of the literature-database programs "Procite V.5.03" and "Endnote V.9" that are very important to me. The feature it interfers with is "CiteWhileYouWrite", it allows for the selection, insertion, and further handling of references into Word documents. If the plugin is installed, this feature is no longer accessible. The respective menus pop-down in Word, but there is neither an action, nor an error message.

Posted by Hugo Scheer on November 21, 2007 at 03:51 AM CET #

Hugo - no clue why our plugin should interfere with other plugins. Please use the feedback channel documented in the readme.txt, so QA people will get noticed and can try to reproduce...

Posted by Malte on November 21, 2007 at 03:57 AM CET #

Hello there,

I have tested the SUN ODF plugin 1.1 with MS Office 2003 and Adobe Acrobat Elements 7.0 installed on the pc. This will cause a bug/failure when trying to save an ODF-document (.odt-file) in Word? Word "hangs" forever when you hit the save button and trie to save it in odt. format?
if I uninstall Adobe Acrobat Elements 7.0 from the pc I can save in .odt-format again.

Anyone have a solution to this problem?

John Bue Damving

Posted by John Damving on December 11, 2007 at 05:04 AM CET #

Wow -- I just installed the plug-in recently, and I really like how cleanly it works. But I also ran into the problem where Excel doesn't get configured correctly. Are there any plans to fix that? For most non-technical users, this will be a show-stopper. Install the plug-in, it doesn't work in Excel, abandon the idea.

Also: I'm sure there's a technical reason for this (and it's probably been discussed already) but the Word plug-in nicely adds the ODF type to the Open file and Save file drop-down filetype lists. But in Excel and PowerPoint, instead, there are separate Import and Export buttons. Not as nicely integrated.

Posted by Robert on January 29, 2008 at 02:06 PM CET #

Robert, thanks for your comments.

Quick answers:

For the Excel problem I don't know a solution, looks like a Excel bug for me.

To the neat integration in Word, compared to Excel/PowerPoint: Well, MS Office doesn't give us the opportunity to do the same neat integrations in all applications.

Posted by Malte on January 30, 2008 at 12:42 AM CET #

Post a Comment:
  • HTML Syntax: NOT allowed

Malte Timmermann


« July 2016