ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pontus Lurcock <pont@talvi.net>
To: ntg-context@ntg.nl
Subject: Re: undefined control sequence bug with German	umlaut in bibliography
Date: Sat, 4 Jun 2011 22:07:30 +1200	[thread overview]
Message-ID: <20110604100730.GL20248@rae.vm.bytemark.co.uk> (raw)
In-Reply-To: <BANLkTi=0HKzbGU+j+OxaWTeYLCdbFZ5m9g@mail.gmail.com>

On Sat 04 Jun 2011, Julian Becker wrote:

> I'm not familiar with the intricacies and details of UTF8 encoding,
> but is it possible that there is a byte missing from the "ä" which
> has been cut off during the abbreviation process?

Well, there *is* more than one way to represent ä in UTF-8, but it's
my understanding that anything beyond ASCII is simply not supported by
BibTeX. You can get away with it in fields that just get pasted
verbatim into the output (usually), but the first three letters of the
first author's name are used to construct the key (which is why
‘Schräger’ worked) so there's no way around using the officially
sanctioned {\"a} form.

> > unfortunately, I'm using Mendeley Desktop for the management of my
> > bibtex file and I can't seem to be able to influence the way in
> > which it encodes the special characters.

This is one reason why I still use plain emacs as a bibliography
manager -- sooner or later you need a hack, and that's harder when the
raw BibTeX is hidden or generated. In this case you may need to
put the hack between Mendeley and BibTeX: pipe the file through 
‘sed -e 's/ä/{\\"a}/g'’ or something similar. And/or ask in the Mendeley 
support forums, since this is a fairly well-known BibTeX ‘feature’
so perhaps someone else has had to deal with it there.

Hope this helps,

Pont
___________________________________________________________________________________
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
___________________________________________________________________________________

  parent reply	other threads:[~2011-06-04 10:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03 18:38 Julian Becker
2011-06-03 19:03 ` Thomas A. Schmitz
2011-06-04  0:31   ` Pontus Lurcock
2011-06-04  8:43     ` Julian Becker
2011-06-04  9:23       ` Julian Becker
2011-06-04  9:26         ` Taco Hoekwater
2011-06-07  7:42           ` Ulrike Fischer
2011-06-04 10:07         ` Pontus Lurcock [this message]
2011-06-04 10:32           ` Julian Becker
2011-06-06 10:11           ` Arthur Reutenauer
2011-06-06 10:29             ` Pontus Lurcock
2011-06-06 10:44               ` Arthur Reutenauer

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=20110604100730.GL20248@rae.vm.bytemark.co.uk \
    --to=pont@talvi.net \
    --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).