From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Marco Patzer <lists@homerow.info>
Subject: Re: Bad names
Date: Fri, 8 Feb 2019 23:26:21 +0100 [thread overview]
Message-ID: <0d64eaae-8494-a291-837e-a6d1cc3bdf0c@xs4all.nl> (raw)
In-Reply-To: <20190208222212.70efc63f@homerow>
On 2/8/2019 10:22 PM, Marco Patzer wrote:
> What is a bad name for context? Does it have any consequences if badly named
> files are used? Just being curious.
Bad names are names that can result i a miss when looked up on a case
sensitive system. When you have a workflow where images come from e.g.
graphic designers don't be surprised to get names with inconsistent
casing, one of more spaces in a row, multiple suffixes (or wrong ones),
etc etc ... now when images are referred to e.g. from xml files that
also come from someplace it can get pretty hard to find where something
goes miss. So, here we always normalize (az09-).
In a tex tree files with the same name can lead to wrong lookups
depending on the order of configured paths. There context alway has had
case insensitive lookups.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-02-08 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 21:22 Marco Patzer
2019-02-08 22:26 ` Hans Hagen [this message]
2019-02-08 23:15 ` Alan Braslau
2019-02-09 19:47 ` Hans Hagen
2019-02-09 11:37 ` Marco Patzer
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=0d64eaae-8494-a291-837e-a6d1cc3bdf0c@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=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).