Oliver Brinzing wrote:
Hi,
a short question's regarding path's:
Is it generally a good idea to have space's and the version number
(for example OOo-dev 3.0, Basis 3.0,...) inside the oo install
path's ?
spaces: no idea if that is good or bad; when coming up with Basis 3.0
I just followed
Hi,
spaces: no idea if that is good or bad; when coming up with Basis 3.0
I just followed prior art (OpenOffice.org 2.4)
that's true, but till oo 2.4 one had a chance to install to a path
without spaces and version numbering, like c:\programs\openoffice.
that's not possible anymore ...
Oliver Brinzing wrote:
Hi,
spaces: no idea if that is good or bad; when coming up with Basis
3.0 I just followed prior art (OpenOffice.org 2.4)
that's true, but till oo 2.4 one had a chance to install to a path
without spaces and version numbering, like c:\programs\openoffice.
that's not
Stephan Bergmann wrote:
Applications on Windows are notorious for having problems with long file
system paths. Some expert on Windows can probably give more insight
into the topic in general. For OOo, the situation has always been that
it can start to fail in mysterious ways if the
Hi,
a short question's regarding path's:
Is it generally a good idea to have space's and the version number
(for example OOo-dev 3.0, Basis 3.0,...) inside the oo install path's ?
This can be a trouble source too, if one needs to do installation using simple
batch scripts ...
Oliver
GnuPG
Applications on Windows are notorious for having problems with long file
system paths. Some expert on Windows can probably give more insight
into the topic in general. For OOo, the situation has always been that
it can start to fail in mysterious ways if the installation path or the
user
Hi Stephan,
Stephan Bergmann wrote (9-4-2008 11:47)
[...]
In short: If your OOo installation on Windows behaves strange, maybe
you should install it into a shorter path. :(
My OOo installation will suffer less than my OpenOffice.org
installation. (hint).
Regards,
Cor
--
The Year of 3
