From: Uwe Siart <uwe.siart@tum.de>
To: "Roland Winkler" <winkler@gnu.org>
Cc: 10254@debbugs.gnu.org
Subject: bug#10254: 24.0.92; Local variable bibtex-dialect has no effect
Date: Wed, 11 Jan 2012 07:41:22 +0100 [thread overview]
Message-ID: <84boqa4u7h.fsf@tum.de> (raw)
In-Reply-To: <20236.33909.640904.783097@gargle.gargle.HOWL> (Roland Winkler's message of "Tue, 10 Jan 2012 12:33:25 -0600")
"Roland Winkler" <winkler@gnu.org> writes:
> Do you want to use buffer-local values of bibtex-dialect because you
> do have multiple BibTeX files, some of which use one BibTeX dialect,
> others use another dialect?
Exactly, yes.
> Such a scenario is somewhat orthogonal to the general notion of BibTeX
> that should provide one database that is used for all LaTeX documents.
Surely I use centrally managed bibfiles. They reside in
~/texmf/bibtex/bib/siart. Since I do not like one huge monolithic
bibfile my database is split across several files where each file is
dedicated to a certain topic. But with a bibfile local to a certain
document BibTeX is also much superior to filling {thebibliography} by
hand.
But this is not the point here. The point is that classical bibstyles
and biblatex are not compatible at bibfile level. A bibfile can only be
used either for bibstyles or for biblatex. In my case mostly due to the
different handling of the month and language fields.
It is IMO not a rare case that one has to use both biblatex and
bibstyles. If I need to implement a certain requirement for the
bibliography that can only be solved by biblatex (e.g. a particular
sorting scheme) I will need to create a bibfile for biblatex. On the
other hand I can not simply throw away all the achivements of classical
bibstyle. Moreover, if a publisher provides a template bibstyle I have
to use it. No way to convince a publisher to switch his workflow to
biblatex immediately.
So I am in a situation where I have to manage both bibtex dialects at
the same time in different files. I don't think that this is really
against the BibTeX paradigm. It's just that we now have both options
(bibstyle and biblatex) and they are not compatible.
> Also, I do not consider this a bug. In my opinion, it's more a missing
> feature.
I got your point and I fully agree. I never meant to decide whether it
is a bug or not. At the time when I filed a bug report I just observed
that setting a buffer-local variable had no effect while click in the
menue worked. This looked like a bug to me at that time.
--
Uwe
next prev parent reply other threads:[~2012-01-11 6:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 7:29 bug#10254: 24.0.92; Local variable bibtex-dialect has no effect Uwe Siart
2011-12-10 7:43 ` Glenn Morris
2011-12-10 9:12 ` Uwe Siart
2012-01-10 1:24 ` Glenn Morris
2012-01-10 18:33 ` Roland Winkler
2012-01-11 6:41 ` Uwe Siart [this message]
2012-01-11 10:46 ` Roland Winkler
2012-01-11 14:57 ` Uwe Siart
2012-01-15 9:04 ` Roland Winkler
2012-01-16 14:14 ` Stefan Monnier
2012-01-16 22:21 ` Roland Winkler
2012-01-17 5:44 ` Uwe Siart
2012-01-17 14:04 ` Stefan Monnier
2012-01-17 20:45 ` Roland Winkler
2012-01-17 21:21 ` Stefan Monnier
2012-01-28 8:17 ` Roland Winkler
2012-01-28 14:05 ` Chong Yidong
2012-01-28 18:13 ` Roland Winkler
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84boqa4u7h.fsf@tum.de \
--to=uwe.siart@tum.de \
--cc=10254@debbugs.gnu.org \
--cc=winkler@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).