Browse Prior Art Database

Extracting the Translatable Text from an Office Systems/2 Program Integrated Information Source File

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

Publishing Venue

IBM

Related People

Snyder, JN: AUTHOR [+2]

Abstract

An OS/2* program is disclosed which will remove the translatable text from an ASCII OS/2 text file which contains a specific type of Program Integrated Information (PII). Using this method, the non-translatable text and translatable text can be separated. This allows various types of text analysis to be more efficiently performed on the translatable text, like spelling verification, grammar checking, terminology validation, or proofreading. It also allows various types of verification to be performed on the non-translatable text, like insuring that the non-translatable text has not been modified during the translation process, which could affect the presentation of the text or the function of the product.

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

Extracting the Translatable Text from an Office Systems/2 Program
Integrated Information Source File

      An OS/2* program is disclosed which will remove the
translatable text from an ASCII OS/2 text file which contains a
specific type of Program Integrated Information (PII).  Using this
method, the non-translatable text and translatable text can be
separated.  This allows various types of text analysis to be more
efficiently performed on the translatable text, like spelling
verification, grammar checking, terminology validation, or
proofreading.  It also allows various types of verification to be
performed on the non-translatable text, like insuring that the
non-translatable text has not been modified during the translation
process, which could affect the presentation of the text or the
function of the product.

      Translatable text is defined as the words, phrases, and
sentences in the PII 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
PII files that links the translatable text to the program code or
affects the presentation of the text.  Translatable information for
an OS/2 product is normally coded in one of these well-defined
formats:
  o  Message file source for the Make Message File (MKMSGF) tool from
      the IBM* Developer's Toolkit for OS/2.
  o  Presentation Manager* (PM) resource file source for the Resource
      Compiler (RC) from the IBM Developer's Toolkit for OS/2.
  o  Information Presentation Facility (IPF) source for the IPF
      Compiler from the IBM Developer's Toolkit for OS/2.
  o  X/Open** Portability Guide, version 4 (XPG/4) message catalog
      source for the Generate Catalog (GENCAT) tool.
  o  Window Management System (WMS) message source.
  o  Window Management System (WMS) help source.
  o  Other user-defined formats.

      Each of these formats contain control information in addition
to the translatable text.  The control information must adhere to a
defined syntax which includes of a set of predefined keywords.  This
tool uses these keywords to determine the type of PII information
contained in the file and to locate the translatable and
non-translatable text.

      The program is passed the name of a file to process.  The
following is performed in order to separate the translatable text
from the non-translatable text:
  o  The file extension value (the one to three characters following
      the period in the file name) and the contents of the file will
be
      analyzed to determine the type of PII contained in the file.
  o  If the file contains MKMSGF message source,
     - Each record within the file is read.
     - Comment records (which are not significant) are ignored.
     - If the record contains a message identifier...