On Sun, Feb 10, 2013 at 11:05:27PM +, Ken Moffat wrote:
> On Sun, Feb 10, 2013 at 02:53:31PM -0600, Randy McMurchy wrote:
> >
> > I have version 287 installed and have the exact same error in my configure
> > logs.
> >
> Thanks. If I manage to fix it, I'll commit the change. At the
> momen
On Sun, Feb 10, 2013 at 02:53:31PM -0600, Randy McMurchy wrote:
> Ken Moffat wrote these words on 02/10/13 13:04 CST:
> > configure:14508: checking for usable Xft/fontconfig package
> > configure:14534: gcc -o conftest -g -O2 -D_GNU_SOURCE
> > -DNARROWPROTO=1 -DFUNCPROTO=15 -DOSMAJORVERSION=3 -DOS
Randy McMurchy wrote:
> Ken Moffat wrote these words on 02/10/13 13:04 CST:
>> configure:14508: checking for usable Xft/fontconfig package
>> configure:14534: gcc -o conftest -g -O2 -D_GNU_SOURCE
>> -DNARROWPROTO=1 -DFUNCPROTO=15 -DOSMAJORVERSION=3 -DOSMINORVERSION=8
>> -I/usr/include/freetype2 c
Ken Moffat wrote these words on 02/10/13 13:04 CST:
> configure:14508: checking for usable Xft/fontconfig package
> configure:14534: gcc -o conftest -g -O2 -D_GNU_SOURCE
> -DNARROWPROTO=1 -DFUNCPROTO=15 -DOSMAJORVERSION=3 -DOSMINORVERSION=8
> -I/usr/include/freetype2 conftest.c -lXft -lXmu -lX
On Sun, Feb 10, 2013 at 09:25:21PM +0100, Aleksandar Kuktin wrote:
> >On Sun, 10 Feb 2013 19:04:29 +
> >Ken Moffat wrote:
> >
> > On Sun, Feb 10, 2013 at 05:17:58PM +, Ken Moffat wrote:
> > > Oh well,
> > > perhaps (some) legacy fonts need to stay in the book for xterm.
> > > [sigh/].
>
>On Sun, 10 Feb 2013 19:04:29 +
>Ken Moffat wrote:
>
> On Sun, Feb 10, 2013 at 05:17:58PM +, Ken Moffat wrote:
> > Oh well,
> > perhaps (some) legacy fonts need to stay in the book for xterm.
> > [sigh/].
> >
> Actually, it looks like a configure problem in xterm, prompted by a
> toolc
On Sun, Feb 10, 2013 at 05:17:58PM +, Ken Moffat wrote:
> Oh well,
> perhaps (some) legacy fonts need to stay in the book for xterm.
> [sigh/].
>
Actually, it looks like a configure problem in xterm, prompted by a
toolchain change in the last couple of years :
configure:14508: checking for
On Sun, Feb 10, 2013 at 01:08:56PM +0100, Aleksandar Kuktin wrote:
> >On Sun, 10 Feb 2013 02:29:58 +
> >Ken Moffat wrote:
>
> > So, does xterm handle these glyphs in UTF-8 for anyone ? If so,
> > what do you have in /etc/X11/app-defaults/XTerm or ~/.Xresources ?
>
> I can confirm that XTer
On Sun, Feb 10, 2013 at 01:09:55PM +0100, Pierre Labastie wrote:
>
> OTH, I just see that comment in the file:
> ! xterm can switch at runtime between bitmap (default) and TrueType fonts.
> ! The "faceSize" resource controls the size of the latter. However, it was
> ! originally given with a size
Le 10/02/2013 12:58, Pierre Labastie a écrit :
> On Debian, the last four lines of /etc/X11/app-defaults/XTerm are
> commented out (including the faceName one), so those lines might not be
> the ones you want to modify.
>
>
Sorry, that is not accurate. I meant that the lines
*VT100*locale: true
*V
>On Sun, 10 Feb 2013 02:29:58 +
>Ken Moffat wrote:
> So, does xterm handle these glyphs in UTF-8 for anyone ? If so,
> what do you have in /etc/X11/app-defaults/XTerm or ~/.Xresources ?
I can confirm that XTerm renders the string correctly for me.
Since I have no idea how does one configu
Le 10/02/2013 03:29, Ken Moffat a écrit :
> In connection with reviewing the TrueType fonts I build, I was
> going to ask if there was a reason why the book still installs
> legacy xorg fonts. I've only used TTF/OTF fonts for several years,
> and the only issue I've noticed is that xcalc can't d
In connection with reviewing the TrueType fonts I build, I was
going to ask if there was a reason why the book still installs
legacy xorg fonts. I've only used TTF/OTF fonts for several years,
and the only issue I've noticed is that xcalc can't display a square
root sign on the appropriate keycap
13 matches
Mail list logo
