From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: bibliography again: “von” and “van”
Date: Thu, 29 Jan 2015 13:53:31 +0100 [thread overview]
Message-ID: <19nd3vk18kbt7$.dlg@nililand.de> (raw)
In-Reply-To: <CADAJKhB-WJdYUND_kKHxU3CVDFCGL9LOiz4w3q4h+EVNoZ=XQw@mail.gmail.com>
Am Thu, 29 Jan 2015 13:06:59 +0100 schrieb BPJ:
> How is a prefix identified as such with this technique?
biber uses the btparse library
(http://search.cpan.org/~ambs/Text-BibTeX-0.70/btparse/doc/bt_split_names.pod)
and prefixes ("von-Parts") are more or less identifyed by lowercase
letters (as in bibtex, see also tamethebeast.pdf). I actually run
once into a problem with a lowercase name which biber didn't like:
https://github.com/plk/biber/issues/43
There are some tricks, like \uppercase{d}, commands, braces, which
one can use to fine-tune the name parsing.
> Is there a hardcoded list somewhere or is it "name begins with a
> 'word' in lowercase". IMHO it would be desirable that the prefix
> itself could be specified in a field.
Well the main problem is that authors are name *lists*, and that
there can be more then one name list in an entry.
But biblatex is extensible. You can, if you want, define a new field
say "authorprefixes={de,von,none,Bbla}" and then write suitable
macros that uses this prefixes instead of the one parsed from the
name. But I doubt that it is really needed. One shouldn't
overcomplicate a system only to catch every special case.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2015-01-29 12:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 18:20 Jörg Weger
2015-01-27 19:16 ` Keith Schultz
2015-01-27 20:11 ` Jörg Weger
2015-01-28 12:00 ` Ulrike Fischer
2015-01-29 12:06 ` BPJ
2015-01-29 12:53 ` Ulrike Fischer [this message]
2015-01-27 20:50 ` Hans Hagen
2015-01-28 3:10 ` Alan BRASLAU
2015-01-28 5:03 ` Jörg Weger
2015-01-28 10:15 ` Keith Schultz
2015-01-31 10:18 ` Hans Hagen
2015-01-28 4:51 ` Jörg Weger
[not found] <mailman.1.1422442801.15564.ntg-context@ntg.nl>
2015-01-29 9:29 ` Robert Blackstone
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='19nd3vk18kbt7$.dlg@nililand.de' \
--to=news3@nililand.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).