[meem]

Originally Posted by tekkasit

@meem I think it is Java 1.4 font properties file format, the documentation is at http://download.oracle.com/javase/1..../fontprop.html

This section should be helpful:

Component Font Character Encodings:

Component font character encoding properties indicate which character encoding AWT should use when accessing the corresponding component fonts. These properties are only needed if the component fonts cannot be accessed using Unicode - newer TrueType fonts can usually be accessed using Unicode and don't need this property.

The keys have the form:

fontcharset.LogicalFontName.ComponentIndex

The values are fully qualified class names of character converters. In this release, character converters are accessed using the old sun.io interfaces, so only the character encodings provided by the Java 2 Runtime Environment can be used. The class names for the publicly supported character encodings are of the form:

sun.io.CharToByteCanonicalName

In a future release, character converters will be accessed through the new java.nio.charset API, which will enable the use of third-party character converters.

And this is Supported Encodings.
But I ask about syntax and efficiency.
As you can see above, the value in font.properties file is "ISO8859_1" not "ISO-8859-1" as what in the reference.
Any way, I am using now:

PHP Code:

fontcharset.serif.0=sun.io.CharToByteUTF-8 


and my custom font is worked perfectly, maybe it's not needed, so I'll try to restore the old value to see the effect.