summaryrefslogtreecommitdiffstats
path: root/usr.bin/file/Magdir/tex
diff options
context:
space:
mode:
Diffstat (limited to 'usr.bin/file/Magdir/tex')
-rw-r--r--usr.bin/file/Magdir/tex25
1 files changed, 25 insertions, 0 deletions
diff --git a/usr.bin/file/Magdir/tex b/usr.bin/file/Magdir/tex
new file mode 100644
index 0000000..734bedd
--- /dev/null
+++ b/usr.bin/file/Magdir/tex
@@ -0,0 +1,25 @@
+#
+# magic.tex:
+#
+# XXX - needs byte-endian stuff (big-endian and little-endian DVI?)
+#
+# From <conklin@talisman.kaleida.com>
+
+# Although we may know the offset of certain text fields in TeX DVI
+# and font files, we can't use them reliably because they are not
+# zero terminated. [but we do anyway, christos]
+0 string \367\002 TeX DVI file
+>16 string >\0 (%s)
+0 string \367\203 TeX generic font data
+0 string \367\131 TeX packed font data
+>4 string >\0 (%s)
+0 string \367\312 TeX virtual font data
+0 string This\ is\ TeX, TeX transcript text
+0 string This\ is\ METAFONT, METAFONT transcript text
+
+# There is no way to detect TeX Font Metric (*.tfm) files without
+# breaking them apart and reading the data. The following patterns
+# match most *.tfm files generated by METAFONT or afm2tfm.
+2 string \000\021 TeX font metric data
+2 string \000\022 TeX font metric data
+>34 string >\0 (%s)
OpenPOWER on IntegriCloud