From: Vinicius Provenzano <viniciusxp@gmail.com>
To: 55740@debbugs.gnu.org
Subject: bug#55740: 27.2; Emacs GNU FAQ 10.4 - Old Information
Date: Tue, 31 May 2022 13:06:58 +0200 [thread overview]
Message-ID: <CA+nNV8FV7YgQHiCGcx8OxPpMosATy0HvYQtLnxntzChx0W2Rag@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
Hi to all,
I've found information on the Emacs GNU FAQ, distributed with Emacs
28.1, that is not relevant anymore - 10.4 How to add fonts for use
with Emacs. Here is the url of the FAQ:
https://www.gnu.org/software/emacs/manual/html_node/efaq/How-to-add-fonts.html
On the FAQ there is a set of instructions on how to add fonts that refer to
bdf fonts.
Bdf fonts are not supported on Emacs since
version 23 on Windows, as per the etc/NEW file.
Reference: https://www.gnu.org/software/emacs/news/NEWS.23.1
** BDF fonts no longer supported on MS-Windows. The font backend was
completely rewritten for this release. The focus on Windows has been
getting acceptable performance and full unicode support, including
complex script shaping for native Windows fonts. A rewrite of the BDF
font support has not happened due to lack of time and developers. If
demand still exists for such a backend even with the improved
language support for native Windows fonts, future development in this
direction will most likely be based on the freetype library, giving
access to a wider range of font formats.
I am not sure if this is the correct way of reporting this kind of
issue, that is not a technical bug, but a documention on need of
update.
Thank you.
Vinicius
[-- Attachment #2: Type: text/html, Size: 5177 bytes --]
next reply other threads:[~2022-05-31 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 11:06 Vinicius Provenzano [this message]
2022-05-31 16:04 ` bug#55740: 27.2; Emacs GNU FAQ 10.4 - Old Information Eli Zaretskii
[not found] ` <CA+nNV8HzTKRqgDTbLrkZgOzO5fpb+t62ka1cPL708UCdWKctCA@mail.gmail.com>
2022-05-31 17:28 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+nNV8FV7YgQHiCGcx8OxPpMosATy0HvYQtLnxntzChx0W2Rag@mail.gmail.com \
--to=viniciusxp@gmail.com \
--cc=55740@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).