public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Andrew P Paplinski via cygwin" <cygwin@cygwin.com>
To: Ken Brown <kbrown@cornell.edu>, cygwin@cygwin.com
Subject: Re: X Server 1.19.6-2 , xset does not add ghostscript fonts for xfig
Date: Mon, 16 Apr 2018 22:51:00 -0000	[thread overview]
Message-ID: <4bece0bb-b415-8d10-06a1-8d4baf2bc911@monash.edu> (raw)
In-Reply-To: <d58371cb-6d59-1a14-178b-6f26c5b7fce7@cornell.edu>



On 17/04/2018 6:45 AM, Ken Brown wrote:
> On 3/22/2018 1:25 PM, Achim Gratz wrote:
>> Ken Brown writes:
>>> What a mess!
>>
>> Indeed.
>>
>>> 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.
>>
>> That works for me.  :-)
>
> Following Fedora 
> (https://src.fedoraproject.org/cgit/rpms/urw-base35-fonts.git/commit/?id=f18d6d5b26d2eae4d7730b0b1137b4b54909d9fa), 
> I've created and uploaded a new subpackage urw-base35-fonts-legacy 
> that contains old versions of the fonts.  These should work with xfig.
>
> The fonts are in /usr/share/X11/fonts/urw-fonts, with a symlink in 
> /etc/X11/fontpath.d/.
>
> I did some limited testing, and xfig seems to find the fonts.  (I 
> didn't call xset or do anything else special.)
>
> Achim, if I'm right, you don't have to do anything with xfig except to 
> add a dependency on urw-base35-fonts-legacy.
>
> But someone more familiar with xfig than I am should test this.
>
> Ken

Thanks, Ken

Magic, magic and xfig works.
I have downloaded the urw-base35-fonts-legacy  (and urw-base35-fonts)  
fonts.
They are, as you said, in
/usr/share/X11/fonts/urw-fonts, with a symlink in /etc/X11/fontpath.d/
and the xfig picked them up automatically.

Thanks, again.

Andrew

-- 
A/Prof. Andrew P Paplinski
http://users.monash.edu/~app


--
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

  reply	other threads:[~2018-04-16 22:51 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
2018-03-22 17:29         ` Achim Gratz
2018-04-16 20:45           ` Ken Brown
2018-04-16 22:51             ` Andrew P Paplinski via cygwin [this message]
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=4bece0bb-b415-8d10-06a1-8d4baf2bc911@monash.edu \
    --to=cygwin@cygwin.com \
    --cc=andrew.paplinski@monash.edu \
    --cc=kbrown@cornell.edu \
    /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).