ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Unicode bibliography
Date: Tue, 27 Apr 2010 10:44:51 +0200	[thread overview]
Message-ID: <n2u6faad9f01004270144j27ce5352n7b081d02950ed74@mail.gmail.com> (raw)
In-Reply-To: <OFB107C32B.269946D3-ON80257712.002B6CA8-80257712.002BBA3E@converteam.com>

On Tue, Apr 27, 2010 at 10:14, Michael Saunders wrote:
>
> What do you use now?  Is there something better?

I don't know any better tool. JabRef seems great.

On Tue, Apr 27, 2010 at 09:57,  <richard.stephens@converteam.com> wrote:
>
>> Long ago (when I was still using JabRef) I was thinking about creating
>> support for export into ConTeXt-specific format.
>
> What a teaser! So if you're not using JabRef now, what are you using and
> why?

Eeeeem ... vim (or TextMate), but I guess that's not the answer you
were expecting.

As for the "why" part:
1.) I don't have too many references to manage/work with.
2.) One of the reasons for not actually writing support for ConTeXt
output in JabRef was that ConTeXt is able to read bib files; and one
of the reasons why I started using just plain text editor was that
JabRef didn't create such a ConTeXt-friendly format.
3.) Until 2005 I was more heavily engaged in the field where almost
every article I had to cite was in PubMed which is no longer true.
JabRef has an enourmous added value when one needs to use citeseer or
PubMed. What I would need now would be DOI2bib converter. As soon as
the time spent on copy-pasting data from article web pages to bib
files will outweight the time spent writing the converter, I'll
probably start writing one (but that still won't be comparable with
JabRef).

What still makes me wonder is tha fact that there are problems with
Unicode. I don't remember any, though I admit that I'm not sure if I
ever cited any non-English item.

Mojca
___________________________________________________________________________________
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:[~2010-04-27  8:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.749.1272353013.4277.ntg-context@ntg.nl>
2010-04-27  7:57 ` richard.stephens
2010-04-27  8:44   ` Mojca Miklavec [this message]
2010-04-27 10:49 Michael Saunders
  -- strict thread matches above, loose matches on Subject: below --
2010-04-27  8:14 Michael Saunders
2010-04-27  3:24 Michael Saunders
2010-04-27  6:05 ` Taco Hoekwater
2010-04-27  6:49 ` Mojca Miklavec

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=n2u6faad9f01004270144j27ce5352n7b081d02950ed74@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).