[EMAIL PROTECTED]
Subject: Re: Problems with OpenOffice 2.3.1 on FreeBSD
Le Mar 1 jan 08 à 21:21:43 +0100, Stephen Montgomery-Smith
<[EMAIL PROTECTED]>
écrivait :
> My personal wish list is that opencascade builds on FreeBSD-7 with the
> new stlport, and that octave-forge not be i
gt; To: Stephen Montgomery-Smith
> Cc: freebsd-questions@freebsd.org; [EMAIL PROTECTED]
> Subject: Re: Problems with OpenOffice 2.3.1 on FreeBSD
>
>
> Le Mar 1 jan 08 à 21:21:43 +0100, Stephen Montgomery-Smith
> <[EMAIL PROTECTED]>
> écrivait :
>
> > My persona
Folks:
If there's a problem with OpenOffice - and there surely is -
complaining here may feel good.
Complaining on "[EMAIL PROTECTED]", however, is _much_
more likely to get the attention necessary to get things fixed.
(Which may still take a while, but hopefully a shorter
Heiko Wundram (Beenic) wrote:
Am Dienstag, 1. Januar 2008 14:15:40 schrieb O. Hartmann:
I use OpenOffice 2.3.1 on several hardwareplatforms running FreeBSD
7.0-PRE/AMD64 and since I upgraded OpenOffice from OO 2.3.0 to 2.3.1 I
have massive problems, rendering OO unusuable! Before doing a PR I wo
Am Dienstag, 1. Januar 2008 14:15:40 schrieb O. Hartmann:
> I use OpenOffice 2.3.1 on several hardwareplatforms running FreeBSD
> 7.0-PRE/AMD64 and since I upgraded OpenOffice from OO 2.3.0 to 2.3.1 I
> have massive problems, rendering OO unusuable! Before doing a PR I would
> like to aks whethere
O. Hartmann wrote:
I use OpenOffice 2.3.1 on several hardwareplatforms running FreeBSD
7.0-PRE/AMD64 and since I upgraded OpenOffice from OO 2.3.0 to 2.3.1 I
have massive problems, rendering OO unusuable! Before doing a PR I would
like to aks whethere there is a solution out.
Whenever I try to
Peter Jeremy writes:
> >This has been discussed within the last two weeks on the
> >openoffice@ list. A message from Peter Jeremy on December 14
> >contains both information about the cause and a patch.
>
> My patch was for a different problem - related to OOo not opening
> any files.
Le Mar 1 jan 08 à 21:21:43 +0100, Stephen Montgomery-Smith <[EMAIL PROTECTED]>
écrivait :
> My personal wish list is that opencascade builds on FreeBSD-7 with the
> new stlport, and that octave-forge not be in its current "IGNORE" state.
> But I fully appreciate that I must either wait, or h
On Tue, Jan 01, 2008 at 10:41:57AM -0500, Robert Huff wrote:
> This has been discussed within the last two weeks on the
>openoffice@ list. A message from Peter Jeremy on December 14
>contains both information about the cause and a patch.
My patch was for a different problem - related to OOo
Predrag Punosevac wrote:
Philipp Ost wrote:
O. Hartmann wrote:
[...]
Whenever I try to save a document in OO writer, OO gets stuck and I
have to kill it. The document gets saved, but I never can load it
again without rendering OO unusuable. Opening M$ Word docs or OO docs
doesn't matter.
I
Robert Huff wrote:
Philipp Ost writes:
> Any ideas? This is a serious situation to me, due to the need of a
> properly working OO :-(
No, perhaps using an other word processor (AbiWord, StarOffice). Or
going back to OOo 2.3.0...
This has been discussed within the last t
Philipp Ost wrote:
O. Hartmann wrote:
[...]
Whenever I try to save a document in OO writer, OO gets stuck and I
have to kill it. The document gets saved, but I never can load it
again without rendering OO unusuable. Opening M$ Word docs or OO docs
doesn't matter.
I have similar problems with
O. Hartmann wrote:
[...]
Whenever I try to save a document in OO writer, OO gets stuck and I have
to kill it. The document gets saved, but I never can load it again
without rendering OO unusuable. Opening M$ Word docs or OO docs doesn't
matter.
I have similar problems with OpenOffice 2.3.1 on
Philipp Ost writes:
> > Any ideas? This is a serious situation to me, due to the need of a
> > properly working OO :-(
>
> No, perhaps using an other word processor (AbiWord, StarOffice). Or
> going back to OOo 2.3.0...
This has been discussed within the last two weeks on the
ope
14 matches
Mail list logo
