unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Bruno Victal <mirai@makinata.eu>
To: Hugo Buddelmeijer <hugo@buddelmeijer.nl>
Cc: mail@cbaines.net, 66747@debbugs.gnu.org
Subject: [bug#66747] [PATCH v2] gnu: font-google-noto: Update to 23.11.1.
Date: Wed, 29 Nov 2023 18:35:48 +0000	[thread overview]
Message-ID: <1aeab6c2-6785-425c-bc9f-231f3cad7031@makinata.eu> (raw)
In-Reply-To: <CA+Jv8O0TGnZMzVF7tnqiweNkKSqDO=nD0MxBhVF2Lx1WJfejVA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 864 bytes --]

Hi Hugo,

On 2023-11-29 14:01, Hugo Buddelmeijer wrote:
> This change seems to have broken the fonts in sway (wayland compositor).
> 
> This is my Sway status bar:
> 
> $ cat .config/sway/status.sh
> DATE=$(date +'%Y-%m-%d %H:%M:%S')
> BATTERY=$(cat /sys/class/power_supply/BAT0/capacity)
> echo "🔋${BATTERY} 📅 ${DATE}"

I didn't check with the old (and ancient, which had
U+2026 … HORIZONTAL ELLIPSIS broken) font-google-noto package though
I can confirm that I'm seeing TOFU when I lookup these characters
with 'gucharmap' command for 'Noto Sans Mono'.

Could you report this to upstream via [1] as indicated in the
README.md [2]?

[1]: <https://notofonts.github.io/reporter.html>
[2]: <https://github.com/notofonts/notofonts.github.io>

-- 
Furthermore, I consider that nonfree software must be eradicated.

Cheers,
Bruno.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-11-29 18:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25 13:25 [bug#66747] [PATCH] gnu: font-google-noto: Update to 23.10.1 Bruno Victal
2023-11-04 11:01 ` [bug#66747] [PATCH v2] gnu: font-google-noto: Update to 23.11.1 Hilton Chain via Guix-patches via
2023-11-05 18:28   ` bug#66747: " Christopher Baines
2023-11-29 14:01 ` [bug#66747] " Hugo Buddelmeijer
2023-11-29 18:35   ` Bruno Victal [this message]
2023-11-29 22:19     ` Hugo Buddelmeijer

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=1aeab6c2-6785-425c-bc9f-231f3cad7031@makinata.eu \
    --to=mirai@makinata.eu \
    --cc=66747@debbugs.gnu.org \
    --cc=hugo@buddelmeijer.nl \
    --cc=mail@cbaines.net \
    /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).