Technical FAQs

SCRIPTMAGIC Windows
SCRIPTMAGIC Web

SCRIPTMAGIC Windows

1. Which versions of Windows are supported?

Windows 2000 (all Service packs), Windows XP (all Service packs), Windows Vista.

2. Does ScriptMagic support Windows 98?

Yes, but now it is considered as a legacy platform with phasing out support.

3. Which back-end database servers are supported?

ScriptMagic works with the front-end of you application, and hence supports any back-end database server.

4. How are the strings captured for translation?

Do we have to provide a string table?

ScriptMagic for Windows has "String Logging" option, which captures all the strings which are displayed on the screen (or printed on printer) in the source language. String tables are not necessary.

5. How do you handle "in-line-coding”?

Since "String Logging" captures all the strings which get displayed, this includes the strings in lined and embedded in the code.

6. Does this mean that one has to run through all the screens and reports of

the application? For large applications, would this take a lot of time?

Yes, navigating through all screens and reports is necessary to ensure that all the phrases get captured. This is a one time effort and requires at the most a few days even for large applications.

7. Does ScriptMagic support ANSI?

Yes. For languages not directly supported on Windows, ANSI fonts and keyboard drivers are also supported. Indian languages in ANSI mode are good example of this. Arabic is also supported in ANIS mode.

8. Does ScriptMagic support Unicode?

Yes. For this, the operating system and the application should be Unicode compliant.

9. How does ScriptMagic handle input?

ScriptMagic supports the input in ANSI as well as Unicode as long as the application supports the same, and can also provide keyboard driver if the operating system does not directly support the target language or the default keyboard map is not desirable.

10. What is stored in the database?

The data entered through the front-end gets stored in the database. Hence, if the application is ANSI, the data storage will be ANSI. For Unicode applications, data storage will be Unicode.

11. What happens when I add or modify forms /screens / reports in

my application? Do I go through the entire capturing process?

If the phrases used in the new forms / screens / reports already exist in the dictionary, they will get converted automatically. Only those phrases get captured which are not converted using the "String Logging" facility of ScriptMagic, and added to the phrase list. If you know which forms / screens / reports have been added or modified, you need to navigate only through these.

12. Do we need to buy or install any other language components viz.

keyboard drivers, fonts, etc.?

No. ScriptMagic handles all the language related issues including fonts and keyboard drivers.

13. For some languages, how do you tackle the issue of inadequate

space for fitting the labels?

Dictionary editor provides feedback during translation if the translated text fits within the available space. If not, appropriate abbreviations approved by the client can be used for this purpose.

14. What is the average size of the installable?

Depending upon the configuration and dictionary size, the installer size ranges between 2-5 MB.

15. What is the memory footprint?

Depending upon the configuration and dictionary size, ScriptMagic requires 2-5 MB or hard-disk space and similar space on RAM.

16. How can I deploy ScritpMagic?

ScriptMagic is supplied as Setup Application or Windws msi.

17. Can there be just one set up to install my application and ScriptMagic?

Yes. There are 2 options. Option 1: Your set can call out setup for installation Option 2: We can provide our files for inclusion in your setup

18. Can we integrate ScriptMagic with my application?

Yes.

19. Do we need to install anything on the server side?

No.

20. Will you provide the source code for us to modify in case we require it?

ScriptMagic is supported during warranty period and subsequently through AMC. The source code of ScriptMagic cannot be made available. However, source code can be kept in escrow for large contracts..

21. How are the newer platforms viz. Versions

of OS/patches/releases supported?

ScriptMagic upgrades are available from time to time addressing the issues arising out of newer versions of OS / patches / releases. These are made available at as part of warranty or AMC.

22. Does ScriptMagic work on Linux Desktop?

No. However, this support can be provided for large volume.

23. Can ScriptMagic convert the image or text embedded in Images?

Yes. A dictionary of images is used for this purpose.

24. What is performance degradation?

Average CPU usage of ScriptMagic Windows is less than 1%. The speed of conversion is such that the user does not realize that ScriptMagic is carrying out on line conversion.

25. What is the CPU and memory over head for using ScriptMagic?

The average incremental CPU usage for desktop version of ScriptMagic is below 1%. The physical memory used by ScriptMagic depends largely on the dictionary size. For a typical business application having about 500 screens & 50 reports, the dictionary may be about 10,000 phrases (actual number of phrases depends on the specific application): with this, total physical memory used is about 2-3 MB.

