ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wagner Macedo <wagnerluis1982@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Is it possible to \cite with UPPERCASED author?
Date: Fri, 10 Feb 2012 16:27:27 -0300	[thread overview]
Message-ID: <CAKGY2PmO=2nAype6qZWnba6yat7mE=QvK9gZN8AL52yEZNbAHg@mail.gmail.com> (raw)
In-Reply-To: <4F3538C1.1040509@uni-bonn.de>


[-- Attachment #1.1: Type: text/plain, Size: 1596 bytes --]

On 10 February 2012 12:33, Thomas A. Schmitz <thomas.schmitz@uni-bonn.de>wrote:

> 1. Edit a local copy of cont-au.bst and insert a function that will make
> the author name uppercase. bst is infamous for its incomprehensible syntax,
> but it appears to be possible. this would be the proper way. google is your
> friend here.
>

Yes, very incomprehensible. And another thing, I couldn't find any
"authoryear" word inside bst files. I think it usefulness is only for
publications list.


>  2. ConTeXt produces a .bbl file from which it retrieves the
> bibliographical information. The authorname used in the \cite command is
> captured in a key=value of the form
> a={{Hagen}},
> Write a simple lua script which will make the captured name uppercase and
> write everything out to a new file. Then, in your preamble, replace the
> \setupbibtex[database=...] line with
> \usepublications[<name>.bbl]
> So this is something you would do at the very end of the editing process,
> when you're sure that all the references are in the bbl file.
>

Thank you. It's the best solution to my problem. But I'll do a Python or
Bash script to do this, as I'm more used to those languages, and I'll add
as a target on my Makefile.


> It may also be possible to hook a lua function into the process when
> ConTeXt typesets the value from the bbl, but that's beyond my knowledge,
> Hans is the only one who knows the internals of the mkiv bib mechanism well
> enough to say if/how this may work.
>

I found something into bibl-bib.lua, and I tried to change but didn't
result in anything. So, it's a black box.

[-- Attachment #1.2: Type: text/html, Size: 2247 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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:[~2012-02-10 19:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 10:59 Wagner Macedo
2012-02-10 11:23 ` Thomas A. Schmitz
2012-02-10 11:58   ` Wagner Macedo
2012-02-10 12:40     ` Thomas A. Schmitz
2012-02-10 14:10       ` Wagner Macedo
2012-02-10 15:33         ` Thomas A. Schmitz
2012-02-10 19:27           ` Wagner Macedo [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='CAKGY2PmO=2nAype6qZWnba6yat7mE=QvK9gZN8AL52yEZNbAHg@mail.gmail.com' \
    --to=wagnerluis1982@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).