From: Jon Turney <jon.turney@dronecode.org.uk>
To: Brian Inglis <Brian.Inglis@Shaw.ca>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: Suggested new Categories: Fonts and Backgrounds or Wallpapers
Date: Thu, 14 Sep 2023 12:32:05 +0100 [thread overview]
Message-ID: <4e0c4da8-c86f-cb61-0e34-c1176c4c4cb7@dronecode.org.uk> (raw)
In-Reply-To: <c41d1547-5776-d84b-be5a-8a2d5bd28666@Shaw.ca>
On 12/09/2023 23:44, Brian Inglis via Cygwin-apps wrote:
> Hi folks,
>
> Often noticed that we have no Font or Background/Wallpaper categories,
> or whatever the kids are calling the latter nowadays! ;^>
Yeah, the fact we don't have 'Fonts' seems a little odd.
The category list is allegedly modelled after Debian package "sections",
which does include 'Fonts', so I guess adding that makes sense.
> The only uses of wallpaper are in KDE: kde-wallpapers and
> plasma-workspace-wallpapers replacing the former, although Debian and
> Ubuntu also use that term, and Fedora uses both.
>
> Cygwin's Fedora backgrounds packages stop at
> f30-backgrounds{,-animated,-extras}.
>
> Should we consider adding one or both of these new categories rather
> than continuing to specify one of:
>
> CATEGORY="Publishing" TeX
> CATEGORY="X11" most others
> CATEGORY="Graphics"
> CATEGORY="Graphics X11"
> CATEGORY="Graphics Text X11"
>
Hmm... Not sure. Also having the X11 category for fonts which can be
used by X applications (as opposed to other formats which presumably can
only be used with other tools like TeX) might be a good idea.
next prev parent reply other threads:[~2023-09-14 11:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 21:21 ITP: last-resort-font Brian Inglis
2023-09-12 22:44 ` Suggested new Categories: Fonts and Backgrounds or Wallpapers Brian Inglis
2023-09-14 11:32 ` Jon Turney [this message]
2023-09-14 14:31 ` Jon Turney
2023-09-15 17:45 ` Brian Inglis
2023-09-13 4:46 ` ITP: last-resort-font Brian Inglis
2023-09-14 14:31 ` Jon Turney
2023-09-15 19:13 ` Brian Inglis
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=4e0c4da8-c86f-cb61-0e34-c1176c4c4cb7@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Brian.Inglis@Shaw.ca \
--cc=cygwin-apps@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).