On 09/03/2014, Urmas davian...@gmail.com wrote:
e-letter:
filenames with undesirable characters (e.g. m$
people adding spaces, strokes (/, \) etc.)
Spaces are not 'undesirable characters.' \ and / are both invalid filename
characters in Windows.
All your contribution to this newsgroup is
On Sun, 9 Mar 2014 14:35:50 +0700
Urmas davian...@gmail.com wrote:
e-letter:
filenames with undesirable characters (e.g. m$
people adding spaces, strokes (/, \) etc.)
Spaces are not 'undesirable characters.' \ and / are both invalid filename
characters in Windows.
All your contribution
On Mon, 10 Mar 2014 13:55:12 +
e-letter inp...@gmail.com wrote:
On 09/03/2014, Urmas davian...@gmail.com wrote:
e-letter:
filenames with undesirable characters (e.g. m$
people adding spaces, strokes (/, \) etc.)
Spaces are not 'undesirable characters.' \ and / are both invalid
Hi :)
It is possible to still get earlier versions of LO! Install in
parallel or into a virtual machine or on a dual-boot or something.
The in parallel is probably easiest unless you already have another
reason for having a vm or dual-boot.
Regards from
Tom :)
On 6 March 2014 01:51, Steve
On 2014-03-06 05:51, Ed_0 wrote:
On 05/03/14 10:08, e-letter wrote:
On 04/03/2014, Ed_0 x9...@mail.ru wrote:
Hi,
I would like to know, why does libreoffice open up after running in a
terminal libreoffice --convert-to odt *.doc?
It should not do this. Check your installation again. (E.g:
Hi :)
Not sure about most of that but point 2
ls is the same as
ls . and
ls ./
it's just a bit of cleverness to try to get around weird limitations.
There shouldn't be any difference but what should be and what is are
sometimes different.
From the summary, i agree that it would be nice to
On 05/03/2014 20:16, Steve Edmonds wrote:
On 2014-03-06 05:51, Ed_0 wrote:
On 05/03/14 10:08, e-letter wrote:
On 04/03/2014, Ed_0 x9...@mail.ru wrote:
Hi,
I would like to know, why does libreoffice open up after running in a
terminal libreoffice --convert-to odt *.doc?
It should not do
On 05/03/2014, Ed_0 x9...@mail.ru wrote:
1) Hmm, I didn't understand those links, the errors displayed are these:
javaldx: Could not find a Java Runtime Environment!
Warning: failed to read path from javaldx
You have another problem; activation of hyperlinks doesn't require java...
2)
