Baslinux mailing list

[Sindi Keesan <keesan AT iamjlamb.com>]

I don't know why your problem occurs after using X since I think
setfont is for console fonts.


If you are using a .psf font, you also have to do something about getting 
the correct unicode map for it.  One way to do this is first to load a 
.psfu font such as viscii (Vietnamese) and after this the .psf fonts will 
be mapped correctly.  Then showfont (I think?) will display the characters 
in the font currently in use.  Setfont puts it back to a default.  You can 
compare the locations of the line drawing characters in the default font 
and in what you have chosen, and then see if loading a unicode font 
followed by latin4 fixed your problem.

You can load viscii and then lat4 in rc.M (?some rc, anyway).
Another approach is to copy the unicode mapping from viscii (after loading 
it) to a file that you then load.  Read about setfont, it is something 
like (run from the command line after booting into linux)
setfont visci.... (full name without the .gz.psfu)
setfont -ou unicode  (this copies the current mapping to 'unicode')

Then put into rc.M  (with the complete path names)
/usr/bin/setfont -u /usr/local/kbd/consolefonts/unicode
/usr/bin/setfont /usr/local/kbd/consolefont/lat4....(full name of font)

Then it should load latin 4 with the correct unicode mapping every time 
you start linux.

I may have the details wrong - read the setfont manual page on this.

On Wed, 12 May 2004, Paulo Orvalho wrote:

> I do load a font for the pt_PT.map keymap at startup
> setfont lat4-16.psf...
> 
> I commented out the line at start up and it solved it.... :)
> But i need a special font for the pt_PT.map, i will try others and see...
> But thanxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....
> ----- Original Message ----- 
> From: "Sindi Keesan" <keesan AT iamjlamb.com>
> To: <baslinux AT lists.ibiblio.org>
> Sent: Wednesday, May 12, 2004 10:34 PM
> Subject: Re: [BL] Strange lines after startx
> 
> 
> > On Wed, 12 May 2004, Paulo Orvalho wrote:
> >
> > >
> > >
> > >
> > > Just tried that ( substitute xvesa ) and no deal....:(((( I got the same
> > > problem......
> > > Also i boot directly from the hardrive....
> > > The lines are still not drawn.... I get instead of a line
> > > AAAAAAAAAAAAAAAAAAAA...
> >
> > Have you loaded a character set different from the standard one?
> > If I load a Cyrillic font I have problems like what you describe.
> > Can someone else explain how to display the currently used font in X?  I
> > only know how for console mode (showfont I think it is).
> >
> > >
> > > > ----- Original Message -----
> > > > From: "Sindi Keesan" <keesan AT iamjlamb.com>
> > > > To: <baslinux AT lists.ibiblio.org>
> > > > Sent: Wednesday, May 12, 2004 5:00 PM
> > > > Subject: Re: [BL] Strange lines after startx
> > > >
> > > >
> > > > > On Wed, 12 May 2004, Paulo Orvalho wrote:
> > > > >
> > > > > > BasicLinux 2.10 with the Xvesa setup of BasicLinux 3.20
> > > > > >
> > > > > > I tried it on 3 or 4 different computers and i get the same
> result....
> > > > >
> > > > > Steven can explain it to you better, but I think you are not
> supposed to
> > > > > mix programs from these two versions of linux because they use
> different
> > > > > basic libraries.  Slackware through version 4 used libc5 and later
> > > > > versions used libc6 also known as glibc.  You can probably use the
> > > > > programs from Slackware 7 in later versions of Slackware, or from
> > > > > Slackware 3 with Slackware 4, but you cannot mix versions with
> different
> > > > > libc numbers.
> > > > >
> > > > > BL2 is based on Slackware 7, BL3 on Slackware 3 with a kernel 2.2.16
> > > > > (similar to that in BL2) that Steven compiled to be very small.  You
> can
> > > > > use Slackware 3 or 4 programs with BL3.
> > > > >
> > > > > Look for an Xvesa.tgz (xvesa.tgz) at delilinux that was compiled for
> > > > > Slackware 7.1 and substitute that for the one from BL3, for use in
> BL2.
> > > > >
> > > > > Also you cannot use Xvesa after booting with MS-DOS 6.22.  Try
> DR-DOS or
> > > > > the DOS from Win9x.   Or hit F5 while booting MS-DOS to bypass the
> > > > > config.sys files.  himem.sys interferes with Xvesa.
> > > > >
> > > > > > ----- Original Message -----
> > > > > > From: "David Lane" <Jaypooh3 AT hotmail.com>
> > > > > >
> > > > > >
> > > > > > > Hardware/version of Basic Linux please,
> > > > > > >
> > > > > > > David Lane
> > > > >
> > > > > David, you certainly asked a leading question!
> > > > >
> > > > > _______________________________________________
> > > > > BasLinux mailing list
> > > > > BasLinux AT lists.ibiblio.org
> > > > > http://lists.ibiblio.org/mailman/listinfo/baslinux
> > > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > BasLinux mailing list
> > > BasLinux AT lists.ibiblio.org
> > > http://lists.ibiblio.org/mailman/listinfo/baslinux
> > >
> >
> > _______________________________________________
> > BasLinux mailing list
> > BasLinux AT lists.ibiblio.org
> > http://lists.ibiblio.org/mailman/listinfo/baslinux
> 
> _______________________________________________
> BasLinux mailing list
> BasLinux AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/baslinux
>