From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: New package: ttf2pt1-3.4.4
Date: Tue, 17 May 2022 04:13:51 +0200 [thread overview]
Message-ID: <20220517021351.1tq9y99UYYGbbx2z58qd-DVNJvjRxYpcif4cFXEXxqY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27970@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
There's a closed pull request on the void-packages repository
New package: ttf2pt1-3.4.4
https://github.com/void-linux/void-packages/pull/27970
Description:
tool to convert TTF fonts to Adobe PS1 fonts. Allows for TTF font usage by tools like Enscript.
It hasn't been updated since 2003 (and still uses CVS for version control :vomiting_face: ), but is written in standard ANSI C, so I don't anticipate any breakage in the future.
The MANPAGE patches are relatively critical, as they clean things up to match up with void filepath standards, and remove a bunch of outdated info related to void linux. They also convert the man pages into proper mdoc format, rather than raw nroff.
I wasn't sure where to put the two main scripts that are included with the tool. For now, I put them in `/usr/share/examples/ttf2pt1` along with most of the remainder of the included files in the package. If there is a better place to put them, please let me know, and I will update the pull request.
next prev parent reply other threads:[~2022-05-17 2:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 23:29 [PR PATCH] " sww1235
2021-01-16 23:41 ` [PR PATCH] [Updated] " sww1235
2021-01-16 23:42 ` sww1235
2021-01-16 23:45 ` [PR PATCH] [Updated] " sww1235
2022-05-02 2:16 ` github-actions
2022-05-17 2:13 ` github-actions [this message]
2022-06-02 2:29 ` sww1235
2022-06-02 2:29 ` sww1235
2023-11-22 4:09 ` sww1235
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=20220517021351.1tq9y99UYYGbbx2z58qd-DVNJvjRxYpcif4cFXEXxqY@z \
--to=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).