* TO BE DONE SHORTLY BEFORE RELEASE
+** Either update, test, and support the old w32 build method, or remove it.
+
** Manuals
+Check for node names using problematic characters:
+ find doc -name '*.texi' -exec grep '^@node[^,]*[:.()]' {} +
+Sadly makeinfo does not warn about such characters.
+
Check cross-references between the manuals (eg from emacs to elisp)
are correct. You can use something like the following in the info
directory in the Emacs build tree:
emacs -Q --eval "(progn (require 'info) (setq Info-directory-list '(\".\")))" \
-f info-xref-check-all
+Setting Info-directory-list avoids having system info pages confuse
+things. References to external manuals will be flagged as
+uncheckable. You should still check these, and also that each
+external manual has an appropriate redirect in the file manual/.htaccess
+in the web pages repository. E.g.:
+Redirect /software/emacs/manual/html_mono/automake.html /software/automake/manual/automake.html
+Redirect /software/emacs/manual/html_node/automake/ /software/automake/manual/html_node/
+
+Another tool you can use to check links is gnu.org's linc.py:
+http://www.gnu.org/server/source/
+
+You run this something like:
+
+cd /path/to/cvs/emacs-www
+linc.py -o /path/to/output-dir --url http://www.gnu.org/software/emacs/ .
+
+Be warned that it is really, really slow (as in, can take ~ a full day
+to check the manual/ directory). It is probably best to run it on a
+single directory at a time from eg manual/html_node. It is very
+inefficient, but may reveal a few things that info-xref does not.
+
+
make emacs.dvi, elisp.dvi, and deal with any errors (undefined
references etc) in the output. Break any overfull lines.
Underfull hboxes are not serious, but it can be nice to get rid of
things to avoid these. (AFAIK, there is no way to find these except
paging through the whole manual.) This should be the very last thing
you do, since any change can alter the layout.
+(Actually, there is probably little point in trying to do this.
+It's only really relevant if printed versions of the manuals are going
+to be published. End-users are not likely to print out all 1000+
+pages of the manuals, and even if they do, the resulting page breaks
+depend on what paper and font size they use. This also means that if
+you _are_ going to do this, it should be done with the paper and font
+size that the GNU Press are going to use when they print the manuals.
+I think this is different to what you get if you just use eg `make
+emacs.pdf' (e.g., enable "smallbook").
** Check the keybindings in the refcards are correct, and add any new ones.
-Regenerate the pdf versions in etc/refcards/.
What paper size are the English versions supposed to be on?
On Debian testing, the packages texlive-lang-czechslovak and
texlive-lang-polish will let you generate the cs-* and sk-* pdfs.
+(You may need texlive-lang-cyrillic, texlive-lang-german for others.)
The Makefile rules did not work for me, I had to use something like:
csplain -output-format=pdf cs-refcard
ru Alex Ott
sk Miroslav Vaško
+** For a major release, add a "New in Emacs XX" section to faq.texi.
+
** Remove temporary +++/--- lines in NEWS.
** Try to reorder NEWS: most important things first, related items together.
** Consider bumping customize-changed-options-previous-release.
+** cusver-check from admin.el can help find new defcustoms missing
+:version tags.
+
* BUGS
** Check for modes which bind M-s that conflicts with a new global binding M-s
----------------------------------
TUTORIAL cyd
TUTORIAL.bg ogi
-TUTORIAL.cn
+TUTORIAL.cn xfq
TUTORIAL.cs
TUTORIAL.de wl
TUTORIAL.eo
TUTORIAL.fr
TUTORIAL.he eliz
TUTORIAL.it
-TUTORIAL.ja
+TUTORIAL.ja
TUTORIAL.ko
TUTORIAL.nl Pieter Schoenmakers
TUTORIAL.pl
fixit.texi cyd
fortran-xtra.texi rgm
frames.texi cyd
-glossary.texi
+glossary.texi rgm
help.texi cyd
indent.texi cyd
killing.texi cyd
misc.texi cyd
modes.texi cyd
msdog.texi rgm (can't actually test any of it though)
- It was not obvious to me that the following is true (it could well be though):
-
- Emacs on Windows automatically determines your default printer and
- sets the variable `printer-name' to that printer's name.
-
msdog-xtra.texi rgm (can't actually test any of it though)
-mule.texi
+mule.texi rgm (not 100% sure about "Fontsets")
m-x.texi cyd
package.texi cyd
picture-xtra.texi rgm
** Check the Lisp manual.
abbrevs.texi rgm
-advice.texi cyd
-anti.texi
-back.texi
+anti.texi rgm
+back.texi rgm
backups.texi cyd
buffers.texi cyd
commands.texi cyd
control.texi cyd
customize.texi cyd
debugging.texi cyd
-display.texi
-edebug.texi
+display.texi cyd
+edebug.texi rgm
elisp.texi
errors.texi rgm
eval.texi cyd
help.texi cyd
hooks.texi rgm
index.texi
-internals.texi rgm (I don't know much about this, so it would be
- good if someone else could at least look at the FIXME? comments.)
+internals.texi rgm cyd
intro.texi cyd
keymaps.texi cyd
lists.texi cyd
macros.texi cyd
maps.texi rgm
markers.texi rgm
-minibuf.texi
+minibuf.texi rgm
modes.texi cyd
nonascii.texi cyd
numbers.texi cyd
objects.texi cyd
-os.texi
+os.texi cyd
package.texi rgm
positions.texi cyd
-processes.texi
-searching.texi
+processes.texi rgm
+searching.texi rgm
sequences.texi cyd
streams.texi cyd
strings.texi cyd
text.texi cyd
tips.texi rgm
variables.texi cyd
-windows.texi
+windows.texi rgm (skimmed)
\f
Local variables:
HCoop / bpt / emacs.git / blobdiff