ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Stefan Müller" <warrence.stm@gmx.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: OT: What reference management software do you use?
Date: Mon, 23 May 2011 23:17:42 +0200	[thread overview]
Message-ID: <4DDACEF6.2060803@gmx.de> (raw)
In-Reply-To: <5E91BCE6-9B40-4E7E-925D-513E33A833F1@uni-bonn.de>

Okay, then I should definitely take a look at JabRef. Anyhow, maybe I'm 
naive here, but I don't see a reason why Zotero should support BibTeX 
Strings. If I type the BibTeX file manually, sure. But Zotero reads the 
(e.g.) Journal names from the corresponding websites, so there should be 
no need to replace those with abbreviations. Is it because I don't 
understand BibTeX strings?

Does JabRef offers synchronisation (e.g. WebDAV) between different machines?

Stefan

On 23.05.2011 23:00, Thomas A. Schmitz wrote:
>
> On May 23, 2011, at 10:45 PM, Stefan Müller wrote:
>
>> +1 for Zotero
>>
>> I tried Mendeley some time ago. It's standalone but sill quite similar to Zotero. "Browser-integration" works via a special bookmark. It also has an embedded pdf-viewer, which is very neat. Reason for changing to Zotereo were some strange bibtex-export issues, where the bibtex file got messed up and had to be readjusted manually.
>
> I find Zotero useless for my work with ConTeXt. You cannot have cross-references within your bibliographic items, and it is impossible to have proper markup in bibliographical items. For me, both are absolute killer arguments; I cannot work with zotero. And the bibtex export sucks; important features such as bibtex strings are not supported. So I would actually recommend jabref if you need a cross-platform tool or bibdesk if you're using OS X exclusively. Regarding a system when you write your context files: I use Emacs, and I haven't seen anything more powerful or more convenient than reftex (which also works with context, after a few tweaks in your configuration file).
>
> Thomas
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2011-05-23 21:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21 12:19 Paul Menzel
2011-05-22 19:55 ` Joerg.Hagmann
2011-05-22 20:14   ` Otso Helenius
2011-05-23 20:45     ` Stefan Müller
2011-05-23 21:00       ` Thomas A. Schmitz
2011-05-23 21:17         ` Stefan Müller [this message]
2011-05-23 21:32           ` John Haltiwanger
2011-05-23 21:38             ` Otso Helenius
2011-05-23 21:47             ` Thomas A. Schmitz
2011-05-24  7:16               ` Stefan Müller
2011-05-23 21:37           ` Pontus Lurcock
2011-05-22 22:01 ` Pontus Lurcock

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4DDACEF6.2060803@gmx.de \
    --to=warrence.stm@gmx.de \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).