view BUGS @ 26882:5b331ff3b477

Define encode-composition-rule and find-composition for Emacs 20.4 and the earlier versions. (ps-mule-init-external-library): Just require a feature for external libraries. (ps-mule-prologue): Postscript code modified for new composition. (ps-mule-find-wrappoint): New arg COMPOSITION. (ps-mule-plot-string): Delete code for composite characaters. (ps-mule-plot-composition): New funcion. (ps-mule-prepare-font-for-components): New function. (ps-mule-plot-components): New function. (ps-mule-composition-prologue-generated): Renamed from ps-mule-cmpchar-prologue-generated. (ps-mule-composition-prologue): New named from ps-mule-cmpchar-prologue. Modified for new composition. (ps-mule-plot-rule-cmpchar, ps-mule-plot-cmpchar, ps-mule-prepare-cmpchar-font): Deleted. (ps-mule-string-encoding): New arg NO-SETFONT. (ps-mule-bitmap-prologue): In Postscript code of BuildGlyphCommon, check Composing, not Cmpchar (ps-mule-initialize): Set ps-mule-composition-prologue-generated to nil. (ps-mule-begin-job): Check existence of new composition.

If you think you may have found a bug in GNU Emacs, please
read the Bugs section of the Emacs manual for advice on
(1) how to tell when to report a bug, and
(2) how to write a useful bug report and what information
it needs to have.

There are three ways to read the Bugs section.

(1) In a printed copy of the Emacs manual.
You can order one from the Free Software Foundation;
see the file etc/ORDERS.  But if you don't have a copy on
hand and you think you have found a bug, you shouldn't wait
to get a printed manual; you should read the section right away
as described below.

(2) With Info.  Start Emacs, do C-h i to enter Info,
then m Emacs RET to get to the Emacs manual, then m Bugs RET
to get to the section on bugs.  Or use standalone Info in
a like manner.  (Standalone Info is part of the Texinfo distribution,
not part of the Emacs distribution.)

(3) By hand.  Do
    cat info/emacs* | more "+/^File: emacs,  Node: Bugs,"