view BUGS @ 103270:c4706100caab

(xfont_chars_supported, xfont_supported_scripts): New functions. (xfont_scripts_cache, xfont_scratch_props): New variables. (Qlatin, Vscalable_fonts_allowed): Extern it. (xfont_list_pattern): Argument changed. Callers changed. Check Vscalable_fonts_allowed. Check the support of a script. (xfont_list): Don't reject a font spec with :script property. (xfont_has_char): Fix setting of encoding. (syms_of_xfont): Staticpro and initialize xfont_scripts_cache and xfont_scratch_props.
author Kenichi Handa <handa@m17n.org>
date Thu, 21 May 2009 11:23:41 +0000
parents fb8bf24d2eb9
children ac52af4a044c
line wrap: on
line source

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,"

Please first check the file etc/PROBLEMS (e.g. with C-h C-p in Emacs) to
make sure it isn't a known issue.