bug#14993: [PATCH] Update information about fonts

bug#14993: [PATCH] Update information about fonts

[Xue Fuqiao]

[-- Attachment #1: Type: text/plain, Size: 413 bytes --]

tags patch

GNU Intlfonts are pretty old bitmapped fonts.  They cannot be used with
GNU Emacs's font shaping capabilities.  The GNU FreeFont exist and offer
support for many scripts and languages, so I made a patch.  (For
downloading fonts and installing them, there’s nothing Emacs-specific,
so I removed them from the Emacs FAQ.)


-- 
Best regards, Xue Fuqiao.
http://www.gnu.org/software/emacs/

[-- Attachment #2: fonts.patch --]
[-- Type: application/octet-stream, Size: 6703 bytes --]

=== modified file 'INSTALL'
--- INSTALL	2013-07-29 11:35:16 +0000
+++ INSTALL	2013-07-31 09:03:44 +0000
@@ -134,23 +134,15 @@
 Note that Emacs cannot support complex scripts on a TTY, unless the
 terminal includes such a support.
 
-* intlfonts-VERSION.tar.gz
-
-The intlfonts distribution contains X11 fonts in various encodings
-that Emacs can use to display international characters.  If you see a
-non-ASCII character appear as a hollow box, that means you don't have
-a font for it.  You might find one in the intlfonts distribution.  If
-you do have a font for a non-ASCII character, but some characters
-don't look right, or appear improperly aligned, a font from the
-intlfonts distribution might look better.
-
-The fonts in the intlfonts distribution are also used by the ps-print
-package for printing international characters.  The file
-lisp/ps-mule.el defines the *.bdf font files required for printing
-each character set.
-
-The intlfonts distribution contains its own installation instructions,
-in the intlfonts/README file.
+* GNU FreeFont
+
+The GNU FreeFont distribution is a free family of scalable outline
+fonts, suitable for general use on computers and for desktop
+publishing.  It is Unicode-encoded for compatibility with all modern
+operating systems.  If you see a non-ASCII character appear as a
+hollow box, that means you don't have a font for it.
+
+The fonts are ready to use, avalable in TrueType and OpenType formats.
 
 * Image support libraries
 

=== modified file 'doc/misc/faq.texi'
--- doc/misc/faq.texi	2013-07-25 07:10:56 +0000
+++ doc/misc/faq.texi	2013-07-31 09:03:44 +0000
@@ -4018,7 +4018,6 @@
 * Emacs does not display 8-bit characters::
 * Inputting eight-bit characters::
 * Right-to-left alphabets::
-* How to add fonts::
 @end menu
 
 @node Emacs does not display 8-bit characters
@@ -4060,126 +4059,6 @@
 Arabic, Farsi, and Hebrew, since version 24.1.
 @xref{New in Emacs 24, bidirectional display}.
 
-
-@node How to add fonts
-@section How do I add fonts for use with Emacs?
-@cindex add fonts for use with Emacs
-@cindex intlfonts
-
-First, download and install the BDF font files and any auxiliary
-packages they need.  The GNU Intlfonts distribution can be found on
-@uref{http://directory.fsf.org/localization/intlfonts.html, the GNU
-Software Directory Web site}.
-
-Next, if you are on X Window system, issue the following two commands
-from the shell's prompt:
-
-@example
-  xset +fp /usr/local/share/emacs/fonts
-  xset fp rehash
-@end example
-
-@noindent
-(Modify the first command if you installed the fonts in a directory
-that is not @file{/usr/local/share/emacs/fonts}.)  You also need to
-arrange for these two commands to run whenever you log in, e.g., by
-adding them to your window-system startup file, such as
-@file{~/.xsessionrc} or @file{~/.gnomerc}.
-
-Now, add the following line to your @file{~/.emacs} init file:
-
-@lisp
-  (add-to-list 'bdf-directory-list "/usr/share/emacs/fonts/bdf")
-@end lisp
-
-@noindent
-(Again, modify the file name if you installed the fonts elsewhere.)
-
-Finally, if you wish to use the installed fonts with @code{ps-print},
-add the following line to your @file{~/.emacs}:
-
-@lisp
-  (setq ps-multibyte-buffer 'bdf-font-except-latin)
-@end lisp
-
-A few additional steps are necessary for MS-Windows; they are listed
-below.
-
-First, make sure @emph{all} the directories with BDF font files are
-mentioned in @code{bdf-directory-list}.  On Unix and GNU/Linux
-systems, one normally runs @kbd{make install} to install the BDF fonts
-in the same directory.  By contrast, Windows users typically don't run
-the Intlfonts installation command, but unpack the distribution in
-some directory, which leaves the BDF fonts in its subdirectories.  For
-example, assume that you unpacked Intlfonts in @file{C:/Intlfonts};
-then you should set @code{bdf-directory-list} as follows:
-
-@lisp
-  (setq bdf-directory-list
-    '("C:/Intlfonts/Asian"
-      "C:/Intlfonts/Chinese" "C:/Intlfonts/Chinese.X"
-      "C:/Intlfonts/Chinese.BIG" "C:/Intlfonts/Ethiopic"
-      "C:/Intlfonts/European" "C:/Intlfonts/European.BIG"
-      "C:/Intlfonts/Japanese" "C:/Intlfonts/Japanese.X"
-      "C:/Intlfonts/Japanese.BIG" "C:/Intlfonts/Korean.X"
-      "C:/Intlfonts/Misc"))
-@end lisp
-
-@cindex @code{w32-bdf-filename-alist}
-@cindex @code{w32-find-bdf-fonts}
-Next, you need to set up the variable @code{w32-bdf-filename-alist} to
-an alist of the BDF fonts and their corresponding file names.
-Assuming you have set @code{bdf-directory-list} to name all the
-directories with the BDF font files, the following Lisp snippet will
-set up @code{w32-bdf-filename-alist}:
-
-@lisp
-  (setq w32-bdf-filename-alist
-     (w32-find-bdf-fonts bdf-directory-list))
-@end lisp
-
-Now, create fontsets for the BDF fonts:
-
-@smallexample
-  (create-fontset-from-fontset-spec
-   "-*-fixed-medium-r-normal-*-16-*-*-*-c-*-fontset-bdf,
-   japanese-jisx0208:-*-*-medium-r-normal-*-16-*-*-*-c-*-jisx0208.1983-*,
-   katakana-jisx0201:-*-*-medium-r-normal-*-16-*-*-*-c-*-jisx0201*-*,
-   latin-jisx0201:-*-*-medium-r-normal-*-16-*-*-*-c-*-jisx0201*-*,
-   japanese-jisx0208-1978:-*-*-medium-r-normal-*-16-*-*-*-c-*-jisx0208.1978-*,
-   thai-tis620:-misc-fixed-medium-r-normal--16-160-72-72-m-80-tis620.2529-1,
-   lao:-misc-fixed-medium-r-normal--16-160-72-72-m-80-MuleLao-1,
-   tibetan-1-column:-TibMdXA-fixed-medium-r-normal--16-160-72-72-m-80-MuleTibetan-1,
-   ethiopic:-Admas-Ethiomx16f-Medium-R-Normal--16-150-100-100-M-160-Ethiopic-Unicode,
-   tibetan:-TibMdXA-fixed-medium-r-normal--16-160-72-72-m-160-MuleTibetan-0")
-@end smallexample
-
-Many of the international bdf fonts from Intlfonts are type 0, and
-therefore need to be added to font-encoding-alist:
-
-@lisp
-  (setq font-encoding-alist
-        (append '(("MuleTibetan-0" (tibetan . 0))
-                  ("GB2312"        (chinese-gb2312 . 0))
-                  ("JISX0208"      (japanese-jisx0208 . 0))
-                  ("JISX0212"      (japanese-jisx0212 . 0))
-                  ("VISCII"        (vietnamese-viscii-lower . 0))
-                  ("KSC5601"       (korean-ksc5601 . 0))
-                  ("MuleArabic-0"  (arabic-digit . 0))
-                  ("MuleArabic-1"  (arabic-1-column . 0))
-                  ("MuleArabic-2"  (arabic-2-column . 0)))
-                font-encoding-alist))
-@end lisp
-
-You can now use the Emacs font menu to select the @samp{bdf: 16-dot medium}
-fontset, or you can select it by setting the default font in your
-@file{~/.emacs}:
-
-@lisp
-  (set-default-font "fontset-bdf")
-@end lisp
-
-
 @c ------------------------------------------------------------
 @node Mail and news
 @chapter Mail and news

bug#14993: [PATCH] Update information about fonts

[Xue Fuqiao]

[-- Attachment #1: Type: text/plain, Size: 100 bytes --]

A new patch with further changes.

-- 
Best regards, Xue Fuqiao.
http://www.gnu.org/software/emacs/

[-- Attachment #2: fonts.patch --]
[-- Type: application/octet-stream, Size: 9765 bytes --]

=== modified file 'INSTALL'
--- INSTALL	2013-07-29 11:35:16 +0000
+++ INSTALL	2013-07-31 09:03:44 +0000
@@ -134,23 +134,15 @@
 Note that Emacs cannot support complex scripts on a TTY, unless the
 terminal includes such a support.
 
-* intlfonts-VERSION.tar.gz
-
-The intlfonts distribution contains X11 fonts in various encodings
-that Emacs can use to display international characters.  If you see a
-non-ASCII character appear as a hollow box, that means you don't have
-a font for it.  You might find one in the intlfonts distribution.  If
-you do have a font for a non-ASCII character, but some characters
-don't look right, or appear improperly aligned, a font from the
-intlfonts distribution might look better.
-
-The fonts in the intlfonts distribution are also used by the ps-print
-package for printing international characters.  The file
-lisp/ps-mule.el defines the *.bdf font files required for printing
-each character set.
-
-The intlfonts distribution contains its own installation instructions,
-in the intlfonts/README file.
+* GNU FreeFont
+
+The GNU FreeFont distribution is a free family of scalable outline
+fonts, suitable for general use on computers and for desktop
+publishing.  It is Unicode-encoded for compatibility with all modern
+operating systems.  If you see a non-ASCII character appear as a
+hollow box, that means you don't have a font for it.
+
+The fonts are ready to use, avalable in TrueType and OpenType formats.
 
 * Image support libraries
 

=== modified file 'doc/emacs/misc.texi'
--- doc/emacs/misc.texi	2013-01-02 16:13:04 +0000
+++ doc/emacs/misc.texi	2013-07-31 13:51:42 +0000
@@ -1853,33 +1853,6 @@
 @code{Times}.  The variable @code{ps-font-size} specifies the size of
 the font for ordinary text.  It defaults to 8.5 points.
 
-@vindex ps-multibyte-buffer
-@cindex Intlfonts for PostScript printing
-@cindex fonts for PostScript printing
-  Emacs supports more scripts and characters than a typical PostScript
-printer.  Thus, some of the characters in your buffer might not be
-printable using the fonts built into your printer.  You can augment
-the fonts supplied with the printer with those from the GNU Intlfonts
-package, or you can instruct Emacs to use Intlfonts exclusively.  The
-variable @code{ps-multibyte-buffer} controls this: the default value,
-@code{nil}, is appropriate for printing @acronym{ASCII} and Latin-1
-characters; a value of @code{non-latin-printer} is for printers which
-have the fonts for @acronym{ASCII}, Latin-1, Japanese, and Korean
-characters built into them.  A value of @code{bdf-font} arranges for
-the BDF fonts from the Intlfonts package to be used for @emph{all}
-characters.  Finally, a value of @code{bdf-font-except-latin}
-instructs the printer to use built-in fonts for @acronym{ASCII} and Latin-1
-characters, and Intlfonts BDF fonts for the rest.
-
-@vindex bdf-directory-list
-  To be able to use the BDF fonts, Emacs needs to know where to find
-them.  The variable @code{bdf-directory-list} holds the list of
-directories where Emacs should look for the fonts; the default value
-includes a single directory @file{/usr/local/share/emacs/fonts/bdf}.
-
-  Many other customization variables for these commands are defined and
-described in the Lisp files @file{ps-print.el} and @file{ps-mule.el}.
-
 @node Printing Package
 @subsection Printing Package
 @cindex Printing package

=== modified file 'doc/emacs/mule.texi'
--- doc/emacs/mule.texi	2013-06-29 13:36:19 +0000
+++ doc/emacs/mule.texi	2013-07-31 13:51:42 +0000
@@ -1306,7 +1306,6 @@
 it specifies.
 
 @cindex fonts for various scripts
-@cindex Intlfonts package, installation
   Each fontset has a name, like a font.  However, while fonts are
 stored in the system and the available font names are defined by the
 system, fontsets are defined within Emacs itself.  Once you have
@@ -1317,13 +1316,7 @@
 fontset in use for them has no font for those characters.  In this
 case, or if the characters are shown, but not as well as you would
 like, you may need to install extra fonts.  Your operating system may
-have optional fonts that you can install; or you can install the GNU
-Intlfonts package, which includes fonts for most supported
-scripts.@footnote{If you run Emacs on X, you may need to inform the X
-server about the location of the newly installed fonts with commands
-such as:
-@c FIXME?  I feel like this may be out of date.
-@c E.g., the intlfonts tarfile is ~ 10 years old.
+have optional fonts that you can install.
 
 @example
  xset fp+ /usr/local/share/emacs/fonts

=== modified file 'doc/misc/faq.texi'
--- doc/misc/faq.texi	2013-07-25 07:10:56 +0000
+++ doc/misc/faq.texi	2013-07-31 09:03:44 +0000
@@ -4018,7 +4018,6 @@
 * Emacs does not display 8-bit characters::
 * Inputting eight-bit characters::
 * Right-to-left alphabets::
-* How to add fonts::
 @end menu
 
 @node Emacs does not display 8-bit characters
@@ -4060,126 +4059,6 @@
 Arabic, Farsi, and Hebrew, since version 24.1.
 @xref{New in Emacs 24, bidirectional display}.
 
-
-@node How to add fonts
-@section How do I add fonts for use with Emacs?
-@cindex add fonts for use with Emacs
-@cindex intlfonts
-
-First, download and install the BDF font files and any auxiliary
-packages they need.  The GNU Intlfonts distribution can be found on
-@uref{http://directory.fsf.org/localization/intlfonts.html, the GNU
-Software Directory Web site}.
-
-Next, if you are on X Window system, issue the following two commands
-from the shell's prompt:
-
-@example
-  xset +fp /usr/local/share/emacs/fonts
-  xset fp rehash
-@end example
-
-@noindent
-(Modify the first command if you installed the fonts in a directory
-that is not @file{/usr/local/share/emacs/fonts}.)  You also need to
-arrange for these two commands to run whenever you log in, e.g., by
-adding them to your window-system startup file, such as
-@file{~/.xsessionrc} or @file{~/.gnomerc}.
-
-Now, add the following line to your @file{~/.emacs} init file:
-
-@lisp
-  (add-to-list 'bdf-directory-list "/usr/share/emacs/fonts/bdf")
-@end lisp
-
-@noindent
-(Again, modify the file name if you installed the fonts elsewhere.)
-
-Finally, if you wish to use the installed fonts with @code{ps-print},
-add the following line to your @file{~/.emacs}:
-
-@lisp
-  (setq ps-multibyte-buffer 'bdf-font-except-latin)
-@end lisp
-
-A few additional steps are necessary for MS-Windows; they are listed
-below.
-
-First, make sure @emph{all} the directories with BDF font files are
-mentioned in @code{bdf-directory-list}.  On Unix and GNU/Linux
-systems, one normally runs @kbd{make install} to install the BDF fonts
-in the same directory.  By contrast, Windows users typically don't run
-the Intlfonts installation command, but unpack the distribution in
-some directory, which leaves the BDF fonts in its subdirectories.  For
-example, assume that you unpacked Intlfonts in @file{C:/Intlfonts};
-then you should set @code{bdf-directory-list} as follows:
-
-@lisp
-  (setq bdf-directory-list
-    '("C:/Intlfonts/Asian"
-      "C:/Intlfonts/Chinese" "C:/Intlfonts/Chinese.X"
-      "C:/Intlfonts/Chinese.BIG" "C:/Intlfonts/Ethiopic"
-      "C:/Intlfonts/European" "C:/Intlfonts/European.BIG"
-      "C:/Intlfonts/Japanese" "C:/Intlfonts/Japanese.X"
-      "C:/Intlfonts/Japanese.BIG" "C:/Intlfonts/Korean.X"
-      "C:/Intlfonts/Misc"))
-@end lisp
-
-@cindex @code{w32-bdf-filename-alist}
-@cindex @code{w32-find-bdf-fonts}
-Next, you need to set up the variable @code{w32-bdf-filename-alist} to
-an alist of the BDF fonts and their corresponding file names.
-Assuming you have set @code{bdf-directory-list} to name all the
-directories with the BDF font files, the following Lisp snippet will
-set up @code{w32-bdf-filename-alist}:
-
-@lisp
-  (setq w32-bdf-filename-alist
-     (w32-find-bdf-fonts bdf-directory-list))
-@end lisp
-
-Now, create fontsets for the BDF fonts:
-
-@smallexample
-  (create-fontset-from-fontset-spec
-   "-*-fixed-medium-r-normal-*-16-*-*-*-c-*-fontset-bdf,
-   japanese-jisx0208:-*-*-medium-r-normal-*-16-*-*-*-c-*-jisx0208.1983-*,
-   katakana-jisx0201:-*-*-medium-r-normal-*-16-*-*-*-c-*-jisx0201*-*,
-   latin-jisx0201:-*-*-medium-r-normal-*-16-*-*-*-c-*-jisx0201*-*,
-   japanese-jisx0208-1978:-*-*-medium-r-normal-*-16-*-*-*-c-*-jisx0208.1978-*,
-   thai-tis620:-misc-fixed-medium-r-normal--16-160-72-72-m-80-tis620.2529-1,
-   lao:-misc-fixed-medium-r-normal--16-160-72-72-m-80-MuleLao-1,
-   tibetan-1-column:-TibMdXA-fixed-medium-r-normal--16-160-72-72-m-80-MuleTibetan-1,
-   ethiopic:-Admas-Ethiomx16f-Medium-R-Normal--16-150-100-100-M-160-Ethiopic-Unicode,
-   tibetan:-TibMdXA-fixed-medium-r-normal--16-160-72-72-m-160-MuleTibetan-0")
-@end smallexample
-
-Many of the international bdf fonts from Intlfonts are type 0, and
-therefore need to be added to font-encoding-alist:
-
-@lisp
-  (setq font-encoding-alist
-        (append '(("MuleTibetan-0" (tibetan . 0))
-                  ("GB2312"        (chinese-gb2312 . 0))
-                  ("JISX0208"      (japanese-jisx0208 . 0))
-                  ("JISX0212"      (japanese-jisx0212 . 0))
-                  ("VISCII"        (vietnamese-viscii-lower . 0))
-                  ("KSC5601"       (korean-ksc5601 . 0))
-                  ("MuleArabic-0"  (arabic-digit . 0))
-                  ("MuleArabic-1"  (arabic-1-column . 0))
-                  ("MuleArabic-2"  (arabic-2-column . 0)))
-                font-encoding-alist))
-@end lisp
-
-You can now use the Emacs font menu to select the @samp{bdf: 16-dot medium}
-fontset, or you can select it by setting the default font in your
-@file{~/.emacs}:
-
-@lisp
-  (set-default-font "fontset-bdf")
-@end lisp
-
-
 @c ------------------------------------------------------------
 @node Mail and news
 @chapter Mail and news

bug#14993: [PATCH] Update information about fonts

[Wolfgang Jenkner]

On Wed, Jul 31 2013, Xue Fuqiao wrote:

> A new patch with further changes.

I don't think emacs has support for printing with .ttf or .otf fonts, so
some info about .bdf fonts (not everything is easily available as type1
font) is perhaps still needed.

Wolfgang

bug#14993: [PATCH] Update information about fonts

[Eli Zaretskii]

> Date: Wed, 31 Jul 2013 17:16:31 +0800
> From: Xue Fuqiao <xfq.free@gmail.com>
> 
> GNU Intlfonts are pretty old bitmapped fonts.  They cannot be used with
> GNU Emacs's font shaping capabilities.  The GNU FreeFont exist and offer
> support for many scripts and languages, so I made a patch.  (For
> downloading fonts and installing them, there’s nothing Emacs-specific,
> so I removed them from the Emacs FAQ.)

Thanks.  You forgot msdos/INSTALL, I think.

Btw, if we are deprecating Intlfonts, should we keep ps-bdf.el?  And
if we drop ps-bdf.el, can we add some ps-otf.el instead?  Perhaps
Handa-san could comment on this.

bug#14993: [PATCH] Update information about fonts

[Kenichi Handa]

In article <83k3k6wx44.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:

> Btw, if we are deprecating Intlfonts, should we keep ps-bdf.el?  And
> if we drop ps-bdf.el, can we add some ps-otf.el instead?  Perhaps
> Handa-san could comment on this.

I was working on ps-ttf.el several years ago, but couldn't
finish it because of lack of time, and that code didn't have
a facility of CTL (Complex Text Layouting).  Nowadays I
think we can utilize cairo to generate ps or pdf, but I'm
not sure I can find a time to work on it.

---
Kenichi Handa
handa@gnu.org

bug#14993: [PATCH] Update information about fonts

[Eli Zaretskii]

> From: Kenichi Handa <handa@gnu.org>
> Cc: xfq.free@gmail.com, 14993@debbugs.gnu.org
> Date: Fri, 02 Aug 2013 22:10:57 +0900
> 
> In article <83k3k6wx44.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Btw, if we are deprecating Intlfonts, should we keep ps-bdf.el?  And
> > if we drop ps-bdf.el, can we add some ps-otf.el instead?  Perhaps
> > Handa-san could comment on this.
> 
> I was working on ps-ttf.el several years ago, but couldn't
> finish it because of lack of time, and that code didn't have
> a facility of CTL (Complex Text Layouting).  Nowadays I
> think we can utilize cairo to generate ps or pdf, but I'm
> not sure I can find a time to work on it.

In that case, perhaps it's too soon to deprecate Intlfonts, since
there's no other way of printing non-ASCII characters with ps-print.

bug#14993: [PATCH] Update information about fonts

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Kenichi Handa <handa@gnu.org>
>> Cc: xfq.free@gmail.com, 14993@debbugs.gnu.org
>> Date: Fri, 02 Aug 2013 22:10:57 +0900
>> 
>> In article <83k3k6wx44.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > Btw, if we are deprecating Intlfonts, should we keep ps-bdf.el?  And
>> > if we drop ps-bdf.el, can we add some ps-otf.el instead?  Perhaps
>> > Handa-san could comment on this.
>> 
>> I was working on ps-ttf.el several years ago, but couldn't
>> finish it because of lack of time, and that code didn't have
>> a facility of CTL (Complex Text Layouting).  Nowadays I
>> think we can utilize cairo to generate ps or pdf, but I'm
>> not sure I can find a time to work on it.
>
> In that case, perhaps it's too soon to deprecate Intlfonts, since
> there's no other way of printing non-ASCII characters with ps-print.

Has anything changed in this area now?  (It's two years later...)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#14993: [PATCH] Update information about fonts

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Kenichi Handa <handa@gnu.org>,  14993@debbugs.gnu.org,  xfq.free@gmail.com
> Date: Wed, 24 Feb 2016 15:32:05 +1100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Kenichi Handa <handa@gnu.org>
> >> Cc: xfq.free@gmail.com, 14993@debbugs.gnu.org
> >> Date: Fri, 02 Aug 2013 22:10:57 +0900
> >> 
> >> In article <83k3k6wx44.fsf@gnu.org>, Eli Zaretskii <eliz@gnu.org> writes:
> >> 
> >> > Btw, if we are deprecating Intlfonts, should we keep ps-bdf.el?  And
> >> > if we drop ps-bdf.el, can we add some ps-otf.el instead?  Perhaps
> >> > Handa-san could comment on this.
> >> 
> >> I was working on ps-ttf.el several years ago, but couldn't
> >> finish it because of lack of time, and that code didn't have
> >> a facility of CTL (Complex Text Layouting).  Nowadays I
> >> think we can utilize cairo to generate ps or pdf, but I'm
> >> not sure I can find a time to work on it.
> >
> > In that case, perhaps it's too soon to deprecate Intlfonts, since
> > there's no other way of printing non-ASCII characters with ps-print.
> 
> Has anything changed in this area now?  (It's two years later...)

I don't think so.  We do have Cairo support, though.

bug#14993: [PATCH] Update information about fonts

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

>> Has anything changed in this area now?  (It's two years later...)
>
> I don't think so.  We do have Cairo support, though.

To recap: There's a patch to remove the mention of intlfonts, but
ps-print.el apparently relies on it.

And looking at the changes to ps-print.el over the last four years, I
guess this is still the case?

So to fix this, we'd have to use Cairo functions to generate a ps/pdf,
and then pension off ps-print.el?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#14993: [PATCH] Update information about fonts

[Robert Pluim]

>>>>> On Thu, 13 Aug 2020 13:20:26 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:

    Lars> Eli Zaretskii <eliz@gnu.org> writes:
    >>> Has anything changed in this area now?  (It's two years later...)
    >> 
    >> I don't think so.  We do have Cairo support, though.

    Lars> To recap: There's a patch to remove the mention of intlfonts, but
    Lars> ps-print.el apparently relies on it.

    Lars> And looking at the changes to ps-print.el over the last four years, I
    Lars> guess this is still the case?

    Lars> So to fix this, we'd have to use Cairo functions to generate a ps/pdf,
    Lars> and then pension off ps-print.el?

Has anyone tried 'x-export-frames' on a Cairo build with PDF support?

Robert

bug#14993: [PATCH] Update information about fonts

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: xfq.free@gmail.com,  handa@gnu.org,  14993@debbugs.gnu.org
> Date: Thu, 13 Aug 2020 13:20:26 +0200
> 
> So to fix this, we'd have to use Cairo functions to generate a ps/pdf,
> and then pension off ps-print.el?

Something like this, yes.

bug#14993: [PATCH] Update information about fonts

[Lars Ingebrigtsen]

Robert Pluim <rpluim@gmail.com> writes:

> Has anyone tried 'x-export-frames' on a Cairo build with PDF support?

Hey!  Nice!  Seems to work perfectly here -- it made a PDF that looks
exactly like what the frame looked like.

So we just need something like that that works on the entire buffer and
not just the displayed frame?

Uhm...  would a wrapper that just pops up a bunch of frames and then
calls that function (and then closes all the new frames) do the trick
here?  It's a bit hacky, but...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#14993: [PATCH] Update information about fonts

[Robert Pluim]

>>>>> On Fri, 14 Aug 2020 13:42:11 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:

    Lars> Robert Pluim <rpluim@gmail.com> writes:
    >> Has anyone tried 'x-export-frames' on a Cairo build with PDF support?

    Lars> Hey!  Nice!  Seems to work perfectly here -- it made a PDF that looks
    Lars> exactly like what the frame looked like.

    Lars> So we just need something like that that works on the entire buffer and
    Lars> not just the displayed frame?

    Lars> Uhm...  would a wrapper that just pops up a bunch of frames and then
    Lars> calls that function (and then closes all the new frames) do the trick
    Lars> here?  It's a bit hacky, but...

I guess you'd need to be a bit careful that successive frames didnʼt
overlap with previous ones (especially the last one).

Robert

bug#14993: [PATCH] Update information about fonts

[Lars Ingebrigtsen]

Robert Pluim <rpluim@gmail.com> writes:

> I guess you'd need to be a bit careful that successive frames didnʼt
> overlap with previous ones (especially the last one).

Yeah...  hm...  and with images that may overlap when "scrolling down".
Well, that's a problem in general: A frame may show half a line at the
bottom, for instance, and we don't really want that when printing the
buffer.

So it would take more than just wrapping that function to have a
workable solution...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#14993: [PATCH] Update information about fonts

[Robert Pluim]

>>>>> On Sat, 15 Aug 2020 12:25:23 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:

    Lars> Robert Pluim <rpluim@gmail.com> writes:
    >> I guess you'd need to be a bit careful that successive frames didnʼt
    >> overlap with previous ones (especially the last one).

    Lars> Yeah...  hm...  and with images that may overlap when "scrolling down".
    Lars> Well, that's a problem in general: A frame may show half a line at the
    Lars> bottom, for instance, and we don't really want that when printing the
    Lars> buffer.

binding frame-resize-pixelwise to nil I think solves the line issue,
not necessarily the image issue.

    Lars> So it would take more than just wrapping that function to have a
    Lars> workable solution...

Could you create a single frame that shows the entire buffer and use
that? Probably that would run into problems with window managers not
letting you create frames larger than the screen size.

Robert

bug#14993: [PATCH] Update information about fonts

[Lars Ingebrigtsen]

Robert Pluim <rpluim@gmail.com> writes:

> binding frame-resize-pixelwise to nil I think solves the line issue,
> not necessarily the image issue.

Ah, right.

>     Lars> So it would take more than just wrapping that function to have a
>     Lars> workable solution...
>
> Could you create a single frame that shows the entire buffer and use
> that? Probably that would run into problems with window managers not
> letting you create frames larger than the screen size.

Yeah, I think that'd be a problem.

And my pop-up-a-bunch-of-frames thing isn't really workable either,
really -- we want to fit the paper size, not the screen size, I think...

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#14993: [PATCH] Update information about fonts

[Lars Ingebrigtsen]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> And my pop-up-a-bunch-of-frames thing isn't really workable either,
> really -- we want to fit the paper size, not the screen size, I think...

Anyway, this means that the proposed patch isn't workable, and it
doesn't seem likely that there'll be further progress here, so I'm
closing this bug report.  If Emacs ever grows better printing support,
then something like the patch should be applied, though.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no