GNU bug report logs - #77917
31.0.50; [PATCH] Stop using the "stop" sign for all warning levels

Previous Next

Full log

Message #106 received at 77917 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stephen Berman <stephen.berman <at> gmx.net>
Cc: rpluim <at> gmail.com, juri <at> linkov.net, 77917 <at> debbugs.gnu.org,
 yantar92 <at> posteo.net, prot <at> protesilaos.com
Subject: Re: bug#77917: 31.0.50; [PATCH] Stop using the "stop" sign for all
 warning levels
Date: Tue, 06 May 2025 18:33:48 +0300

> From: Stephen Berman <stephen.berman <at> gmx.net>
> Cc: Robert Pluim <rpluim <at> gmail.com>,  yantar92 <at> posteo.net,
>   77917 <at> debbugs.gnu.org,  prot <at> protesilaos.com,  juri <at> linkov.net
> Date: Tue, 06 May 2025 14:04:07 +0200
> 
> On Tue, 06 May 2025 14:29:34 +0300 Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
> >> I conclude from that that we should use U+26A0 U+FE0F ⚠️ as the symbol
> >> to insert.
> >
> > Really?  So we've just made another full circle back to the beginning?
> > Where someone said, and I agree, that showing ⚠️ explains itself worse
> > than the existing symbol, because it could be easily interpreted as
> > meaning just "Warning".
> 
> What about the character "ℹ" (#x2139 INFORMATION SOURCE), perhaps with a
> box face attribute, or alternatively as emoji "ℹ️"?  This sign is widely
> recognized and I think even invites clicking to see what the information
> is (though having an explicit button as well would avoid any
> misunderstanding).

If this is recognized widely enough, sure.  But can you point to some
examples of using this for that purpose?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.