On Sun, 10 Dec 2000, [EMAIL PROTECTED] wrote:
>
> And a cast to (unsigned int) and a cast to (unsigned char) will naturally produce
>different values.
>
> The bad news are that I haven't got a clue on how you can keep Unicode support...
>yet the way libfnt works right now, it
> doesn't support what is the most important subset of Unicode, at least according to
>my (highly! :-) eurocentric view.
I hope you understand that I wanted unicode support so Euro-people would be
happy not upset.
If the cast sets the ascii value from negative to positive and works, why not
have the ascii value be positive in the first place? What's up with that?
I think in the CharS case your cast is a good idea. It gets the "correct"
behaviour in the most cases.
Unicode can be kept if we add gftPrintCode(vis, code) and gftCodeAdv(code)
etc. and changed the PrintChar(vis, uint code) PrintChar(vis, char );
I'll add them to the api. I thought that I could combine the routines for
char and unicode into one routine since they are so close. I was wrong I
guess. So gftCode* routines should be added in order to separate the two
types of values.
No?
--
Lee Brown Jr.
[EMAIL PROTECTED]
