From: Philip McGrath <philip@philipmcgrath.com>
To: 56849@debbugs.gnu.org
Cc: Philip McGrath <philip@philipmcgrath.com>
Subject: [bug#56849] [PATCH 6/8] gnu: Add texlive-sourcesanspro.
Date: Sat, 30 Jul 2022 21:08:48 -0400 [thread overview]
Message-ID: <b140070a1e55ff380f082f32df799a43f6963797.1659229280.git.philip@philipmcgrath.com> (raw)
In-Reply-To: <cover.1659229280.git.philip@philipmcgrath.com>
* gnu/packages/tex.scm (texlive-sourcesanspro): New variable.
---
gnu/packages/tex.scm | 28 ++++++++++++++++++++++++++++
1 file changed, 28 insertions(+)
diff --git a/gnu/packages/tex.scm b/gnu/packages/tex.scm
index d3185f5256..1221726ccd 100644
--- a/gnu/packages/tex.scm
+++ b/gnu/packages/tex.scm
@@ -11231,3 +11231,31 @@ (define-public texlive-physics
typesetting equations in the languages of vector calculus and linear
algebra, using Dirac notation.")
(license license:lppl)))
+
+(define-public texlive-sourcesanspro
+ (package
+ (inherit (simple-texlive-package
+ "texlive-sourcesanspro"
+ '("/doc/latex/sourcesanspro/"
+ "/fonts/enc/dvips/sourcesanspro/"
+ "/fonts/map/dvips/sourcesanspro/"
+ "/fonts/opentype/adobe/sourcesanspro/"
+ ;; ^ It would be tempting to use our
+ ;; font-adobe-source-sans-pro for these, but the version in
+ ;; texlive could differ from our version: probably the
+ ;; difference would be small, but debugging would not be fun.
+ ;; If the files are really identical, Guix will hard-link them
+ ;; anyway.
+ "/fonts/tfm/adobe/sourcesanspro/"
+ "/fonts/type1/adobe/sourcesanspro/"
+ "/fonts/vf/adobe/sourcesanspro/"
+ "/tex/latex/sourcesanspro/")
+ (base32
+ "18z7ln8dyh0sp6v0vdvc6qqxnpg3h3ix0f5magjcjbpay54kl0i3")
+ #:trivial? #t))
+ (home-page "https://ctan.org/pkg/sourcesanspro")
+ (synopsis "Use Source Sans Pro with TeX(-alike) systems")
+ (description "This package provides the Source Sans Pro font family from
+Adobe in both Adobe Type 1 and OpenType formats, plus macros supporting the
+use of the fonts in LaTeX (Type 1) and XeLaTeX/LuaLaTeX (OTF).")
+ (license (list license:lppl1.3+ license:silofl1.1))))
--
2.32.0
next prev parent reply other threads:[~2022-07-31 1:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 1:06 [bug#56849] [PATCH 0/8] gnu: Add several TeX packages Philip McGrath
2022-07-31 1:08 ` [bug#56849] [PATCH 1/8] gnu: Add texlive-abstract Philip McGrath
2022-07-31 1:08 ` [bug#56849] [PATCH 2/8] gnu: Add texlive-breqn Philip McGrath
2022-07-31 1:08 ` [bug#56849] [PATCH 3/8] gnu: Add texlive-comment Philip McGrath
2022-07-31 1:08 ` [bug#56849] [PATCH 4/8] gnu: Add texlive-datatool Philip McGrath
2022-07-31 1:08 ` [bug#56849] [PATCH 5/8] gnu: Add texlive-physics Philip McGrath
2022-07-31 1:08 ` Philip McGrath [this message]
2022-07-31 1:08 ` [bug#56849] [PATCH 7/8] gnu: Add texlive-sourceserifpro Philip McGrath
2022-07-31 1:08 ` [bug#56849] [PATCH 8/8] gnu: Add texlive-sourcecodepro Philip McGrath
2022-08-05 12:47 ` bug#56849: [PATCH 0/8] gnu: Add several TeX packages 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b140070a1e55ff380f082f32df799a43f6963797.1659229280.git.philip@philipmcgrath.com \
--to=philip@philipmcgrath.com \
--cc=56849@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).