Browse Prior Art Database

Validating OS/2 Message Files after Language Translation

IP.com Disclosure Number: IPCOM000116354D
Original Publication Date: 1995-Sep-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 4 page(s) / 108K

Publishing Venue

IBM

Related People

Snyder, JN: AUTHOR [+2]

Abstract

An OS/2* program is disclosed which will aid in the identification of translator introduced problems into OS/2 message source as early in the translation process as possible, but definitely before the message source is compiled. Using this method, a translator can verify that no message control information has been modified during the language translation process, that the message source is compilable, and that there will be no functional problems when the product uses these translated messages.

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

Validating OS/2 Message Files after Language Translation

      An OS/2* program is disclosed which will aid in the
identification of translator introduced problems into OS/2 message
source as early in the translation process as possible, but
definitely before the message source is compiled.  Using this method,
a translator can verify that no message control information has been
modified during the language translation process, that the message
source is compilable, and that there will be no functional problems
when the product uses these translated messages.

      Translatable text is defined as the words, phrases, and
sentences in the OS/2 message source files which are presented to the
product's end user.  The text is typically translated into European
and Asian languages for National Language Versions (NLV) of the
product.  Non-translatable text is defined as the control information
in the OS/2 message source files that links the translatable text to
the program code or affects the presentation of the text, such as
replacement variables.

      The program is passed the name of the file containing the
translated message source and the name of the corresponding master
file containing the before-translation message source.  The following
is performed in order to validate the contents of the translated
message file:
  o  The master source file will be opened and each record processed.
      The contents of each non-comment record will be analyzed and
      control information which is required for the validation will
be
      extracted and written to a temporary work file.  In other
words,
      the translatable message text is stripped from the master
source
      file and only the control information is saved in the temporary
      work file.  Control information includes:
     -  The message component identifier (identifies the first three
         characters for all of the message identifiers within this
file).
     -  The message identifier for each message.
     -  The message type for each message.
     -  An indication whether the message has translatable text or
not.
     -  The replacement variables used within the message text.

For example, if the OS/2 message source was:
  ; Comment information record
  ABC
  ABC0001H: Translatable text for message number 1.
  ABC0002?:
  ABC0003I: Translatable text with %1 and %3 replacement variables
             imbedded in the message text.
  ABC0004W: Translatable text for a warning type message.

The information stored in the temporary work file would be:
  ABC;
  ABC0001H:;TEXT;
  ABC0002?:;
  ABC0003I:;TEXT; 1 3
  ABC0004W:;TEXT;
  o  Once the master source file has been analyzed, the translated
      source file will be opened and each record processed.  The
      contents of each record will be analyzed and the same type of
      control information which was extra...