Browse Prior Art Database

Codepage Search

IP.com Disclosure Number: IPCOM000120994D
Original Publication Date: 1991-Jul-01
Included in the Prior Art Database: 2005-Apr-02
Document File: 1 page(s) / 53K

Publishing Venue

IBM

Related People

Weber, OW: AUTHOR

Abstract

This article describes the ability to determine the correct codepage for data without unnecessary intervention from the user. OS/2* users should not have to deal with codepage errors unless every effort has been made by the application to determine the codepage corresponding to a data field. This article describes a new API (Application Programming Interface) which will intervene between the user's request to display DIA-formatted EAs (Extended Attributes) and the actual display of the properties. The new API solves the problem by exhausting all possible ways to determine the correct codepage of the data.

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

Codepage Search

      This article describes the ability to determine the
correct codepage for data without unnecessary intervention from the
user. OS/2* users should not have to deal with codepage errors unless
every effort has been made by the application to determine the
codepage corresponding to a data field. This article describes a new
API (Application Programming Interface) which will intervene between
the user's request to display DIA-formatted EAs (Extended Attributes)
and the actual display of the properties.  The new API solves the
problem by exhausting all possible ways to determine the correct
codepage of the data.

      The solution is to provide an algorithm and a mechanism for
appropriately exhausting all possibilities to retrieve the codepage.
When the request is made to work with file properties, this new API
determines whether or not there is codepage data associated with this
actual instance of this particular property.  For example, if there
are fifty keywords, the new API checks each occurrence for its own
codepage data.  If there is no codepage data for keyword number 25,
for example, this new API then goes into an indexed algorithm,
stepping backwards through all the previous keywords, looking for
appropriate codepage information.  If the codepage is found, then
that codepage value is assumed for the keyword which has its codepage
missing as well.  If the codepage data is still missing, the
algorithm then falls through to check the code...