Offline Translation File Support

Translations that support multiple languages in SAP POS exist in databases that only become available when a cashier signs on. This means that the required language may not be displayed until a connection to the database is established. To support availability of the main store language before connection to the database the following offline files are created.

POS Application	Name of Offline File	Example of Use
Configurator	POSCFGW.OFL POSCFGW.OFL is generated when the application translatable object configuration files translate_objects_cfg.txt and translate_original_cfg.txt are applied by the Configurator application in a translatable objects synchronization process. During this process, the references to the offline translatable objects are extracted from the USERDB.DB database and used to populate the offline language translation file.	The following is an example of POSCFGW.OFL: [ENG Translation] u_action_ok::text=&OK MSG::E12=Release information not available. Notify SAP Support MSG::E13=Wrong number of input arguments, Input arguments: [Password] [Drive\Path] MSG::E14=Error in input arguments, Drive\Path is not valid MSG::M0=Microhelp …
Store Manager	BACKOFF.OFL The offline language file contains references to any object, literal, or message and associated translated text that are defined to display in offline mode. BACKOFF.OFL is generated when the application translatable object configuration files translate_original.txt and translate_objects.txt are applied by the Store Manager application to synchronize the set of translatable objects. During this synchronization process, the references to the offline translatable objects are extracted from the BACKOFF database and used to populate the offline language translation file. The existing translation maintenance window in the Store Manager application allows the user to define translations for any of the translatable objects, including those objects denoted as being offline. When the translations are saved through the translation window, the BACKOFF.OFL file is updated with the translations.	The following is an example of a section in BACKOFF.OFL defined for English translations (ISO code=ENG): [ENG Translation] d_elapsed_time::elapsedtime_t=>>>Elapsed Time d_srvconnect_info::connected_t=>>>Connected d_srvconnect_info::license_t=>>>License d_srvconnect_info::port_t=>>>Port # d_srvconnect_info::server_t=>>>Server Address d_srvconnect_info::version_t=>>>Version m_mdi_frame::[1]=>>>&Topics …
Electronic Journal Viewer	JOURNAL.OFL This file is used to translate any messages, literals, or object texts required before the application connects to the database. The layout of JOURNAL.OFL consists of a reference to the object and the translated text. There is a separate section in the offline language file for each language defined for the Electronic Journal Viewer application. The offline language file is automatically created when the application translation object configuration files translate_objects_jrl.txt and translate_original_jrl.txt are applied by the Electronic Journal Viewer application to synchronize translatable objects.

POS Application

Name of Offline File

Example of Use

Configurator

POSCFGW.OFL

POSCFGW.OFL is generated when the application translatable object configuration files translate_objects_cfg.txt and translate_original_cfg.txt are applied by the Configurator application in a translatable objects synchronization process. During this process, the references to the offline translatable objects are extracted from the USERDB.DB database and used to populate the offline language translation file.

The following is an example of POSCFGW.OFL:

[ENG Translation]

u_action_ok::text=&OK

MSG::E12=Release information not available. Notify SAP Support

MSG::E13=Wrong number of input arguments, Input arguments: [Password] [Drive\Path]

MSG::E14=Error in input arguments, Drive\Path is not valid

MSG::M0=Microhelp …

Store Manager

BACKOFF.OFL

The offline language file contains references to any object, literal, or message and associated translated text that are defined to display in offline mode. BACKOFF.OFL is generated when the application translatable object configuration files translate_original.txt and translate_objects.txt are applied by the Store Manager application to synchronize the set of translatable objects. During this synchronization process, the references to the offline translatable objects are extracted from the BACKOFF database and used to populate the offline language translation file.

The existing translation maintenance window in the Store Manager application allows the user to define translations for any of the translatable objects, including those objects denoted as being offline. When the translations are saved through the translation window, the BACKOFF.OFL file is updated with the translations.

The following is an example of a section in BACKOFF.OFL defined for English translations (ISO code=ENG):

[ENG Translation]

d_elapsed_time::elapsedtime_t=>>>Elapsed Time

d_srvconnect_info::connected_t=>>>Connected

d_srvconnect_info::license_t=>>>License

d_srvconnect_info::port_t=>>>Port #

d_srvconnect_info::server_t=>>>Server Address

d_srvconnect_info::version_t=>>>Version

m_mdi_frame::[1]=>>>&Topics

…

Electronic Journal Viewer

JOURNAL.OFL

This file is used to translate any messages, literals, or object texts required before the application connects to the database. The layout of JOURNAL.OFL consists of a reference to the object and the translated text. There is a separate section in the offline language file for each language defined for the Electronic Journal Viewer application.

The offline language file is automatically created when the application translation object configuration files translate_objects_jrl.txt and translate_original_jrl.txt are applied by the Electronic Journal Viewer application to synchronize translatable objects.