Language Selection

English French German Italian Portuguese Spanish

OOo Off the Wall: The Elephant in the Living Room -- OOo and MS Office

Filed under
OOo

For OpenOffice.org (OOo), MS Office (MSO) is the elephant in the living room. As much as the project might want to ignore MSO, it cannot. Many potential users never have used anything except MSO, and most have to share files with MSO users at some point. The lucky exceptions, of course, are those in a free software work or educational environment, who deal only with equally lucky family members and friends.

For these reasons, OpenOffice.org includes design elements and features to making interacting with MS Office and switching from it as easy as possible. Much of the interface as well as the basic work flow is the same in both programs. Many features have the same name and are located in the same place in the menu, although enough differences exist that users occasionally will stumble. In additional, several features exist specifically for interacting with MSO. Yet, in the end, despite all of these provisions, you still need to plan intelligently if you regularly share files between OOo and MSO.

Full Story.

More in Tux Machines

Red Hat News

Development News: LLVM, New Releases, and GCC

PulseAudio 10 and Virtual GPU in Linux

  • PulseAudio 10 Coming Soon, Using Memfd Shared Memory By Default
    It's been a half year since the debut of PulseAudio 9.0 while the release of PulseAudio 10 is coming soon. PulseAudio 9.99.1 development release was tagged earlier this month, then usually after x.99.2 marks the official release, so it won't be much longer now before seeing PulseAudio 10.0 begin to appear in Linux distributions.
  • Experimenting With Virtual GPU Support On Linux 4.10 + Libvirt
    With the Linux 4.10 kernel having initial but limited Intel Graphics Virtualization Tech support, you can begin playing with the experimental virtual GPU support using the upstream kernel and libvirt.

Licensing FUD and Licensing Advice

  • On the Law and Your Open Source License [Ed: Black Duck is just a parasite selling proprietary software by bashing FOSS]
    "Looking back five or ten years, companies managing open source risk were squarely focused on license risk associated with complying with open source licenses," notes a report from Black Duck Software. Fast-forward to today, and the rules and processes surrounding open source licensing are more complex than ever.
  • Explaining the source code requirement in AGPLv3
    This condition was intended to apply mainly to what would now be considered SaaS deployments, although the reach of "interacting remotely through a computer network" should perhaps be read to cover situations going beyond conventional SaaS. The objective was to close a perceived loophole in the ordinary GPL in environments where users make use of functionality provided as a web service, but no distribution of the code providing the functionality occurs. Hence, Section 13 provides an additional source code disclosure requirement beyond the object code distribution triggered requirement contained in GPLv2 Section 3 and GPLv3 and AGPLv3 Section 6.