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


check the archives




________________________________
From: Simon Cropper <simoncropper@fossworkflowguides.com>
To: users@global.libreoffice.org 
Sent: Tuesday, 5 June 2012 11:02 AM
Subject: Re: [libreoffice-users] LO 3.5 w/zotero crashing on export?

Ditto.

I have never seen your posts on Zotero or PDF. I require both and all versions of LO have 
supported this functionality since it forked from OO.

On 05/06/12 04:11, Marc Grober wrote:
Whoa! You posted concerns re exporting LO 3.5 to PDF w zotero entries? Sorry, but never saw the 
post and it's news to me as my install of 3.5.3.2 works perfectly with export of zotero cites 
and works cited to PDF -AND I would be very put out if it stopped working. Could someone point 
me to the current bug on this? Not to say a bug will be addressed (the quicklook issue has not 
been touched  though the solution appeared to be available) but it's nice to keep an eye on 
such.....

On Jun 4, 2012, at 8:42 AM, RustyRiley<russwilsonau@yahoo.com.au>  wrote:

It's crucial that people test each particular use of an application, and THEN
decide.

I've gone to using Apache OpenOffice V3.0, as LO seems to have "fallen over"
badly -- none of the responses I got in response to a problem I was
experiencing with using Zotero were even minimally useful to me, so I gave
up LO but still get the user help messages, still being subscribed to that
list.

Trying to get LO 3.5 (and now 3.5.4) to export a file with Zotero entries to
PDF causes LO to crash, it successfully saves the file, and I think that's
an advance on where it was before

but being able to use Zotero AND export to PDF are CRUCIAL for me, so, as I
said, it's back to AOO, I'm not even bothering with LO as I basically use
it, currently, as a wordprocessor only (with Zotero support).

so much for advances in the product -- depends on what "ready" means, I
guess, 3.5.4 is NOT ready for me, but still showing signs of some sort of
"reversion" (sorry I can't be more helpful in specifying -- as I've just
demonstrated, I'm not even au fait with using Nabble!)

--
View this message in context: 
http://nabble.documentfoundation.org/Is-3-5-4-ready-for-business-users-tp3987579p3988101.html
Sent from the Users mailing list archive at Nabble.com.


-- Cheers Simon

   Simon Cropper - Open Content Creator / Website Administrator

   Free and Open Source Software Workflow Guides
   ------------------------------------------------------------
   Introduction              http://www.fossworkflowguides.com
   GIS Packages          http://www.fossworkflowguides.com/gis
   bash / Python    http://www.fossworkflowguides.com/scripting

-- For unsubscribe instructions e-mail to: users+help@global.libreoffice.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.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted




-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.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.libreoffice.org/global/users/
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.