* doc/autoconf.texi: Document @$.

[bison.git] / NEWS

diff --git a/NEWS b/NEWS
index 6833d69fe7cdf39ed674c3d8adb579b09468e643..2a9937d19a902739563597434595a65f1283fc8b 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -1,7 +1,43 @@
 Bison News
 ----------
 
 Bison News
 ----------
 

-Change in version 1.26:
+Changes in version 1.28a:
+
+* Russian translation added.
+
+* NLS support updated; should hopefully be less troublesome.
+
+* Added the old Bison reference card.
+
+* Added `--locations' and `%locations'.
+
+* Added `-S' and `--skeleton'.
+
+* `%raw', `-r', `--raw' is disabled.
+
+* Special characters are escaped when output.  This solves the problems
+  of the #line lines with path names including backslashes.
+
+* New directives.
+  `%yacc', `%fixed_output_files', `%defines', `%no_parser', `%verbose', and
+  `%debug'.
+\f
+Changes in version 1.28:
+
+* Should compile better now with K&R compilers.
+
+* Added NLS.
+
+* Fixed a problem with escaping the double quote character.
+
+* There is now a FAQ.
+\f
+Changes in version 1.27:
+
+* The make rule which prevented bison.simple from being created on
+  some systems has been fixed.
+\f
+Changes in version 1.26:

 
 * Bison now uses automake.
 
 
 * Bison now uses automake.
 


@@ -18,11 +54,11 @@ Change in version 1.26:
 * Generated parsers should now work even on operating systems which do
   not provide alloca().
 \f
 * Generated parsers should now work even on operating systems which do
   not provide alloca().
 \f

-Change in version 1.25:
+Changes in version 1.25:

 
 * Errors in the input grammar are not fatal; Bison keeps reading
 the grammar file, and reports all the errors found in it.
 
 * Errors in the input grammar are not fatal; Bison keeps reading
 the grammar file, and reports all the errors found in it.

-               
+

 * Tokens can now be specified as multiple-character strings: for
 example, you could use "<=" for a token which looks like <=, instead
 of chosing a name like LESSEQ.
 * Tokens can now be specified as multiple-character strings: for
 example, you could use "<=" for a token which looks like <=, instead
 of chosing a name like LESSEQ.