Browse Prior Art Database

Preserving Office Systems/2 Dialog Coordinate Information during Language Translation

IP.com Disclosure Number: IPCOM000117513D
Original Publication Date: 1996-Mar-01
Included in the Prior Art Database: 2005-Mar-31
Document File: 4 page(s) / 120K

Publishing Venue

IBM

Related People

Walters, DA: AUTHOR

Abstract

Disclosed is a method of using an IBM language translation product, TranslationManager/2 (TM/2), to more efficiently translate OS/2* Presentation Manager (PM) resource files. Translatable text can currently be saved in TM/2's Translation Memory (TM) files when the text translation is performed, and can automatically be retrieved from this file when a new version of the resource file is processed. This enhanced processing method will also save the associated dialog coordinate values in the same TM/2 translation memory file, and will automatically retrieve these values when a new version of the resource file is processed.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 38% of the total text.

Preserving Office Systems/2 Dialog Coordinate Information during
Language Translation

      Disclosed is a method of using an IBM language translation
product, TranslationManager/2 (TM/2), to more efficiently translate
OS/2* Presentation Manager (PM) resource files.  Translatable text
can currently be saved in TM/2's Translation Memory (TM) files when
the text translation is performed, and can automatically be retrieved
from this file when a new version of the resource file is processed.
This enhanced processing method will also save the associated dialog
coordinate values in the same TM/2 translation memory file, and will
automatically retrieve these values when a new version of the
resource file is processed.

      In order for the dialog's coordinate information to be used
within the TM file concept, the original coordinate values (source
segment) and modified coordinate values (target segment) must be
saved in the TM file during the translation process.  Therefore, when
the translator initially translates a window within the TM/2
environment and changes the coordinate values for a resource file
control, the translation editor being used must save this coordinate
information in the current TM file.  This TM entry must be structured
as follows in order to create a unique TM entry for every set of
coordinates:
  1.  Source segment.  This part will contain the following items
       concatenated together, ensuring that each TM entry is unique.
      a.  File name.  The name of the resource file.
      b.  Dialog name.  The name of the dialog section within the
           resource file.
      c.  Control ID.  The control identifier value of the PM control
           within the dialog section.  Each control within a dialog
           section must have a numeric value (or a symbolic name
which
           is eventually resolved to a numeric value) by which the
code
           can access the control.
      d.  Original translatable text (before any translation) for
this
           control.  Since more than one control within a dialog can
           have the same ID value, including the translatable text
           increases the uniqueness of this TM entry.
      e.  Original coordinate values.  This will consist of the four
           coordinate values concatenated together.
  2.  Target segment.
      a.  Target coordinate values.  This will consist of the four
           coordinate values concatenated together.

      Once a TM entry has been created for a resource file control,
the editor must update this TM entry whenever the translator changes
any of the coordinate values for that control.  This will ensure that
the TM file is up-to-date and matches the information in the original
English and translated resource files.

      For example, a dialog definition within an O...