perfbook.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Akira Yokosawa <akiyks@gmail.com>
Cc: perfbook@vger.kernel.org
Subject: Re: [PATCH -perfbook 1/2] Don't run fixfonts for pstricks figures
Date: Fri, 14 Jul 2023 08:15:07 -0700	[thread overview]
Message-ID: <45115b17-ba95-448f-bd58-a0a099a2d084@paulmck-laptop> (raw)
In-Reply-To: <f8a28118-e3e4-d3ef-faa6-6c874e5c463a@gmail.com>

On Fri, Jul 14, 2023 at 11:07:37PM +0900, Akira Yokosawa wrote:
> fixfonts scripts don't have any effect on EPS files generated
> from pstricks + dvips.
> 
> Font in the figures should be specified in the source .tex files.
> 
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>

Queued and pushed both, thank you!

							Thanx, Paul

> ---
>  Makefile | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/Makefile b/Makefile
> index bffdd2da1f4d..f25baf27d8ad 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -414,13 +414,11 @@ perfbook-a4.tex:
>  
>  # Rules related to perfbook_html are removed as of May, 2016
>  
> -$(EPSSOURCES_FROM_TEX): $(FIXANEPSFONTS) $(FIXFONTS)
>  $(EPSSOURCES_FROM_TEX): %.eps: %.tex
>  	@echo "$< --> $(suffix $@)"
>  	sh utilities/mpostcheck.sh
>  	@latex -output-directory=$(shell dirname $<) $< > /dev/null 2>&1
>  	@dvips -Pdownload35 -E $(patsubst %.tex,%.dvi,$<) -o $@ > /dev/null 2>&1
> -	@sh $(FIXANEPSFONTS) $@
>  
>  $(EPSSOURCES_FROM_DOT): $(FIXANEPSFONTS) $(FIXFONTS)
>  $(EPSSOURCES_FROM_DOT): %.eps: %.dot
> 
> base-commit: b48ccb045d17f6d551ff210c74118f1769f66c63
> -- 
> 2.25.1
> 

      parent reply	other threads:[~2023-07-14 15:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 14:07 [PATCH -perfbook 1/2] Don't run fixfonts for pstricks figures Akira Yokosawa
2023-07-14 14:09 ` [PATCH -perfbook 2/2] SMPdesign: Specify sans-serif font in " Akira Yokosawa
2023-07-14 15:15 ` Paul E. McKenney [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45115b17-ba95-448f-bd58-a0a099a2d084@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=akiyks@gmail.com \
    --cc=perfbook@vger.kernel.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.
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).