DOC

Readme (1)

By Diana Reynolds,2014-09-07 15:32
8 views 0
Readme (1)

     AppLocale - Readme File

     April 2003

     ? Copyright Microsoft Corporation, 2003

    This document contains important, late-breaking information about AppLocale. Before installing AppLocale, please review this entire document. It contains critical information to ensure proper installation and use of the product.

TABLE OF CONTENTS

    1.0 What is AppLocale

    2.0 Common User Scenarios

    3.0 System Requirements

    4.0 How to Use AppLocale

    4.1 AppLocale Setup

    4.2 Adding/Removing Applications with AppLocale

    4.3 Launching Applications with AppLocale

    5.0 Known Issues

    6.0 Tested Applications

1.0 What is AppLocale

    Unicode based platforms, such as Windows XP, emulate the language environment required to run non-Unicode applications by internally converting application's non-Unicode text data to Unicode using a system-wide variable commonly called the system local (or language for non-Unicode applications). The language of the

    non-Unicode applications should be of the same script or family as the one defined by the system locale. Failing to meet this condition results in display of garbage characters in the UI of the application.

This approach has few usability limitations:

    - Only an administrator has the ability of setting the system locale value.

    - Setting the system locale requires a system reboot.

    - Only one system locale can be set at a time.

    AppLocale (or Application Locale) is a temporary solution to these limitations caused by non-Unicode applications running on the Unicode (UTF-16) based Windows XP. AppLocale detects the language of the legacy application and simulates a corresponding system locale for code-page to/from Unicode conversions.

IMPORTANT NOTES:

    - If you frequently use non-Unicode applications in a given script (or set of languages), it is strongly recommended to set your system locale variable to the language of the target

    application and not to use AppLocale.

    - Application developers should not consider AppLocale as an alternative to migrate their product to Unicode. Today, with Microsoft Layer for Unicode (MSLU), creating pure Unicode applications that can also be deployed on non-Unicode platforms -- such as Windows 98 -- has been made possible.

2.0 Common User Scenarios

    2.1 A user is running the English version of Windows XP with the system locale set to

    English-US (Windows codepage 1252). This user wants to run a popular Japanese application that is code-page based. In order to run this app flawlessly in Windows XP, the user needs to set the system locale to Japanese (Windows cp 932) and reboot the machine.

    Two restrictions: the user might not be an administrator to force this setting change; and/or the user might not want to force a reboot.

    AppLocale can be an attractive workaround in this scenario. The user does not need to be an administrator and no reboot is necessary.

    2.2 An educational center in Israel has all its machines running localized Hebrew versions of Windows XP with their system locale set to Hebrew (Windows codepage 1255). This

    allows even non-Unicode Hebrew applications to run properly. But this educational center also offers Russian courses that use a legacy Russian application (required cp 1251). This Russian application cannot run unless the system locale of the target machines is changed

    to Russian and a reboot is forced. Keep in mind that with this new configuration, existing Hebrew legacy applications will stop functioning properly.

    AppLocale can be an attractive workaround in this scenario. The system locale does not need to be changed to run the Russian application, thus allowing the user to still run all of his Hebrew legacy applications as well.

3.0 System Requirements

    AppLocale is based on the new application compatibility technology introduced in Windows XP. It can only be installed on Windows XP (Home or Pro) or Windows 2003 Server. Please note that AppLocale setup requires administrator rights to the system since some system component files are being installed.

4.0 How To Use AppLocale

4.1 AppLocale Setup

    The AppLocale setup program installs the following files on your system under %SystemRoot%\AppPatch directory:

- readme.rtf This file

    - apploc.exe The AppLocale applet used to launch the target application - alres***.dll The localized resource files for the AppLocale applet

    - alLayer.dll AppLocale specific application compatibility engine

    - .Custom\{deb7008b-681e-4a4a-8aae-cc833e8216ce}.sdb

     AppLocale engine application database

The AppLocale setup program also installs a shortcut to the AppLocale wizard and to this

    readme file under: Start ? All Programs ? Microsoft AppLocale

4.2 Adding/Removing Applications with AppLocale

    Launch the AppLocale wizard accessible from Start ? All Programs ? Microsoft

    AppLocale. On the second page of the wizard entitled Locale The Application, select Add

    or remove program option.

To proceed, click on the Next button.

    On the page tilted Detect The Language, select the language of the target application that you wish to install or uninstall.

To proceed, click on the Next button and then click on the Finish button.

AppLocale will then launch the Windows Add or Remove Programs utility in a language-

    compatibility mode that matches the language of your target language.

