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

Hi :)
I meant to the LibreOffice bug-reporting system;
I'm not sure whether it'd be better to mark as a "feature request" or keep
as a standard bug-report so just do the default for now.

If you have already filed a bug-report with Mendeley then it'd be great to
include a clickable link to that in your report to the LibreOffice people.
If the Mendeley people are being nice then it'd be nice to copy the new
link from your bug-report here to them but they sound a bit unfriendly so i
would leave that for a couple of days - that gives the LibreOffice people
have more of a chance of "getting up to speed".
Regards from
Tom :)

On 1 April 2015 at 13:33, Sun Shine <> wrote:

 Hello Tom

Nice to hear from you, and thanks for the suggestion.

Can you clarify: did you mean post a bug report to the LibO developers or
to the Mendeley people (who seem to want to pass the buck onto LibO)?

For the LibO folk, is there a protocol one follows - e.g. is it via an
email list or a website or ... ?

Thanks again.

On 01/04/15 12:30, Tom Davies wrote:

  Hi :)
 Maybe post a bug-report about it and maybe copy&paste what you just wrote
in that email into there?

 Maybe say that you suspect that our Devs might be better at communicating
with their devs to get the issue resolved?
 Regards from
 Tom :)

On 1 April 2015 at 09:08, Sun Shine <> wrote:

Hi list

This follows up on an email written earlier this year regarding a
time-lag in LibO when using Mendeley Desktop plugin [ ]. At the
time of writing, I thought this was a LibO issue, but it seems more like a
Mendeley Desktop (MD) issue:

I wrote to MD support to ask about progress made in response to a cohort
of other LibO users who have posted to the MD website reporting similar
time lags in using the MD insert citations plugin. Josh, a support person
at MD, responded that no work had been undertaken on this because it was
"deemed to be a LO problem in how they process fieldcodes".

I responded that since LibO is open source and that Mendeley developed
the plugin for LibO this is a Mendeley issue ... but this has resulted in a
deafening silence from MD!

What field codes is Josh referring to and is there anything I as a lowly
end-user can do to fix this, at least locally? Is this something that LibO
developers are able to address with MD to facilitate uptake among
universities of LibO, many of which would also use Mendeley?

For specs, I'm running LibO on Mint 17, using the latest Mendeley
Desktop and plugin versions.

Thanks for any suggestions


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.