unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jean-Christophe Helary <brandelune@gmail.com>,
	Kenichi Handa <handa@gnu.org>
Cc: 35355@debbugs.gnu.org
Subject: bug#35355: 27.0.50; ps-print-buffer-with-faces does not print non-ascii
Date: Sun, 21 Apr 2019 12:26:45 +0300	[thread overview]
Message-ID: <83bm0zaeui.fsf@gnu.org> (raw)
In-Reply-To: <A9976D6C-BA71-419B-9259-B8DFD4E729D8@gmail.com> (message from Jean-Christophe Helary on Sun, 21 Apr 2019 18:02:38 +0900)

> From: Jean-Christophe Helary <brandelune@gmail.com>
> Date: Sun, 21 Apr 2019 18:02:38 +0900
> 
> 
> I tried to print a simple C buffer with some Japanese characters in commentsand the default printout was in b/w, but all the Japanese characters were printed out nicely.
> 
> Then, I tried the ps-print-buffer-with-faces command and the syntax highlighting worked fine but all the Japanese characters were replaced by ???.
> 
> Then, after reading the documentation a bit, I tried to
> (setq ps−multibyte−buffer ’non−latin−printer)
> 
> but now the Japanese characters are totally mojibaked:
> // $*$_$/$8$NFbMF0lMw
> 
> so I tried 'bfd-fonts and I got a weird message about having no font for
> ascii, and with 'bfd-fonts-except-latin, I'm back to ???.
> 
> I tried the same with an elisp file and the result was the same.
> 
> A minor issue is that the first line of the header for the ps file seems
> truncated. Only the path and the date are printed.

Thanks, I hope Handa-san (CC'ed) could comment on this.





  reply	other threads:[~2019-04-21  9:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-21  9:02 bug#35355: 27.0.50; ps-print-buffer-with-faces does not print non-ascii Jean-Christophe Helary
2019-04-21  9:26 ` Eli Zaretskii [this message]
2019-04-29  4:02   ` handa
2019-04-29 13:22     ` Jean-Christophe Helary
2019-04-29 15:08       ` Eli Zaretskii
2019-04-29 15:50         ` Jean-Christophe Helary
2019-05-01  9:29       ` handa

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=83bm0zaeui.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35355@debbugs.gnu.org \
    --cc=brandelune@gmail.com \
    --cc=handa@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).