Changeset 231

Timestamp:

Jan 9, 2011, 4:52:44 PM (15 years ago)

Author:

dmik

Message:

jdk: Added fontconfig for the Liberation font family and placed instructions how to activate it to README.OS2.

Location:

trunk

Files:

• doc/README.OS2 (modified) (5 diffs)
• openjdk/jdk/make/sun/awt/Makefile (modified) (2 diffs)
• openjdk/jdk/src/os2/classes/sun/awt/os2/fontconfig.liberation.properties (added)

trunk/doc/README.OS2

@@ -52 +52 @@
   of your CONFIG.SYS (and reboot) to make the given Java installation the
   default one.
+
+  Please read the further sections (especially the "CURRENT LIMITATIONS" section
+  below) to make sure that you are aware of possible problems you may run into
+  while running Java applications using this product.
+
+
+
+FONT SELECTION
+
+  OpenJDK comes with no fonts and uses the system fonts by default. On OS/2,
+  these fonts are Helvetica, Times New Roman and Courier -- they are are
+  present in any version of OS/2. However, these are very old Type1 fonts with
+  many glyphs having poor quality which can be seen even with font anti-aliasing
+  turned on.
+
+  For this reason, OpenJDK for OS/2 provides an alternative font configuration
+  that uses a freely available Liberation font family: Liberation Sans,
+  Liberation Serif and Liberation Mono (with font metrics close to a widely
+  used set of Monotype TTF fonts: Arial, Times New Roman and Courier New,
+  respectively). In order to use the Liberation font family instead of the
+  default Type1 fonts, do the following:
+
+  1. Download the latest binary (TTF) archive of Liberation fonts from:
+
+     https://fedorahosted.org/liberation-fonts/
+
+  2. Copy all *.TTF files from the archive to a directory and install them
+     normally (for example, using the OS/2 Font Palette object).
+
+  3. Go to the directory "<OpenJDK>\bin\jre\lib" (where <OpenJDK> is where you
+     installed the OpenJDK package) and copy the file
+     "fontconfig.liberation.bfc" to "fontconfig.bfc". It is safe to overwrite
+     the target file.
+
+  In order to return back to the default fonts, go to "<OpenJDK>\bin\jre\lib"
+  again and copy the file "fontconfig.default.bfc" to "fontconfig.bfc".
+
+  Note that you need to restart all Java applications to let them pick up the
+  new fonts.
+
+  Font Anti-Aliasing
+
+  In the current release, due to the low quality of the standard OS/2 Type1
+  fonts, both AWT and Swing Java GUI toolkits use subpixel font anti-aliasing by
+  default for all standard components.
+
+  If you want to change this behavior, you may use the following Java command
+  line option:
+
+       -Dawt.useSystemAAFontSettings=<mode>
+
+  where <mode> is one of the following anti-aliasing modes:
+
+  off              Turns anti-aliasing off
+  on               Turns on monochrome anti-aliasing
+  lcd | lcd_hrgb * Turns on subpixel anti-aliasing optimized for HRGB LCD panels
+  lcd_hbgr         Turns on subpixel anti-aliasing optimized for HBGR LCD panels
+  lcd_vrgb         Turns on subpixel anti-aliasing optimized for VRGB LCD panels
+  lcd_vbgr         Turns on subpixel anti-aliasing optimized for VBGR LCD panels
+
+  The setting marked with * is the default anti-aliasing value as it is suitable
+  for the majority of the modern display hardware.
 
 
@@ -73 +135 @@
   is known to be 512M. In later versions it is controlled by the
   VIRTUALADDRESSLIMIT parameter in CONFIG.SYS (which is specified in megabytes
-  and defaults to 1024M).
+  and defaults to 1024).
 
   Furthermore, not all memory within the virtual address limit is available to
@@ -112 +174 @@
      arena.
 
-  So, if your machine has, say, 2G of RAM and you attempt to start it in server
-  mode (using the -server command line option), Java will want 512M (2G/4) plus
-  additional 20-30%. This would obviously not fit into 432M of free private
-  memory available for the process when VIRTUALADDRESSLIMIT is set to 1024 and
-  it was the case with earlier releases of OpenJDK 6 for OS/2 as well as with
-  the releases of InnoTek Java 1.4.x for OS/2.
+  So, if your machine has, say, 2G of RAM and you attempt to start a Java
+  application Java server mode (using the -server command line option), Java
+  will want 512M (2G/4) plus additional 20-30%. This would obviously not fit
+  into 432M of free private memory available for the process when
+  VIRTUALADDRESSLIMIT is set to 1024 and this was the case with earlier releases
+  of OpenJDK 6 for OS/2 as well as with the releases of InnoTek Java 1.4.x for
+  OS/2.
 
   Starting with version 6 Beta 2, OpenJDK for OS/2 solves this problem by
   limiting the amount of memory Java wants for the heap to the actual size of
   the available memory block in the private arena. So, in the above case Java
-  would actually get about 310M in server mode (instead of performing a failed
+  will actually get about 310M in server mode (instead of performing a failed
   attempt to allocate 512M). You may change this limit by changing the
   VIRTUALADDRESSLIMIT value in CONFIG.SYS (according to the table above), but
@@ -133 +196 @@
   command line option if you are not satisfied with the default value for some
   reason or if your applcation gives you the "Could not reserve enough space for
-  object heap" message at startup. However, keep in mind that if you specify a
-  -Xmx value which is, increased by 20-30% as described in step 3 above, bigger
-  than the maximum free block in the private arena, you will get the same memory
-  allocation error which indicates that you should use a smaller value.
+  object heap" error message at startup. However, keep in mind that if you
+  specify a -Xmx value which is, increased by 20-30% as described in step 3
+  above, bigger than the maximum free block in the private arena, you will get
+  the same memory allocation error which indicates that you should use a smaller
+  value.
 
 
@@ -151 +215 @@
      subdirectory of the SDK distribution archive).
 
-  3. AWT and Swing always use font anti-aliasing for all standard components.
-     If you want to disable anti-aliasing, you may use the following Java
-     command line argument:
-
-       -Dawt.useSystemAAFontSettings=off
-
-     However, this is not recommended since Java uses standard OS/2 Type1
-     fonts by default which look really ugly with anti-aliasing turned off.
-
   3. Some rarely used Java system classes may be still missing in this release.
 

trunk/openjdk/jdk/make/sun/awt/Makefile

@@ -447 +447 @@
 FONTCONFIGS_SRC = $(PLATFORM_SRC_OS2)/classes/sun/awt/os2
 _FONTCONFIGS = \
-        fontconfig.properties
+        fontconfig.properties \
+        fontconfig.liberation.properties
 
 FONTCONFIGS_SRC_PREFIX =
@@ -499 +500 @@
 FONTCONFIGS     = $(_FONTCONFIGS:%=$(LIBDIR)/%.src)
 BINARYFONTCONFIGS = $(_FONTCONFIGS:%.properties=$(LIBDIR)/%.bfc)
+
+ifeq ($(PLATFORM), os2)
+# copy the default fontconfig file to fontconfig.default.* for convenience
+FONTCONFIGS       += $(LIBDIR)/fontconfig.default.properties.src
+BINARYFONTCONFIGS += $(LIBDIR)/fontconfig.default.bfc
+$(LIBDIR)/fontconfig.default.properties.src: $(LIBDIR)/fontconfig.properties.src
+        $(install-file)
+$(LIBDIR)/fontconfig.default.bfc: $(LIBDIR)/fontconfig.bfc
+        $(install-file)
+endif
 
 fontconfigs: $(FONTCONFIGS) $(BINARYFONTCONFIGS)