public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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: Tue, 20 Mar 2018 13:07:00 -0000	[thread overview]
Message-ID: <ea575a6b-50c7-3d3b-c48a-a0b618be33b6@cornell.edu> (raw)
In-Reply-To: <66756897-e6cf-9d20-dec5-de9e634defa4@monash.edu>

On 3/19/2018 9:02 PM, Andrew P Paplinski via cygwin wrote:
> Dear Cygwin X,
> 
> I am running X Server 1.19.6-2 built 2018-03-12
> 
> I have the following error:
> 
> $ xset fp+ /usr/share/ghostscript/fonts/
> xset:  bad font path element (#2), possible causes are:
>      Directory does not exist or has wrong permissions
>      Directory missing fonts.dir
>      Incorrect font server address or syntax
> 
> The font directory does exist:
> 
> app@MU00108269 /usr/share/ghostscript
> $ ls -l
> total 12
> drwxr-xr-x+ 1 app Domain Users 0 Mar 9 10:02 9.22
> drwxr-xr-x+ 1 app Domain Users 0 Mar 9 10:02 fonts
> 
> Also
> 
> $ xset q
>   Font Path:
>    catalogue:/etc/X11/fontpath.d,built-ins
> 
> Without  ghostscript fonts  xfig  does not get the proper fonts.

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.

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

  reply	other threads:[~2018-03-20  2:44 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 [this message]
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
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=ea575a6b-50c7-3d3b-c48a-a0b618be33b6@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).