nanogui: About pcf_readbitmaps function
Subject:
Re: [nanogui] About pcf_readbitmaps function
From:
"Caleb Harper" ####@####.####
Date:
1 Feb 2007 06:06:41 +0000
Message-Id: <2e9c26800701312206x72ac58dt9254b6170111f0c2@mail.gmail.com>
Hi,
I'm new to nano-X, and I've also noticed that the .pcf files from my FC
install cause nano-X to crash. I've only had success with the .pcf files
packaged with nano-X. Do I need a special tool to generate valid .pcf files
(I've tried bdftopcf) or is there somewhere I can download them?
Thanks,
Caleb Harper
On 2/1/07, max xiayi ####@####.#### wrote:
>
> Hi Greg,
>
> Thanks for your important message.
>
> I do check the byte order. It seems that my config file is set correctly.
> After analyse the pcf file, i found the point.
> The pcf font files I use on arm board is from my PC ,Fedora 5. The files
> seems that the byte order differs between the front header part and the
> latter parts. And engine/font_pcf.c fails to deal with that situation.
> For example,
> helvB18-ISO8859-1.pcf,
> format = readLSB32(file); //the format is got is 00 00 00 0E
> endian = (format & PCF_BIT_MASK)? PCF_LSB_FIRST: PCF_MSB_FIRST;
> num_glyphs = readLSB32(file);
> // The value should be 00 00 00 C0, however after readLSB32, i got C0 00
> 00
> 00. it is wrong.
> This is the reason of why my ARM system crashes.
>
> Thanks
> Max
> 2007/2/1, Greg Haerr ####@####.####
> >
> > : num_glyphs = readLSB32(file);
> > : it seems that the num_glyphs is not read correctly.
> >
> > Check your endian format and make sure that the config
> > file has it specified correctly. (BIGENDIAN=Y or N)
> >
> > Regards,
> >
> > Greg
> >
>
>
