[NTG-context] Bad names

Marco Patzer lists at homerow.info
Fri Feb 8 22:22:12 CET 2019


Hi!

I was wondering what context considers a “bad” file name and what consequences
that might have. From workflows-mkiv.pdf:

  “Bad names are reported and suitable action can be taken”

Indeed, every run context tells me how many files are badly named:

  mkiv lua stats  > graphics processing time: 0.021 seconds including tex, 14 processed images, 14 unique asked, 7 bad names

A small test:

\starttext
  \externalfigure [a]           %% good
  \externalfigure [a.png]       %% good
  \externalfigure [a.b.png]     %% good
  \externalfigure [a.1.png]     %% bad
  \externalfigure [a-1.png]     %% good
  \externalfigure [a-.1.png]    %% bad
  \externalfigure [a-b.1.png]   %% bad
  \externalfigure [a-1.b.png]   %% good
  \externalfigure [A]           %% good
  \externalfigure [A.B]         %% good
  \externalfigure [A.b]         %% bad
  \externalfigure [A.B.png]     %% bad
  \externalfigure [A.png]       %% bad
  \externalfigure [a.c-b.b.png] %% bad

  %% bad names are reported in red
  \usemodule [s-figures-names]
\stoptext

I note that “A.png” and “a.1.png” are bad file names and “a-1.b.png” and
“a-1.png” are good file names. What's the idea behind that logic? “A.png” and
“a.1.png” seem perfectly fine file names to me.

The files are included without issues, regardless of context's opinion about
the name.

What is a bad name for context? Does it have any consequences if badly named
files are used? Just being curious.

Marco


More information about the ntg-context mailing list