diff options
Diffstat (limited to 'doc/context/sources/general/manuals/workflows/workflows-resources.tex')
| -rw-r--r-- | doc/context/sources/general/manuals/workflows/workflows-resources.tex | 22 |
1 files changed, 13 insertions, 9 deletions
diff --git a/doc/context/sources/general/manuals/workflows/workflows-resources.tex b/doc/context/sources/general/manuals/workflows/workflows-resources.tex index 41de6dc35..323bf8209 100644 --- a/doc/context/sources/general/manuals/workflows/workflows-resources.tex +++ b/doc/context/sources/general/manuals/workflows/workflows-resources.tex @@ -6,10 +6,10 @@ \startchapter[title=Accessing resources] -One of the benefits of \TEX\ is that you can use it in automated workflows -where large quantities of data is involved. A document can consist of -several files and normally also includes images. Of course there are styles -involved too. At \PRAGMA\ normally put styles and fonts in: +One of the benefits of \TEX\ is that you can use it in automated workflows where +large quantities of data is involved. A document can consist of several files and +normally also includes images. Of course there are styles involved too. At +\PRAGMA\ normally put styles and fonts in: \starttyping /data/site/context/tex/texmf-project/tex/context/user/<project>/... @@ -37,11 +37,12 @@ The processing happens in: Putting styles (and resources like logos and common images) and fonts (if the project has specific ones not present in the distribution) in the \TEX\ tree makes sense because that is where such files are normally searched. Of course you -need to keep the distributions file database upto|-|date after adding files there. +need to keep the distributions file database upto|-|date after adding files +there. Processing has to happen isolated from other runs so there we use unique -locations. The services responsible for running also deal with regular cleanup -of these temporary files. +locations. The services responsible for running also deal with regular cleanup of +these temporary files. Resources are somewhat special. They can be stable, i.e.\ change seldom, but more often they are updated or extended periodically (or even daily). We're not @@ -55,7 +56,7 @@ resource tree. In the 100K case there is a deeper structure which is in itself predictable but because many authors are involved the references to these files are somewhat instable (and undefined). It is surprising to notice that publishers don't care about filenames (read: cannot control all the parties involved) which -means that we have inconsist use of mixed case in filenames, and spaces, +means that we have inconsistent use of mixed case in filenames, and spaces, underscores and dashes creeping in. Because typesetting for paper is always at the end of the pipeline (which nowadays is mostly driven by (limitations) of web products) we need to have a robust and flexible lookup mechanism. It's a side @@ -67,7 +68,7 @@ get it fixed. \footnote {From what we normally receive we often conclude that copy|-|editing and image production companies don't impose any discipline or probably simply lack the tools and methods to control this. Some of our workflows had checkers and fixers, so that when we got 5000 new resources while only a few -needed to be replaced we could filter the right ones. It was not uncommon to find +needed to be replaced we could filter the right ones. It was not uncommon to find duplicates for thousands of pictures: similar or older variants.} \starttyping @@ -151,6 +152,9 @@ When you add, remove or move files the tree, you need to remove the \type {dirlist.*} files in the root because these are used for locating files. A new file will be generated automatically. Don't forget this! +When content doesn't change an alternative discussed in in a later chapter can be +considered: hashed databases of files. + \stopchapter \stopcomponent |