view doc/mansupp/mansupp-240.html @ 24:a4899cdfc2d6 default tip

Obfuscate the regexps to strip off the IBM compiler's copyright banners. I don't want bots scanning github to think they're real copyright notices because that could cause real problems.
author David A. Holland
date Mon, 13 Jun 2022 00:40:23 -0400
parents 13d2b8934445
children
line wrap: on
line source

<html>
<head>
<title>AnaGram 2.40 Manual Supplement</title>
</head>
<body text="#000000" link="#0000ff" vlink="#551a8b" alink="#ff0000" 
      bgcolor="#ffffff">

<h1 align="center">AnaGram 2.40</h1>

<h1 align="center">Supplement to User's Guide</h1>
<p>
AnaGram 2.40 is the first open-source release of AnaGram. It should be
considered a beta version: it should be perfectly fine to use, but
before adopting it permanently in place of 2.01, double-check that
everything is behaving as expected. Please file a bug report on any
discrepancies you encounter.
</p>

<p>
The intent going forward is to maintain AnaGram 2.40 with bug fixes
(builds will be numbered 2.40.01, 2.40.02, etc.) with the next
milestone being a fully stable, usable version numbered 2.50. Once
that is ready, a new GUI is required, because the current GUI is both
unportable and depends on an orphaned legacy toolkit; the first
version with a new GUI is expected to be numbered 3.00.
</p>

<h2>Unix Support</h2>
<p>
The command-line version of AnaGram (<tt>agcl</tt>) can be compiled
for, and will run on, most Unix and Unix-like systems. There is, for
the moment, no GUI support on Unix.
</p>

<p>
Note that while the Windows version of AnaGram will <em>run</em> in
Wine, it does not, for the time being at least, run very well. Most
seriously, problems with font handling cause all fonts to be the same,
which makes the marked tokens (that is, where you are) in the File
Trace and Grammar Trace become indistinguishable from the other
tokens. This makes the user interface nearly impossible to use. For
further detail, look at the file <tt>doc/admin/wine-issues.txt</tt> in
the AnaGram source distribution.
</p>

<h2>Tidier Install</h2>
<p>
The separate <tt>AnaGram.cgb</tt> and <tt>AnaGram.hlp</tt> files that
appeared in earlier releases of AnaGram are now compiled directly into
the executable.
</p>

<h2>Manual Re-Typeset</h2>
<p>
The manual has been translated from WordPerfect to LaTeX and re-set.
As of this writing, the manual's index is in disarray. We hope to have
this cleaned up in time for the projected 2.50 release.
</p>

<h2>Internal Cleanup</h2>
<p>
The source tree has been rearranged and tidied up for public release;
so has much of the source code itself. The entire build system and all
makefiles have been replaced.
</p>

<h2>Bug Fixes</h2>
<p>
A few bugs have been fixed.
See <A HREF=whatsnew.html>whatsnew.html</A> for details.
</p>

<h2>Internal Errors</h2>
<p>
The reporting of internal errors has been changed to be more
consistent with an open-source program; internal errors are now
readable messages with a source file and line number rather than magic
code numbers.
</p>

<h2>Trial Copies</h2>
<p>
All the logic for dealing with trial copies, serial numbers,
registration, and so forth has been removed.
</p>

<h2>Character-Set Limitation</h2>
<p>
It has been ascertained that AnaGram can currently only handle
character sets up to 16 bits wide; thus, the larger Unicode sets will
not work. In at least some cases, attempts to use wider character sets
will cause assertion failures in AnaGram itself. This is a bug and we
hope to get it sorted out in time for the 2.50 release.
</p>

</body>
</html>