unicode rasterfont files
Posted: Sun Aug 17, 2014 4:10 pm
Unicode on Kolibri is born:
To get started, I produced (on my win7 pc) 2 unicode raster font files : Arial regular and Consolas.
Both files have the data for 2211 glyphs, for the fontsizes 7,8,10,12, and 14, and take 460Kb each.
For now, I left out the Hebrew and Arabic glyphs. (I do not intent to implement RTL (right to left) typing).
Here is a screenshot of Greek and Cyrillic unicodes (0x400 to 0x520) in proportional Arial 10 on Kolibri OS. Anti-aliasing is obtained, because the font has a 4-bit color value for each pixel.
I did not add kerning information to the fontfile. I intent to realise kerning by evaluating the pixels.
My major problem is to obtain crispy glyphs for small fonts. I still need to elaborate on this.
I will publish working results (a new Klib version) as soon as I solved these problems.
Direct screen-draw issues
The drawing routine draws the pixels directly to the framebuffer (using GS).
(The Bitblit routine has no rasterop for color blending/transparency.)
I need to add clipping logic to prevent drawing in windows in front.
Can someone point me to assembly code for this clipping logic?
Utf-8 issues
I propose utf-8 coding for strings.
This makes low-level routines more complex, but it simplifies high level routines.
It avoids having two or more versions of many OS routines (like in Win32).
I believe it becomes the favourite coding method in networking.
Are there utf8 example routines in assembly around? Is Fasm utf-8 friendly?
To get started, I produced (on my win7 pc) 2 unicode raster font files : Arial regular and Consolas.
Both files have the data for 2211 glyphs, for the fontsizes 7,8,10,12, and 14, and take 460Kb each.
For now, I left out the Hebrew and Arabic glyphs. (I do not intent to implement RTL (right to left) typing).
Here is a screenshot of Greek and Cyrillic unicodes (0x400 to 0x520) in proportional Arial 10 on Kolibri OS. Anti-aliasing is obtained, because the font has a 4-bit color value for each pixel.
I did not add kerning information to the fontfile. I intent to realise kerning by evaluating the pixels.
My major problem is to obtain crispy glyphs for small fonts. I still need to elaborate on this.
I will publish working results (a new Klib version) as soon as I solved these problems.
Direct screen-draw issues
The drawing routine draws the pixels directly to the framebuffer (using GS).
(The Bitblit routine has no rasterop for color blending/transparency.)
I need to add clipping logic to prevent drawing in windows in front.
Can someone point me to assembly code for this clipping logic?
Utf-8 issues
I propose utf-8 coding for strings.
This makes low-level routines more complex, but it simplifies high level routines.
It avoids having two or more versions of many OS routines (like in Win32).
I believe it becomes the favourite coding method in networking.
Are there utf8 example routines in assembly around? Is Fasm utf-8 friendly?