From: gnwiii@gmail.com
Subject: Re: Specifying BibTeX engine
Date: Sat, 4 Nov 2006 11:09:03 -0400 [thread overview]
Message-ID: <22af238a0611040709r4bbd8292j56bcc26917b8017a@mail.gmail.com> (raw)
In-Reply-To: <eihmju$9on$1@sea.gmane.org>
On 11/4/06, Philipp Reichmuth <reichmuth@web.de> wrote:
> Hi,
>
> texexec has been doing the necessary BibTeX calls for some time now, but
> is there a way to configure which BibTeX engine is being called? I am
> using BibTeX 8 (because of Unicode in my bibliography) and have been
> renaming the executable so far, but it seems there should be a better way.
I've been editing the installprogram line found with:
$ grep bibtex $(kpsewhich t-bib.tex)
%D \item bibtex is now registered as a program to be run by texexec (8/8/2006)
%D \item support mlbibtex
2: file -- not found, waiting for bibtex
\def\setupbibtex{\dosingleempty\dosetupbibtex}
\def\dosetupbibtex[#1]%
\installprogram{bibtex \jobname}}}
%D This is the result of bibtex's `language' field.
to replace "bibtex" with "ctxbibtex", which is a shell script I can edit
to use bibtex8, etc. with appropriate arguments (e.g., for very
large .bib files) as well as encoding tricks. A dirty hack is to put an
\installprogram{ctxbibtex \jobname}}}
line in your file (after the other setup). The job runs bibtex and
then ctxbibtex, so you end up with the results of whatever is in your
script.
In MiKTeX-2.5 this works using "ctxbibtex.cmd" scripts.
> (Incidentally, I've been using a Python script to convert BibTeX files
> between Unicode and {\=a}-style accent notation and am currently
> thinking of putting in ConTeXt {\adiaeresis}-style accents as well;
> would this be of interest to anyone?)
I use GNU recode for this, but not with ConTeXt, where
"\enableregime[utf]" has been working with my utf8 bibliography, so
I haven't needed ConTeXt {\adiaeresis}-style accents. My main concern
is searchable .pdf files, where the default Adobe Reader configuration
at work (Win32) seems to use plain old "a" in searches when I enter á,
etc. (search for xáy finds xay, xày, etc.).
I'd prefer to see a context encoding added to GNU recode for the
benefit of future archeologists trying to decipher ancient documents.
--
George N. White III <aa056@chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia
next prev parent reply other threads:[~2006-11-04 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-04 9:30 Philipp Reichmuth
2006-11-04 9:53 ` Taco Hoekwater
2006-11-04 10:05 ` Philipp Reichmuth
2006-11-04 15:09 ` gnwiii [this message]
2006-11-04 16:19 ` Unicode stuff (was: Re: Specifying BibTeX engine) Philipp Reichmuth
2006-11-09 16:47 ` Mojca Miklavec
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=22af238a0611040709r4bbd8292j56bcc26917b8017a@mail.gmail.com \
--to=gnwiii@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).