From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: X Server 1.19.6-2 , xset does not add ghostscript fonts for xfig
Date: Wed, 21 Mar 2018 22:07:00 -0000 [thread overview]
Message-ID: <3160976e-19a9-4ac1-02fa-d511185240a7@cornell.edu> (raw)
In-Reply-To: <87d0zyipi7.fsf@Rainer.invalid>
On 3/20/2018 2:13 PM, Achim Gratz wrote:
> 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.
What a mess!
There's a comment just yesterday at
https://bugzilla.redhat.com/show_bug.cgi?id=1551219#c8
suggesting that there will be some Fedora changes in the urw font
package coming this week. So let's wait for the dust to settle, and
then I hope we can just copy whatever solution Fedora comes up with.
Ken
--
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-21 20:31 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
2018-03-21 22:07 ` Ken Brown [this message]
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=3160976e-19a9-4ac1-02fa-d511185240a7@cornell.edu \
--to=kbrown@cornell.edu \
--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).