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
___________________________________________________________________________________
