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

Re: [tdf-discuss] Re: Installing on Mac OS X


Hi all,

Pardon my intrusion into your fight. For the record I have never seen a Mac. Also, English (US) is 
my native language.

That said, it makes no sense to me for execution of any program one time before adding a language 
pack to it should make it any safer after adding the language pack than waiting to execute it for 
the first time until after an appropriate language pack has been added.

What am I missing in this discussion? I know that I would flee in horror from any program that 
natively had a Greek UI if that program had to be executed once that way before I could install an 
available English language pack. Is this not analogous to the topic under discussion?

As for Larry's protestation that the download did not go wrong, I don't know how anybody can be 
absolutely certain of that. Error checking is very sophisticated now but there is also a very slim 
chance that offsetting corruptions could occur. I would at least try a second download before 
eliminating "bad download" as a possible cause of trouble. <paranoia> Even one chance in 10^100 of 
an error creeping in is still not zero. It's excellent for most purposes -- just not _absolutely_ 
perfect. </paranoia> ;-)

-- 
Jim 

-----Original Message-----
From: Larry Gusaas <larry.gusaas@gmail.com>
To: discuss@documentfoundation.org
Sent: Fri, 18 Dec 2015 12:19
Subject: [tdf-discuss] Re: Installing on Mac OS X

On 2015-12-18, 7:56 AM Uwe Altmann wrote:
Hi Larry

Am 18.12.15 um 10:34 schrieb Larry Gusaas:
No, the download did not go wrong. I also installed the en-GB language
pack. Doing so makes the signing certificate invalid and it can't be
opened unless I switch security settings to "Anywhere". You obviously
didn't read my post clearly.
Maybe your post wasn't clearly enough on this? Also my English is
extremely bad so perhaps I missed the point?

So for this I downloaded en-GB langpack and installed it on my 5.0.4
(with German langpack already installed). Started LO as usual - no
problem. No invalid or invalidated certificate so far. en-GB is
available now. Everything is as it should.

To clarify:
When you download LibreOffice and a language pack and install LibreOffice and then install the 
language pack before opening LibreOffice you will get the error message.

If you have already opened LibreOffice before installing the language pack, like you did, the 
language pack will install and you will not get an error message.

This is a serious issue for non-english speaking  people since they are likely to install the 
language pack before they open LibreOffice.

Installing a language pack before opening LibreOffice modifies the program and makes the 
certificate invalid since it does not cover the modification.

Probably the error message is right and you perhaps got the NSA-Version
of the download ( ;-) - just joking). Try download again from

https://www.libreoffice.org/download/libreoffice-fresh/?type=mac-x86_64&version=&lang=en-GB
Perhaps I should just stick with Apache OpenOffice instead of using a clone.


-- 
_________________________________

Larry I. Gusaas
Moose Jaw, Saskatchewan Canada

-- 
To unsubscribe e-mail to: discuss+unsubscribe@documentfoundation.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


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.