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: publications and custom author separator
Date: Mon, 31 Aug 2009 15:10:27 +0200	[thread overview]
Message-ID: <6faad9f00908310610v3a6def4teb70859369de4b8@mail.gmail.com> (raw)
In-Reply-To: <0CA2EC3C-D2AE-4B4E-9309-0526F39DB09A@gmail.com>

On Mon, Aug 31, 2009 at 01:55, Črt Gorup wrote:
> Hi
>
> I am trying to replace ('in' instead of 'and') a  separator between the last
> two authors for every article, but I am facing a semi success. My approach
> was to set the variable finalnamesep in \setuppublicationlist. At the moment
> it is working only when there are three or more authors per entry.
>
> This example with 5 authors is ok, there is 'in' between last two authors.
>
> Rong-En Fan, Kai-Wei Chang, Cho-Jui Hsieh, Xiang-Rui Wang in Chih-Jen
> Lin, LIBLINEAR: A library for large linear classification v Journal of
> Machine
> Learning Research, 2008.
>
>
> This example has only 2 authors, there should be 'in' instead of 'and'.
>
> T. M. J. Fruchterman and E. M. Reingold, Graph drawing by force-directed
> placement v Software: Practice and Experience, št. 11, zv. 21, str.
> 1129-1164,
> 1991.
>
>
> Does anybody have any idea?

There's a long list of adjustments that one needs to make. See
bibl-num.tex or bibl-yourcitingstyle.tex for example (I might be that
I'm looking into the old module, so don't take my word for it). There
are lots of places such as:

\setupcite
       [author,year]
       [\c!andtext={ and },
        \c!otherstext={ et al.},
        \c!pubsep={, },
        \c!lastpubsep={ and },
        \c!compress=\v!no,
        \c!inbetween={ },
        \c!left={(},
        \c!right={)}]

\setupcite
       [authoryear]
       [\c!andtext={ and },
        \c!otherstext={ et al.},
        \c!pubsep={, },
        \c!lastpubsep={ and },
        \c!compress=\v!no,
        \c!inbetween={ },
        \c!left={(},
        \c!right={)}]

(you would normally leave the \c! out of course).

But the idea is to rewrite that file completely (see bibl-num-fr.tex
for example), so that you can also change "page" into "str" etc.

If you have done that already or planning to do it or if you have half
an hour of free time in the following days ... let me know. I would be
interested to get the file translated as well (though I would only
need it until Friday or not at all for the next few years :).

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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      parent reply	other threads:[~2009-08-31 13:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-30 23:55 Črt Gorup
2009-08-31  1:01 ` David Rogers
2009-08-31 13:10 ` Mojca Miklavec [this message]

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=6faad9f00908310610v3a6def4teb70859369de4b8@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).