User:Netfriend

Interlingual SQL is a system for transforming a single-language database or RDMS into an Interlingual database providing full access to multiple simultaneous textual language translations of the internal transactions. The Interlingual SQL application and service converts existing data structures, translates text into supported languages and provides ongoing translation and database structure monitoring.

The resulting databases are deemed truly interlingual, having the ability to represent the same data simultaneously in various textual languages and/or character sets regardless of the language in which the individual data transactions were initially created. This is contrasted to a database being multi-lingual or multi-language, having the ability to store data in multiple textual languages and character sets but only presenting the data back in the language and character set in which it was initially stored.

Interlingual SQL is the property of a single for-profit firm, the United States based company Net Foundation which also holds the copyright to its codebase. The software and service are currently in beta version 1.1 as of February 2009, and the project's source code is planned to be made available under proprietary agreements.

Uses
Interlingual SQL is desirable for any business or software developer that needs to expand their new or existing DBMS-running software to support more than one textual language in a truly interlingual manner without needing to invest in database redesign and translating engines. Interlingual SQL both transforms databases into a structure that efficiently supports Interlingual data and then converts the translatable portions of each data element into the desired additional languages.

This approach enables applications developers to write applications which can switch between textual languages from within software applications by simply calling one of the newly created views of the data in place of existing database views or database table calls. These interlingual views are identical in structure to pre-transformed views except that the data returned is in the textual language identified in the view naming convention.

After the initial conversion phase Interlingual SQL continues to provide near real-time replication and translation of new records and modified fields using their proprietary change tracking algorithms.

Platforms and interfaces
Interlingual SQL is an ASP.NET application written Visual Basic and connects to any DBMS that supports standard SQL syntax. The application installs on Microsoft XP or Vista servers with the support engines running as a Windows Service.

Administration of Interlingual SQL is done using a supplied GUI administration tool. A locally installed database stores a translation matrix which is updated from a centralized master translation matrix.

Features
The following features are part of the Interlingual SQL application and service:

Interlingual SQL Software

•  Database Analyzer

•  Table/Field Configuration Tool

•  Translation Context Tool

•  Database Re-Designer

•  Translation Engine

Interlingual SQL Service

•  Translation Engine

•  Context Modification Tool

•  Database Change Alert

History
As of February 2009 Interlingual SQL is currently in beta release version 1.1 with an open public beta release planned with beta release version 2.0 tentatively scheduled for 2Q 2009. Companies or individuals interested in participating in the open-public beta release can register for email notification of its availability.

Support and Licensing
Net Foundation licenses and supports Interlingual SQL. Registered users have access to a support website on which they can access product and service documents, FAQs, tips mailing lists, their active user forum, and can open direct support cases.

Interlingual SQL is currently available as a free beta product for the initial limited testers and will be available as a free beta product during the open-public beta version 2.0 release. Production pricing is expected to be based on user database size and the number of CPUs on the server hosting the service application.

Issues
None reported.

Criticisms
Translation

Machine-based translation processes by themselves are inadequate in providing totally satisfactory textual language translation for many reasons. (1.) Many words, especially proper nouns, simply do not have correlating textual translation strings in all other languages and character sets. International citizens will often adopt different names in different languages simply because there is not a direct meaningful translation. (2.) Many languages including many idioms or phrases that have implicit meanings that are at best lost, and at worst comical or insulting if translated literally. (3.) The use of the same word (adverb, adjective, verb, etc.) may be represented in many other words in other languages. (4.) Many languages such as American English routinely embrace the use of acronyms and abbreviations which do not have direct equivalents in all other languages. Even a common word such as "email" will not directly translate into languages.

Because Interlingual SQL provides machine-based translation, the results will only be acceptable with end-user linguistic staff support. Interlingual SQL provides an interface through which linguistic support staff can define and monitor translation based on context, column definitions, and even to the level of single-record instructions.

Interlingual SQL does not work well with all types of applications. Transaction-intensive applications such as banking, CRM and ERP application work well because of the relatively consistent manner of the data to be translated. Applications managing large quantities of text documents such as blogs or newspaper applications do not work well because of the higher probability that complete textual translation will not be acceptable without significant linguistic staff efforts.

Latency

Interlingual SQL does not immediately translate records into all supported languages. Availability of new and changed transaction data is dependent on the speed and number of Interlingual SQL engines managing the database. While new records usually made available to all supported languages within a few seconds of them being created, translation of all of the content with in new or modified records may take a few minutes or even up to a few hours, depending on transaction volume. Until the final translation is performed, the original language (and a language tag) is stored and displayed in the fields yet to be translated. In some instances, the final translation may be dependent on end-user linguistic staff maintenance.