hi.
i have a word documents that include password.
when i want to open one of it, it needs one hour and 45 minute to open.
libreoffice should can open it but in a very long time.
when i open it, it does not request password from me and run properly.
On 10/5/16, Dave Liesse
On 10/04/2016 10:06 PM, V Stuart Foote wrote:
> James Knott wrote
>> Neither of them currently uses soffice. LibreOffice uses libreoffice
>> and OpenOffice uses openoffice4.
> Sorry, Dave is correct.
>
> Those actually are names of the AppData folders holding the user profile,
> both programs on
James Knott wrote
> Neither of them currently uses soffice. LibreOffice uses libreoffice
> and OpenOffice uses openoffice4.
Sorry, Dave is correct.
Those actually are names of the AppData folders holding the user profile,
both programs on Windows builds use a mixed--soffice.exe launcher and
On 10/04/2016 11:35 AM, Tom Davies wrote:
> Thanks :) I think it used to be quite noticeable. Whichever one was open
> first (including quick-starter if that was enabled) would stay fine but the
> 2nd instance wouldn't open, or would get part-way open and then crash.
>
> I think the problem was
Is LO capable of opening an XLSX file that has a password? I tried it
with v4.0 and LO thought it was a CSV file. I just tried with v5.2.1.2
and LO at least recognizes that there's a password but won't accept it.
I'm sure this isn't the only client that's going to do this to me, so
want to
Tom et al.,
I looked at this a while back and discovered that on my Slackware
system, LO and AOO are installed into separate sub-directories in /opt,
with symlinks in /usr/bin with different names pointing to the
appropriate soffice. soffice seems to be some sort of legacy name from
the old
Hi Kamil,
Kamil Landa wrote on 03-10-16 12:40:
> How to get the current language using on keyboard (actual display
> language) in Libreoffice Basic? I want to create macro for Writer
> which will do -> if current language is English do thing1, if current
> language is Czech do thing2.
No
On 04/10/2016 15:35, Tom Davies wrote:
> I think the problem was caused by LibreOffice and OpenOffice (and i think
> the various forks which have now mostly merged back into LO or AOO afaik)
> using the same command to open;
> soffice
That is a problem when one doesn't use the full path, when
Hi :)
Thanks :) I think it used to be quite noticeable. Whichever one was open
first (including quick-starter if that was enabled) would stay fine but the
2nd instance wouldn't open, or would get part-way open and then crash.
I think the problem was caused by LibreOffice and OpenOffice (and i
