*>Hold your horses – what you do currently is already part of the GSoC*
*>project! Right now you should do some preliminary investigations only*
*>so that you are able to write a useful proposal.*
Got it! :)
*>That said, `zlog` looks indeed promising. Not sure about the Windows*
*>port,
Hello Priyesh,
> Working forward in an external library hunt i came across two
> C based logging libraries: [...]
>
> I am also working on a prototype that will print log messages
> generated by FT_ERROR into a log file.
Hold your horses – what you do currently is already part of the GSoC
Hey,
Working forward in an external library hunt i came across two C based
logging libraries:
1.log4c
2.zlog
In the above mentioned libraries zlog claims to be faster, more safer and
powerful.
It is also well tested and mature, it also has a windows version.
Some of zlog's features which i think
I've just updated our GSoC pages with the following.
Port the font-rs rendering engine to FreeType
Raph Levien has developed font-rs[1], an experimental font
renderer written in the Rust programming language. A blogpost
describes some of its features in more detail; of
> So you're saying the only anti-aliasing is overkill
> anti-aliasing.
? What do you mean?
> Who thought of this as a good idea? It is ever so slightly more
> accurate but really not worth it on lower end hardware such as
> embedded systems. 4*4 oversampling is a high priority feature
>
