From: Philip McGrath <philip@philipmcgrath.com>
To: 53131@debbugs.gnu.org
Cc: Philip McGrath <philip@philipmcgrath.com>
Subject: [bug#53131] [PATCH 4/4] gnu: font-fira-go: Note lack of corresponding source.
Date: Sat, 8 Jan 2022 18:47:18 -0500 [thread overview]
Message-ID: <20220108234718.150528-4-philip@philipmcgrath.com> (raw)
In-Reply-To: <20220108234718.150528-1-philip@philipmcgrath.com>
* gnu/packages/fonts.scm (font-fira-go)[description]: Note lack of
corresponding source.
---
gnu/packages/fonts.scm | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/fonts.scm b/gnu/packages/fonts.scm
index 41caa4d5ee..b37408f653 100644
--- a/gnu/packages/fonts.scm
+++ b/gnu/packages/fonts.scm
@@ -1136,7 +1136,13 @@ (define-public font-fira-go
(synopsis "Multilingual extension of the Fira Sans font family")
(description "FiraGO is a multilingual extension of the Fira Sans font
family. Based on the Fira Sans 4.3 glyph set, FiraGO adds support for the
-Arabic, Devanagari, Georgian, Hebrew and Thai scripts.")
+Arabic, Devanagari, Georgian, Hebrew and Thai scripts.
+
+Note that FiraGO does not include corresponding source.")
+ ;; See:
+ ;; - https://github.com/bBoxType/FiraGO/issues/42
+ ;; - https://github.com/bBoxType/FiraSans/issues/4#issuecomment-699882058
+ ;; For further discussion, see comments on font-fira-sans.
(license license:silofl1.1)))
(define-public font-fira-code
--
2.32.0
next prev parent reply other threads:[~2022-01-08 23:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 23:44 [bug#53131] [PATCH 0/4] Update Fira fonts Philip McGrath
2022-01-08 23:47 ` [bug#53131] [PATCH 1/4] gnu: font-fira-sans: Update to 4.203 Philip McGrath
2022-01-08 23:47 ` [bug#53131] [PATCH 2/4] gnu: font-fira-mono: Inherit from font-fira-sans Philip McGrath
2022-01-08 23:47 ` [bug#53131] [PATCH 3/4] gnu: font-fira-code: Update to 6.2 Philip McGrath
2022-01-08 23:47 ` Philip McGrath [this message]
2022-01-13 22:03 ` bug#53131: [PATCH 0/4] Update Fira fonts Ludovic Courtès
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=20220108234718.150528-4-philip@philipmcgrath.com \
--to=philip@philipmcgrath.com \
--cc=53131@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.