From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Christoph Heiss <c.heiss@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager 2/3] ui: add 'font-logos' stylesheet and font files
Date: Wed, 7 Jun 2023 12:59:23 +0200 [thread overview]
Message-ID: <5c3f0fe2-8424-4973-5e82-777de63ba8c1@proxmox.com> (raw)
In-Reply-To: <20230503095042.137966-3-c.heiss@proxmox.com>
Am 03/05/2023 um 11:50 schrieb Christoph Heiss:
> From [0]. As they are licensed under the "Unlicence" license, including
> them here and re-distributing them should bear no problems [1].
>
> [0] https://github.com/Lukas-W/font-logos
> [1] https://choosealicense.com/licenses/unlicense/
>
> Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
> ---
> Formatted the patch with `--no-binary` for now to ease reviewing, as it
> otherwise would be pretty big for the mailing list, due to the binary
> files. For testing, either download the latest release [2] and copy
> `assets/font-logs.{ttf,woff,woff2}` from the extraced folder to
> `www/css/fonts/`, or drop me a line and I can send the full patch
> off-list.
>
> There's also the possibility to build a customized version of the font
> from source, to reduce it down to just the logos needed for the ten
> distributions currently supported/recogized. The file sizes are reduced
> to about 10-20% of their original files, so might be worth to do that -
> for example, the .woff goes from 73kB to 9.2kB.
>
> It's fairly easy, basically just throwing out all unneeded entries in
> the `icons.tsv` file in the repo. If that would be preferred, I happily
> do that; adding some instructions too on how to replicate/rebuild the
> font as needed.
>
> [2] https://github.com/lukas-w/font-logos/releases/download/v1.0.1/font-logos-1.0.1.zip
>
> www/css/Makefile | 3 +-
> www/css/font-logos.css | 224 +++++++++++++++++++++++++++++++++
> www/css/fonts/Makefile | 14 +++
> www/css/fonts/README.md | 5 +
> www/css/fonts/font-logos.ttf | Bin 0 -> 29116 bytes
> www/css/fonts/font-logos.woff | Bin 0 -> 74576 bytes
> www/css/fonts/font-logos.woff2 | Bin 0 -> 15724 bytes
> www/index.html.tpl | 1 +
> 8 files changed, 246 insertions(+), 1 deletion(-)
> create mode 100644 www/css/font-logos.css
> create mode 100644 www/css/fonts/Makefile
> create mode 100644 www/css/fonts/README.md
> create mode 100644 www/css/fonts/font-logos.ttf
> create mode 100644 www/css/fonts/font-logos.woff
> create mode 100644 www/css/fonts/font-logos.woff2
Please, let's not repeat the mistake again and pull in some binary artefacts in
manager even if they don't are directly related to it.
Lets set up a separate package, that way we can also give proper attribution
(even if the license used wouldn't necessarily require it).
I created:
https://git.proxmox.com/?p=fonts-font-logos.git;a=summary
It contains a trivial packaging, the build fonts and the CSS file, but with the
web-font path adopted to use ../fonts/ to load them, just like Font Awesome does.
That way we can add it to pveproxy in a similar manner, please test if that works
out for you.
next prev parent reply other threads:[~2023-06-07 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 9:50 [pve-devel] [PATCH manager 0/3] fix #2435: lxc: show distro and privileged status in summary Christoph Heiss
2023-05-03 9:50 ` [pve-devel] [PATCH manager 1/3] ui: clean up remnants of in-tree font-awesome files Christoph Heiss
2023-06-07 10:15 ` [pve-devel] applied: " Thomas Lamprecht
2023-05-03 9:50 ` [pve-devel] [PATCH manager 2/3] ui: add 'font-logos' stylesheet and font files Christoph Heiss
2023-06-07 10:59 ` Thomas Lamprecht [this message]
2023-06-09 9:28 ` Christoph Heiss
2023-05-03 9:50 ` [pve-devel] [PATCH manager 3/3] ui: GuestStatusView: add 'privileged' and 'ostype' fields Christoph Heiss
2023-06-07 11:49 ` Thomas Lamprecht
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=5c3f0fe2-8424-4973-5e82-777de63ba8c1@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=c.heiss@proxmox.com \
--cc=pve-devel@lists.proxmox.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