All I said was this isn't the appropriate place to discuss w/e opinions
you have. You've gotten a crystal clear answer, your responses are "sure
Java has some issues but TDF has a responsibility to offer some hacky
solution to work around THEIR bug." We've rejected that proposal (which
is pretty obvious why we would) and yet you continue to say the same
thing. If there are open bug reports - awesome. There is no need for
more (in particular since you're not offering to help implement a fix).
I'll dare to ask....have you bothered Java with perpetual emails about
THEIR bug or are you sticking solely to this list?
Best,
Joel
On 03/11/2016 04:29 PM, Larry Gusaas wrote:
On 2016-03-11, 5:55 PM Joel Madero wrote:
In short....no.
Gee. Very in-depth answer.
Or do you, like some others here, not care about Mac users perceptions
of LibreOffice?
Since I am not on the developer list (and it is not available through
Gmane, which is the only way I follow these and other lists) this
seemed like the most appropriate list.
--
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
[tdf-discuss] Re: Java still broke on LibreOffice 5.1.1 · Larry Evans
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.