GNU bug report logs -
#78155
31.0.50; eintr manual 1.8.3 Variable Number of Argument unknown charecters
Previous Next
Full log
Message #29 received at 78155 <at> debbugs.gnu.org (full text, mbox):
Ping! Ping! Ping! Po Lu, please chime in.
> Cc: theothernighttheotherday <at> gmail.com, 78155 <at> debbugs.gnu.org
> Date: Sat, 24 May 2025 11:54:37 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
>
> Ping! Ping!
>
> > Cc: 78155 <at> debbugs.gnu.org, theothernighttheotherday <at> gmail.com
> > Date: Sat, 10 May 2025 13:02:30 +0300
> > From: Eli Zaretskii <eliz <at> gnu.org>
> >
> > Ping! Po Lu, could you please chime in?
> >
> > > Cc: 78155 <at> debbugs.gnu.org
> > > Date: Wed, 30 Apr 2025 11:25:06 +0300
> > > From: Eli Zaretskii <eliz <at> gnu.org>
> > >
> > > > From: badli al rashid <theothernighttheotherday <at> gmail.com>
> > > > Date: Wed, 30 Apr 2025 15:05:26 +0800
> > > > Cc: 78155 <at> debbugs.gnu.org
> > > >
> > > > The output
> > > >
> > > > "-1ASC-Droid Sans Mono-regular-normal-normal-*-37-*-*-*-m-0-iso10646-1"
> > >
> > > So I guess this font is not a good choice for Emacs.
> > >
> > > Po Lu, what are our recommendations for fonts to use in the Android
> > > port? Do users need to do something special on Android devices to
> > > have reasonable font setup? It sounds like this user has no fonts at
> > > all that could display the non-ASCII symbols used by info.el. If this
> > > situation is probable enough, perhaps the test in info.el that probes
> > > these characters for being displayable should in the Android case
> > > disregard the display-multi-font-p condition?
> > >
> > >
> > >
> > >
> >
> >
> >
> >
>
>
>
>
This bug report was last modified 10 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.