On Thu, Jun 13, 2013 at 5:49 PM, David <lists@edeca.net> wrote:
> On 2013-06-13 13:03, Manu Abraham wrote:
>> On Thu, Jun 13, 2013 at 5:05 PM, David <lists@edeca.net> wrote:
>>>
>>> I use MuGUI Font & Bitmap generator, from www.mugui.de to produce
>>> these:
>>> https://github.com/edeca/Electronics/blob/master/Include/fonts/font_luc=
idaconsole.h
>>>
>>> It is especially nice because it supports custom XSL files[1] which
>>> allow you to generate the output in any way you'd like.  There are
>>> some
>>> good built-in examples, but if you want to integrate with existing
>>> code
>>> you can tweak the output into any format you'd like.
>>>
>>> There are some example photos of a GLCD with my fonts/code halfway
>>> down
>>> my ST7565 tutorial:
>>> http://edeca.net/wp/electronics/the-st7565-display-controller/
>>>
>>> David
>>>
>>> 1 - See
>>> https://github.com/edeca/Electronics/blob/master/Support/GlcdFiles/mugu=
i_edeca.xsl
>>
>> I downloaded MuGUI yesterday and tried playing with it a bit.
>> The generated font header confuses me a bit:
>>
>>       /* Index 3, character 35 "#" (width: 13 pixels) */
>> 0xD,
>> 0x70,0x0E,0x00,0x70,0x6E,0x00,0x70,0x7F,0x00,0xF8,0x7F,0x00,0xFE,0x1F,0x=
00,0xFE,0x0E,0x00,0x76,0x6E,0x00,0x70,0x7F,0x00,0xF8,0x7F,0x00,0xFE,0x1F,0x=
00,0xFE,0x0E,0x00,0x76,0x0E,0x00,0x70,0x0E,0x00,
>>
>>
>> What the relevance of 0xD ? Is it because it is using variable width
>> fonts ?
>> I liked the MuGUI interface a bit, but the results got me confused
>> quite a bit
>> and made me look at other alternatives.
>>
>> I think, fixed width fonts are better suited in my case. (I am not
>> really sure
>> about that, but being simpler to handle and hence that comment. Have
>> started to play with it since a few days alone.)
>
> When you import a font you have the choice of proportional or fixed
> width.  I believe the default XSL output files will generate fixed width
> information.
>
> The 0xD is the width, which is 13 and therefore the same as the width
> in the comment.  Looks like whatever font you used was tall enough to
> require three bytes (this will be in the font header), thus there are 39
> total data bytes in the character above.
>
> I didn't like the default XSL files much so I wrote my own.  It did
> take some fiddling, but reading through the example XSL files will
> likely teach you a lot.

One issue that I found, with my display:

B00,B01,B02,B03,B04,B05,B06,B07,B08,B09,B10,B11,B12,B13,B14,B15   <-- Page0
B16,B17,B18,B19,B20,B21,B22,B23,B24,B25,B26,B27,B28,B29,B30,B31   <-- Page1
B32,B33,B34,B35,B36,B37,B38,B39,B40,B41,B42,B43,B44,B45,B46,B47   <-- Page2

must be written for a 16x24 font

ie for eg (a hand crafted array):

char t1[] =3D {
	0xaa, 0x55, 0xaa, 0x55, 0xaa, 0x55, 0xaa, 0x55,
	0xaa, 0x55, 0xaa, 0x55, 0xaa, 0x55, 0xaa, 0x55,
	0xaa, 0x55, 0xaa, 0x55, 0xaa, 0x55, 0xaa, 0x55,
	0xaa, 0x55, 0xaa, 0x55, 0xaa, 0x55, 0xaa, 0x55,
	0xaa, 0x55, 0xaa, 0x55, 0xaa, 0x55, 0xaa, 0x55,
	0xaa, 0x55, 0xaa, 0x55, 0xaa, 0x55, 0xaa, 0x55,
};

gives me a nice 16x24 hatched rectangular box.

None of the byte orientations in muGUI doesn't seem to display the
font correctly ?
(Proportional checkbox, unchecked, which should give me fixed width fonts ?=
)

The generated '0' looks thus:

char t2[]=3D{
	0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
	0xC0, 0x07, 0x60, 0x0C, 0x30, 0x18, 0x30, 0x18,
	0x18, 0x30, 0x18, 0x30, 0x18, 0x30, 0x18, 0x30,
	0x18, 0x30, 0x18, 0x30, 0x18, 0x30, 0x30, 0x18,
	0x30, 0x18, 0x60, 0x0C, 0xC0, 0x07, 0x00, 0x00,
	0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
};

The displayed '0' doesn't look like a Zero at all, but I can make out
the 6 pieces of
the Zero very clearly. Seems like the byte orientation is incorrect ?

Any ideas ?

Regards,

Manu
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.