From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] urw-base35-fonts 20170801-3
Date: Tue, 02 Jan 2018 13:48:00 -0000 [thread overview]
Message-ID: <74c6eb7d-5f6e-617a-ecaa-5f6507aa4d7f@cornell.edu> (raw)
In-Reply-To: <caa611ce-1649-7547-3257-bfe5aeba63a4@gmail.com>
On 1/1/2018 2:28 PM, Marco Atzeri wrote:
> On 15/11/2017 19:54, Ken Brown wrote:
>> The following package has been uploaded to the Cygwin distribution:
>>
>> * urw-base35-fonts-20170801-3
>>
>> This package contains the 35 fonts in the PostScript Level 2 Core Font
>> Set. These fonts are used by ghostscript and xpdf.
>>
>> This release removes a workaround for an xpdf problem that has now
>> been fixed properly.
>>
>> Ken Brown
>> Cygwin's urw-base35-fonts maintainer.
>>
>
> Hi Ken, Yaakov,
>
> The package htmldoc
> https://cygwin.com/packages/x86_64/htmldoc/htmldoc-1.8.28-3
>
> is expecting the old fonts to be available
> ..
> usr/share/htmldoc/fonts/Helvetica.afm ->
> /usr/share/ghostscript/fonts/n019003l.afm
> usr/share/htmldoc/fonts/Helvetica.pfb ->
> /usr/share/ghostscript/fonts/n019003l.pfb
> ..
> so currently is broken.
>
> While grace and libwmf have both a copy of the same fonts:
>
> usr/share/grace/fonts/type1/n019003l.afm
> usr/share/grace/fonts/type1/n019003l.pfb
> ..
> usr/share/grace/fonts/type1/n019003l.afm
> usr/share/grace/fonts/type1/n019003l.pfb
Hi Marco,
htmldoc and grace are both Yaakov's, so I'll let him decide how these
should be fixed. I can adapt to whatever he does. libwmf is orphaned,
but maybe it's harmless to leave it alone. If not, I'll adopt it.
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
prev parent reply other threads:[~2018-01-02 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 19:14 Ken Brown
2018-01-01 19:28 ` Marco Atzeri
2018-01-01 21:03 ` Brian Inglis
2018-01-02 13:48 ` Ken Brown [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=74c6eb7d-5f6e-617a-ecaa-5f6507aa4d7f@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).