TTFEdit is a GPL editor for TrueType fonts. TrueType is a standard used by modern operating systems like Mac OS X, Windows XP, Linux and of course OS/2, also known as eComStation. There are two different TrueType specifications: from Apple (original author of this technology) and from Microsoft. Mac OS X and Windows XP use own font rendering engines, there is also FreeType library used by Linux. On these systems the same font will generally look different. TTFEdit tries to produce TTF files compatible with all mentioned systems.

System requirements
  • Minimum JRE version is 1.6
  • Graphics card with minimum resolution of 1024x768 with 16-bit color depth.
  • Program uses 256Mb RAM

TTFEdit on an eComStation machine with Open JDK

TTFEdit on an eComStation machine with Open JDK

Installing TTFEdit
Download Create a folder (directory) "TTFEdit". Unzip the file into the new created folder (directory). That's it!

The ttfedit.cmd file
With this file the program TTFEdit starts. I have made a ttfedit.cmd file with the following contents;
@echo off
set path=[drive: java]\JAVA160ga5\bin
set BEGINLIBPATH=[drive: java]\JAVA160ga5\bin
[drive: ttfedit]
cd [drive: ttfedit]\ttfedit
java -Xms256m -Xmx256m -Duser.home=[drive: ttfedit]\ttfedit -XX:+UseConcMarkSweepGC -XX:+UseParNewGC
-XX:+CMSParallelRemarkEnabled -XX:SoftRefLRUPolicyMSPerMB=100000 -Xincgc -Dsun.java2d.d3d=True
-Dsun.java2d.d3dtexbpp=16 -Dsun.java2d.translaccel=true -Dsun.java2d.ddscale=true 
-jar ttfedit.jar 2>ttfedit-bugs.txt
The last four lines are actual one line, but I had to break it up in parts. Be aware that there is a space between "ttfedit.jar" and "2>".
I use 2 separate folders (directories), one for Java and one for TTFEdit with the files created by this program. The references used in the cmd file;

  • [drive: java] = drive with Java
  • [drive: ttfedit] = drive with ttfedit

should be replaced with real drive letters. Edit and save the file "ttfedit.cmd" from the file. This file is copied to the "TTFEdit" folder (directory). Furthermore, different paths?, adjust according to your needs. Create a new program object. Specify the path and file name: "[drive: ttfedit]\ttfedit\ttfedit.cmd". In the tabpage Session check the boxes "OS/2 window", "Running as an icon" and "Close Window to end program". In the tabpage General you can enter the name "TTFEdit". You find enclosed in the file a TTFEdit OS/2 icon.

Parameters / options explained
  • The statement "-Duser.home=[drive: ttfedit]\ttfedit" will ensure that TTFEdit will save all necessary files in own directory instead of saving them in the home directory.
  • The addition "2>ttfedit-bugs.txt" ensures that errors are saved in the file "ttfedit-bugs.txt". The 2 in "2>" is not a typo!
  • The specification "-Xms256m" comes from the file run.cmd. The "-Xms256m" specify the initial size of the memory allocation pool.
  • The specification "-Xmx256m" comes from the file run.cmd. The "-Xmx256m" indicates the maximum limit.
  • All other parameters and options comes from the file run.cmd. Be aware that you can't run this file in OS/2-eCS. If you want to use this file you have to edit it first.

In the file you can find the above command file (all driveletters are set to C:) and an OS/2 TTFEdit icon:

revision May 7, 2016