Computer graphics processing and selective visual display system – Display driving control circuitry – Controlling the condition of display elements
Reexamination Certificate
1998-08-14
2001-06-26
dela Torre, Crescelle N. (Department: 2173)
Computer graphics processing and selective visual display system
Display driving control circuitry
Controlling the condition of display elements
C709S241000, C704S008000
Reexamination Certificate
active
06252589
ABSTRACT:
TECHNICAL FIELD
The present invention generally relates to operating systems and more particularly to operating systems that provide an efficient mechanism for switching the user-interface language.
BACKGROUND OF THE INVENTION
A resource is binary data or non binary data, e.g., a text file. In Windows NT® and all other O/S of the Windows® family, resources are binary data Resource data can reside in the executable file of an application, so the executable file is a binary file with code and resource data in it. Processes defined by the code can use the resources in their own binary executable files or other executable files. Resources used by such processes may also reside in resource-only files, for example, resource-only dynamic link libraries (DLLS). A resource may be either standard or user-defined. The data in a standard resource describes an icon, cursor, menu, dialog box, bitmap, enhanced metafile, font, accelerator table, message-table entry, string-table entry, or version. A user-defined resource contains any data required by a specific application. The resources required by operating system processes may be handled in various different ways. Many of these resources include words, symbols, formatting data, etc. that are language-specific. Usually, a particular language is determined by the operating system installation package chosen by the user. If the language of the software is English, only the English language-specific resources will be installed with the operating system. This is convenient because of the large quantity of language-specific resources that would have to be copied on the hard-disk to cover all languages.
Providing a single language for the operating system to support is also convenient because it allows resources to be efficiently loaded and unloaded into and from memory as the need arises. Far too many resources exist for all to reside in memory at all times. To manage the loading and unloading of resources so that resources do not unnecessarily occupy memory when not required, the code that generates the processes requiring the resources and the resources peculiar to the process may be incorporated in the same binary files. When a process is invoked, a binary file containing the code for the process, and the attendant resources, may be loaded into memory or otherwise made accessible to the process. When the process is terminated, the resource and code sections of such a file are unloaded from memory or otherwise made in-accessible. These binary files can be executable programs, dynamic link libraries (DLLs), device drivers, etc. If they were bloated with all the alternative language resources, an excessive amount of memory would be required.
An example of how one operating system handles such resources is as follows. First, a resource finder, an operating system function, is employed to create a handle to the specified resource's info block. A process requiring a resource sends the finder a resource module handle and the resource name, type, and optionally, a language ID. The latter specifies a language specific resource in the resources defined by the resource module handle. The finder returns a handle to the specified resource's info block and the process can call a resource loader to place the resource in memory. The process gives the resource handle and the resource module handle to the resource loader, which places the resource in memory and returns a handle to the memory block containing the resource. The resource is then available to the process. The operating system may then use other devices to free the memory after the process loading it into memory no longer needs it, is terminated, or if other conditions require it.
The above is only one type of resource access facility in an example operating system. Other mechanisms may make resources available in other ways, such as by placing text messages in an output buffer, immediately loading and returning a handle to resource data in a single function call, etc. The common feature of these mechanisms is that they find a resource either in memory or in a disk file or other storage system and make the resource available to the process that requires it. This may involve loading a file from disk into memory or just providing access to the resource by providing a handle or some other device. The file (device, or channel) containing the resource may be in the same file as the code defining the requesting process or another file. The other file could contain code or be a resource-only file. A process may not need explicitly to unload a resource it no longer needs.
With the low cost of disk storage, it may be desirable in some instances for the same installation of an operating system to provide, transparently to the user, appropriate resources for a number of languages. This would allow users of various tongues to share the same computer. The user would log on, select a desired language, and use the computer, thereafter seeing all resource-based operating system features in the chosen language. However, for an operating system built around the above resource management regimes, the options available to modify the operating system to accommodate selectable languages appear quite problematic, as discussed below.
To provide multilingual support, one option might be to provide a different set of binary files for each language. Considering there might be on the order of a thousand binary files containing language-specific resources in an complex operating system and that it might be desired to support many different languages, the number of binary files to be installed would be large indeed. In addition to the labor required to provide for the selection of a language by the user, the redundancy in the resulting mass of files would be tremendous because all language-non-specific resources would be duplicated for each language supported. Not only would the language-non-specific resource require duplication, but also all the code sections.
Another option might be to install the operating system binary files anew, each time a new user requiring a different language logged on. This option is unattractive because it would take a great deal of time.
Still another option might be to provide the different language-specific resources in each binary file. This would eliminate the redundancy of the first option since each binary file would only add language-specific resources. However, this option would require recoding of each binary file, so it also is not an elegant option. Something similar to this is currently done on a very limited basis. Some binary files contain alternate resources, each being preferred depending on the language or country of the user. The code sections of these binary files define processes that address a different resource based on a “guess” as to the preferred language of resource. This guess is made based on the settings of some system parameter, for example, which date format has been selected. So, for example, if a Russian style of date is selected, the resources tagged as Russian might be loaded.
There is at least one type of operating system that now provides for language selection on a limited basis. This operating system provides separate text files for each language. When a process requires a text file resource in a particular language, the operating system addresses the appropriate file. The user can select his default language of choice through a system variable.
As mentioned briefly, at least one current operating system (Windows®) provides some support for the creation of language-specific libraries, for example text messages. A system variable is defined indicating the locale (Note, the locale of a system is not a language setting. Locale is a mixture of language and location) of the operating system installation and this variable can be used by the applications running on the operating system to format messages specifically for the current language. This requires, however, that the process (the application) identify precisely the appropriate language resource and
Miller Edward S.
Rettig Bjorn C.
Wilson Gregory
Xu Shan
Banner & Witcoff , Ltd.
dela Torre Crescelle N.
Microsoft Corporation
LandOfFree
Multilingual user interface for an operating system does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Multilingual user interface for an operating system, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Multilingual user interface for an operating system will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2461991