From: Marco Patzer <lists@homerow.info>
To: ntg-context@ntg.nl
Subject: Re: No bibliography in the output, depends on file name
Date: Fri, 17 Jan 2014 13:15:57 +0100 [thread overview]
Message-ID: <20140117121557.GA4495@homerow> (raw)
In-Reply-To: <nvitacolonna-F46457.15024715012014@news.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1537 bytes --]
On 2014–01–15 Nicola wrote:
> maybe this is a known issue,
It's a known fact that context has a different notion of valid file
names than your operating system does. This is by design. To quote
the manual:
“It is highly recommended, that all input files, i.e. the ConTEXt
source and other included files such as image files, have only the
letters a–z, digits and dashes in their names, that is in the
names of their full paths, otherwise you can easily get into
problems.”
> I'm writing a ConTeXt document called modern-c++.tex (in OS X 10.7.5). The
> content of the file is:
>
> \setupbibtex[database={modern-c++}, sort=author]
> \setuppublications[numbering=yes]
> \starttext
> \completepublications[criterium=all]
> \stoptext
Especially since c++ didn't work out, I expected dropping the “++”
would work (“modern-c”), but it didn't. So I ran some tracing:
\enabletrackers [resolvers.readfile]
\starttext
\readfile{file++.ext}{}{}
\stoptext
This reports:
files > readfile > not found by tree lookup: file .ext
Which means the “++” is replaced by two spaces, instead of searching
for “file++.ext” or “file.ext” which is what I had expected. I
didn't dig into the code to check where the spaces creep in.
Regardless if this particular issue gets fixed or not, I doubt that
Hans will put much effort into general support for “esoteric” file
names. So, it's best to avoid plus signs in file names.
Marco
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 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
___________________________________________________________________________________
next prev parent reply other threads:[~2014-01-17 12:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 14:02 Nicola
2014-01-17 12:15 ` Marco Patzer [this message]
2014-01-17 13:34 ` Hans Hagen
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=20140117121557.GA4495@homerow \
--to=lists@homerow.info \
--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).