From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: X Server 1.19.6-2 , xset does not add ghostscript fonts for xfig
Date: Tue, 20 Mar 2018 19:18:00 -0000 [thread overview]
Message-ID: <87d0zyipi7.fsf@Rainer.invalid> (raw)
In-Reply-To: <4e10fb29-6905-2214-67f3-bf35f3021337@cornell.edu> (Ken Brown's message of "Tue, 20 Mar 2018 10:18:45 -0400")
Ken Brown writes:
>> The 35 core postscript fonts are now in
>> /usr/share/fonts/urw-base35. But I'm not sure what you have to do to
>> make xfig find them.
>
> I just looked at Fedora's xfig packaging
> (https://src.fedoraproject.org/cgit/rpms/xfig.git), and the two most
> recent commits fix issues with the urw fonts. So maybe Cygwin's xfig
> needs something similar.
I might do that although these patches look extra hairy. But, reading
the commit messages I start to wonder if it's not the URW font package
that needs fixing (there might still be a need to patch some things in
xfig)? I'd not want to fl<y in some patches that don't actually fix the
problem, but just shove it further out.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-03-20 18:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 1:22 Andrew P Paplinski via cygwin
2018-03-20 13:07 ` Ken Brown
2018-03-20 18:14 ` Ken Brown
2018-03-20 19:18 ` Achim Gratz [this message]
2018-03-21 22:07 ` Ken Brown
2018-03-22 17:29 ` Achim Gratz
2018-04-16 20:45 ` Ken Brown
2018-04-16 22:51 ` Andrew P Paplinski via cygwin
2018-04-17 16:07 ` Achim Gratz
2018-04-17 17:19 ` Achim Gratz
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=87d0zyipi7.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@cygwin.com \
/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).