Skip to main content

JavaSE 6 U 10 font rendering

It seems that the font rendering engine has changed. It looks very good and apparently uses the native ClearType on Windows now instead of it's own rendering (which was excellent).
The only bad thing for me, is that it looks blurred now. When running jedit or NetBeans with Windows Look and Feel, the font is the same as native apps but it's subtly different.
They look as good as native Windows fonts, but on my LCD they look almost like Bold has been turned on. Windows apps font seem thin compared to the heavier Java rendered font.
Labels:

Comments

Post a Comment

Popular posts from this blog

Overcome Java JNI gdb errors on GNU/Linux

If you happen to try to debug any Java JNI programs using gdb on GNU/Linux you will soon come across error messages. For example : $ gdb --args java MyJavaProgramUsingJNI cannot find user-level thread for LWP nnn: generic error warning: Cannot initialize thread debugging library: versions of libpthread and libthread_db do not match The reason for this is that the java program mucks around with LD_LIBRARY_PATH and that prevents gdb from running correctly. To overcome this, you have to run your Java program and place a pause in the Java code, such as reading a key, and then in another shell, run gdb to attach to the running Java process. You can then set your breakpoint on your JNI code and debug it. Here is an example : Compile your Java program: $ javac JNITest.java Generate the JNI header file: $ javah -jni JNITest.java Create and compile your C code library: $ cat jnilib.c #include "JNITest.h" JNIEXPORT jint JNICALL Java_JNITest_addValues( JNIEnv...
Read more