Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

On 01/27/2011 03:34 AM, Michael Meeks wrote:
Hi there,

On Tue, 2011-01-25 at 18:43 -0800, NoOp wrote:
It also still uses soffice.exe et all in Windows; meaning that LO still
takes over OOo if both are installed in parallel.

      Unfortunately, there is some inevitability of conflict here. This would
have always been the situation between StarOffice and OpenOffice in the
past eg. AFAIK (and I am no expert), we would both want to clobber the
same COM component names - and remove them socially on uninstall etc.
Short of the typical "I notice XYZ other app is the default, do you want
to change to me" type code that would need adding on both sides, there
will be issues here for a while.

 The latter seems MS like; are LO insistent on obliterating OOo by
continuing to use OOo registry entries and executable file names?

      If you install OO.o over LO - you will find it does the same thing;
there is no malice implied on either side.

Actually OOo does not. I just tested OOo final 3.3.0 on WinXP and it
does not disturb LO. Right-clicking on an .odt and selecting 'Open With'
offers: Writer (OOo 3.3.0 stable was installed after LO)
LibreOffice Writer (RC4/Stable is installed)
Microsoft Word

I suggest that you revisit the "Change executable/sh names" thread that
I started on the dev list.

That SVG import still is incomplete and doesn't work properly. In fact
SVG import is pretty much an ongoing joke (whether it be OOo-go-oo or LO).

      Well; it does something useful; we (and you) are welcome to make it
better. In my view, something useful is almost always better than
nothing, even if it is not perfect. Perhaps the most serious thing it
does is showcase the poor performance of draw with lots of complex
shapes - something that is intrinsic to draw, but of course not seen if
you don't load any data into it ;-)

Perhaps 'ongoing joke' was a little harsh & I offer my apologies to
Bernhard Haumacher & any devs that have been working on it since then.
However the problem(s) have been ongoing for years (starting in 2005 +

My point was; promoting a broken feature as key reason to switch to LO
seems to me to be misguided. You know it's broke, I know it's broke, and
the multiple (years old) bug reports validate my opinion.  It really
doesn't matter if the issue is with Draw or the SVG extension/code, the
issue is/was the press release promoting a "feature" with significant

Sorry, but IMO RC4/Final should have waited awhile until some of the
more basic bugs were resolved.

      I am sorry you think so. But rest assured, you'll have plenty of time
to fix and test bug fixes for 3.3.1 with us all. It is not as if the
baseline we are starting from is bug-free perfection too.

Happy to help in any way that I can. BTW these might be worth a
look/relook as well:
[[upstream] export of openoffice draw to svg renders text invisable in
the svg file] - note my post of 2008
[[Linux] LibORC2: Impress video / `GLIBCXX_3.4.11' not found]
[ [FILESAVE] LibO stops responding saving particular documents as .doc]
If you look at the history,>
you'll find that was discovered in RC2.

There's more, but that's enough for this response.

I'm quite happy to help via troubleshooting/testing etc., but IMO taking
a fast track to release so soon after RC4 (which is the stable release)
is an indication that the releases are timed to distros/other events. I
think it better to slow things down and release 'when LO are ready'
rather than on buttons pushed by outside sources.

Unsubscribe instructions: E-mail to
*** All posts to this list are publicly archived for eternity ***


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.