summaryrefslogtreecommitdiff
path: root/Build/tests/largefile/README
diff options
context:
space:
mode:
Diffstat (limited to 'Build/tests/largefile/README')
-rw-r--r--Build/tests/largefile/README15
1 files changed, 9 insertions, 6 deletions
diff --git a/Build/tests/largefile/README b/Build/tests/largefile/README
index f62b2af52a3..f78c6b46e21 100644
--- a/Build/tests/largefile/README
+++ b/Build/tests/largefile/README
@@ -2,15 +2,19 @@ $Id$
Copyright (C) 2012 Peter Breitenlohner <tex-live@tug.org>
You may freely use, modify and/or distribute this file.
-Shell scripts and data to test large file support (LFS) for TeX-like
-engines, in particular pdfTeX. These tests consume a generous amount
-of disk space in the current directory, typically 4GB and more. Since they
-require a fair amount of time a progress report is displayed on the
-terminal, followed by a line starting with either 'PASS' or 'FAIL'.
+Shell scripts and data to test large file support (LFS) for dvips and
+TeX-like engines, in particular pdfTeX. These tests consume a generous
+amount of disk space in the current directory, typically 4GB and more.
+Since they require a fair amount of time a progress report is displayed on
+the terminal, followed by a line starting with either 'PASS' or 'FAIL'.
============
Run
+ PATH_TO_largeps.test PATH_TO_dvips
+to verify that dvips can create PS files with 2GB or more.
+
+Run
PATH_TO_largedvi.test PATH_TO_TEX_ENGINE
to verify that the TeX engine (TeX, pdfTeX, Aleph, etc.) detects when a DVI
file would be 2GB or more.
@@ -29,4 +33,3 @@ indicates the test(s) to perform:
jpeg-1, jpeg-2, png-1, png-2, jbig2-1, jbig2-2: just one test
jpeg, png, jbig2, pdf: two tests
all: all seven tests.
-