Property Files for Printer Peripheral Type 

Purpose

The emulator property files offer the option to add or remove available fonts and media from the emulator.

Each property file may have two versions, a default and a user specific version. The default file has a DFT extension, for example "filename.dft". The second file has an extension of ".username", that is “filename.username”. The extension "username" refers to the logon name of the user.

The default versions are created the first time the Emulator runs. The user specific versions are created when the property files are modified through the Capability… and/or Setup… windows.

Features

All property files follow the Java Property file format:

●      The line starting with “#” is a comment line.

●      Other lines follow the “Key=Value” format.

If a Key has a space as part of the name, for example “Courier New”, a backslash (\) must be inserted before the space. The Key in the file will look like:

Courier\ New

...

●      When a list is assigned to a Key the values are separated by a coma and no spaces are allowed between the coma and the value. For example, Key1=value1,value2,value3, and so on.

The property files are located in the path ECLIPSE_HOME\plugins\com.sap.ip.me.mdk.pios.docgen_X.Y.Z\emulator\inst\Printer.

ECLIPSE_HOME refers to the location in the hard disk where Eclipse is installed and X.Y.Z refers to the current version, for example, 1.1.0.

Constraints

●      The system does not validate the parameters values. SAP strongly recommends that you make a backup before modifying a property file.

●      Invalid key values can cause unexpected behavior in the emulator. For example, if you add a font in InstalledFontFamilies with a space between the comma and the font name (, font), the Emulator starts Java Virtual Machine (JVM) but no screen appears.

●      The Emulator loads the configuration files when it is started. The Emulator must be restarted whenever a file is modified for the changes to take effect.

●      Fonts and their respective styles and sizes must be available (installed) in the operating system.

●      A mobile application can use an installed font only if its configuration can be found in the font configuration file. A font can be installed in the Emulator only if it is available in the operating system and is added to the InstalledFont file. The font configuration must be added separately in the pipremulator.fntcfg file to be available for use by the mobile application.