summaryrefslogtreecommitdiff
path: root/systems/unix/tex-gpc/triplog/READMe
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
committerNorbert Preining <norbert@preining.info>2019-09-02 13:46:59 +0900
commite0c6872cf40896c7be36b11dcc744620f10adf1d (patch)
tree60335e10d2f4354b0674ec22d7b53f0f8abee672 /systems/unix/tex-gpc/triplog/READMe
Initial commit
Diffstat (limited to 'systems/unix/tex-gpc/triplog/READMe')
-rw-r--r--systems/unix/tex-gpc/triplog/READMe15
1 files changed, 15 insertions, 0 deletions
diff --git a/systems/unix/tex-gpc/triplog/READMe b/systems/unix/tex-gpc/triplog/READMe
new file mode 100644
index 0000000000..219f142dbc
--- /dev/null
+++ b/systems/unix/tex-gpc/triplog/READMe
@@ -0,0 +1,15 @@
+The TRIP test nicely shows the sin of TeX-GPC: It does not trim trailing
+spaces of input lines.
+This is shown in trip.log.diff, the "**" line of TeX-GPC's log file
+contains a space, whereas the original log file doesn't. Furthermore
+the statistics the high water marks of the buffer stack differ by
+one (113b not 114b) which is the trailing space.
+
+TeX-GPC needs more strings and string characters than TeX because it
+does not conserve string space.
+
+These are all differences shown by the TRIP test, so TeX-GPC is
+still pretty close to TeX.
+
+September 2008
+Wolfgang Helbig