SCRIPTMAGIC Web

1. Which Web Servers are supported?

IIS 5.x,/6.0, Apache 2.x, IBM HTTP Server.

2. Which Operating Systems are supported?

Windows 200x Server, Linux and Linux clone, IBM AIX, HP UX etc.

3. Does ScriptMagic support Application servers like WebLogic, WebSphere?

Yes, through Web Server i.e. with Apache or IBM HTTP Server.

4. Which programming languages are supported?

ScriptMagic predominantly works with the Microsoft Web Applications (ASP, .NET) and Java (JSP). In general any programming language generating html format is supported.

5. How Does ScriptMagic handle JavaScript?

Yes.

6. Which back-end database servers are supported?

ScriptMagic works with the Web Server, and hence supports any backend database server.

7. Which client Operating Systems are supported?

ScriptMagic has no dependence on client OS, but the client OS should support the target language, encoding (Unicode) and rendering (wherever applicable).

8. Which Client Browsers are supported?

ScriptMagic has no dependence on Client Browser, but the Client Browser should support the target language, encoding (Unicode) and rendering (wherever applicable).

9. How Does ScriptMagic handle JavaScript?

Yes.

10. How are the strings captured for translation?

Do we have to provide a string table?

ScriptMagic for Web has "String Logging" option, which captures all the strings which are part of web page in the source language. String tables are not necessary.

11. How do you handle "in-line-coding”?

Since "String Logging" captures all the strings which are present in the web page, this includes the strings in lined and embedded in the code.

12. Does this mean that one has to run through all the screens and

reports of the application? For large applications, would this take a lot of time?

Yes, navigating through all screens and reports is necessary to ensure that all the phrases get captured. This is a one time effort and requires at the most a few days even for large applications.

13. Does ScriptMagic support ANSI?

14. Does ScriptMagic support Unicode?

Yes. For this, the client operating system and the application should be Unicode compliant.

15. What is stored in the database?

The data entered through the front-end gets stored in the database. Hence, if the application is ANSI, the data storage will be ANSI. For Unicode applications, data storage will be Unicode.

16. What happens when I add or modify forms /screens /

reports in my application? Do I go through the entire capturing process?

17. Do we need to buy or install any other language components viz.

keyboard drivers, fonts, etc.?

No. ScriptMagic handles all the language related issues including fonts.

18. For some languages, how do you tackle

the issue of inadequate space for fitting the labels?

Dictionary editor provides feedback during translation if the translated text fits within the available space. If not, appropriate abbreviations approved by the client can be used for this purpose.

19. What is the average size of the installable?

Depending upon the configuration and dictionary size, the installer size ranges between 2-5 MB.

20. What is the memory footprint?

Depending upon the configuration and dictionary size, ScriptMagic requires 2-5 MB or hard-disk space and similar space on RAM.

21. How can I deploy ScriptMagic?

ScriptMagic is supplied as Setup application or Windws msi.

22. Can we integrate ScriptMagic with my application?

Yes.

23. Do we need to install anything on the client side?

No.

24. Does ScriptMagic support multiple languages for a web application?

Yes.

25. Will you provide the source code for us to modify in case we require it?

ScriptMagic is supported during warranty period and subsequently through AMC. The source code of ScriptMagic cannot be made available. However, source code can be kept in escrow for large contracts.

26. How are the newer platforms viz.

Versions of OS/patches/releases supported?

ScriptMagic upgrades are available from time to time addressing the issues arising out of newer versions of OS / patches / releases. These are made available at as part of warranty or AMC.

27. Can ScriptMagic convert the image or text embedded in Images?

Yes. A dictionary of images is used for this purpose.

28. What is performance degradation?

Average CPU usage of ScriptMagic Web is less than 5%. The speed of conversion is such that there is hardly any incremental latency time due to use of ScriptMagic.

29. What is the CPU and memory over head for using ScriptMagic ?

The average incremental CPU usage for Web version of ScriptMagic is below 5%. The physical memory used by ScriptMagic depends largely on the dictionary size. For a typical business application having about 500 screens & 50 reports, the dictionary may be about 10,000 phrases (actual number of phrases depends on the specific application): with this, total physical memory used is about 2-3 MB.