4.3 Launching Applications with AppLocale

    Launch the AppLocale wizard accessible from Start ? All Programs ? Microsoft

    AppLocale. On the second page of the wizard entitled Locate The Application, select Add

    or remove program option and proceed by clicking the Next button. On the second page

    of the wizard entitled Locale The Application, select Launch an application option. You

    can then either use the Browse button to locate the target application or just drag and drop the applications icon on top of the current wizard page. If you wish to execute the target application with command line options, specify those options in the Arguments field.

To proceed, click on the Next button.

    On the page tilted Detect The Language, select the language of the target application that you wish to execute.

To proceed, click on the Next button.

    On the final page of the wizard, users will experience one of the following three scenarios:

    - If the language support for the target application is not installed on your machine, AppLocale will provide a link to learn how to install the language support that is required to run that application.

    - If the language of the target application can already be accommodated by your system

    locale, AppLocale will simply launch the desired application without providing any compatibility support.

    - If compatibility support is required, AppLocale will launch the target application in compatibility mode. It also offers you the possibility of creating a shortcut for this application for express execution in future. The shortcut will be created under the Start ?

    All Programs ? Microsoft AppLocale menu.

To complete the process, click on the Finish button.

5.0 Known Issues

    Because of the nature of AppLocale’s implementation and because each application is unique in the way it handles text data, AppLocale might cause application-specific side-effects and limitations that the user would not experience once the "system locale" is properly set. Some of these application-specific side-effects and limitations may be:

    - Setup programs: for some for setup programs that require a reboot, it is strongly suggested to properly set the system locale to match the language of the target application

    during the installation.

    - Server application: non-Unicode server applications have not been tested and are not supported by AppLocale.

- 16-bit application are not supported by AppLocale.

    - Input Method Editors (IME) might not properly function in some private or owner drawn edit controls.

    - File system support: creating localized file names or installing applications in localized

folder names that do not match your system locale might result in broken functionality.

    - Even after applying AppLocale some of the application’s user interface might not render properly. This should not cause any functionality breaking and it is related to the application’s specific way of handling non-Unicode data.

    - Running Unicode applications or applications that handle their own character encoding conversions (e.g. Internet Explorer) in AppLocale compatibility mode might result in unexpected results and breaking functionality.

6.0 Tested Applications

    Extensive testing has been conducted on a large number of popular localized applications with AppLocale. Below is a summary of these applications and their level of support provided by AppLocale.

    6.1 Applications that are fully functional and represent a minimum of breaking functionality when launched with AppLocale:

Adobe Acrobat 5.0

    Adobe ImageREady 3.0

    CorelDRAW 9

    Flash Macromedia 5.0

    FrontPage 2002

    JinShanKuaiYi 2002

    Outlook 2000

    Outlook Express

    Outlook XP

    Pagemaker 6.5 (needs the matching system locale for installation)

    PhotoImpact 7

    PhotoShop 7.0 (needs the matching system locale for installation)

    WordPerfect suite 8.0

    6.2 Applications that are mostly functional but might have some minor breaking functionality when launched with AppLocale:

Abba Bushot

    Adobe Acrobat Reader 5.0

    Atena Shoku Nin 2001

    AutoCAD2000LT

    Babylon 4.5

    ChaoJiJieBa 3000

    Daum Messenger 2.7

    DongFangKuaiChe XP

    Excel XP

    Fude-Mame 13

    Genie messenger 4

HaiZhiLanGe - The legend of Heroes V

    Hanako 11 (Special Pack) Hancom Office 2003

    HunMinJungEum Office 2000i HunMinJungEum Office XP Ichitaro 12

    Illustrator 10

    Internet Mo Yakuse!! Goma Bilingual 6 (needs the matching system locale for

    installation)

    JinShanCiBa 2003

    JinShanDuBa 2003

    KV3000 ShaDuWang

    Menahel 4.5

    Money2002 Deluxe

    Namo WebEditor 5.1

    Namo WebEditor 5.01 Nature IME 6.5

    Norton AntiVirus 2002 OASYS V8

    PC-DIC 9

    PhotoDraw 2000

    PhotoExplorer 7

    PhotoExpress 4.0

    PhotoImpact 7

    Picture It ! 2000

    PowerDVD 3

    PowerPoint XP

    Project 2002

    Publisher 2000 (Office 2000 SR1)

    RealPlayer 8

    Rising 2003

    VedioStudio 6

    Visio 2002

    WinZip 8.1

    Word XP

    Works 2001 (needs the matching system locale for installation)

    WPS Office 2000

    Xiao Ao Jiang Hu

    ZhiNengKuangPin

Report this document

For any questions or suggestions please email
cust-service@docsford.com