public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lemures Lemniscati <lemures.lemniscati@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] fontforge 20170731-1
Date: Sun, 05 Jul 2020 09:48:32 +0900	[thread overview]
Message-ID: <20200705094829.8A3F.50F79699@gmail.com> (raw)
In-Reply-To: <dd329acb-eb7c-ceb1-e2df-be704455c20d@gmail.com>

Date: Sat, 4 Jul 2020 07:34:51 +0200
From: Marco Atzeri

> On 04.07.2020 05:13, Lemures Lemniscati via Cygwin wrote:
> > Subject: [ANNOUNCEMENT] fontforge 20170731-1
> > Date: Mon, 19 Mar 2018 20:05:12 -0500
> > From: Yaakov Selkowitz
> >
> >> The following packages have been uploaded to the Cygwin distribution:
> >>
> >> * fontforge-20170731-1
> >> * libfontforge2-20170731-1
> >> * libfontforge-devel-20170731-1
> >> * python2-fontforge-20170731-1
> >>
> >> An outline font editor that lets you create your own postscript, truetype,
> >> opentype, cid-keyed, multi-master, cff, svg and bitmap (bdf, FON, NFNT)
> >> fonts, or edit existing ones. Also lets you convert one format to another.
> >>
> >> This is an update to the latest upstream release:
> >>
> >> https://github.com/fontforge/fontforge/releases
> >
> > Hi !
> >
> > Is there any plan to update fontforge?
> >
> > --
> > Lem
> 
> unfortunately no.
> The package is currently without an active maintainer
> 
> https://sourceware.org/pipermail/cygwin-apps/2020-March/039877.html
> 
> Are you eventually interested to adopt it ?

I'm interested but I cannot even build it...
It seems too much task for me...

Many packages are related, and according to release notes https://github.com/fontforge/fontforge/releases , there are many changes since the current cygwin version.
So I think adequately or more skilled persons should do...


And packaging woff2 https://github.com/google/woff2 seems necessary to prepare fontforge.


--
Lem

  reply	other threads:[~2020-07-05  0:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20  1:23 Yaakov Selkowitz
2020-07-04  3:13 ` Lemures Lemniscati
2020-07-04  5:34   ` Marco Atzeri
2020-07-05  0:48     ` Lemures Lemniscati [this message]
2020-09-26 10:15 ` [ANNOUNCEMENT] Updated: fontforge-20200314p70-1 (test) Lemures Lemniscati via Cygwin-announce
2020-11-30 12:36 ` [ANNOUNCEMENT] Updated: fontforge-20201107p8-1 (test) Lemures Lemniscati via Cygwin-announce

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=20200705094829.8A3F.50F79699@gmail.com \
    --to=lemures.lemniscati@gmail.com \
    --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).