CONTENT
CREATION IN INDIAN LANGUAGES
In content creation field there are two types of outputs are required:
The static html pages can be made using the ISM or LEAP series. The major part is the font, which will allow these static pages to display appropriately.
ISM is a keyboard manager application, which can be used with the standard WYSIWYG HTML editors.
LEAP is a word processing application, which can export the documents into HTML format. Whenever content is created using LEAP make sure it is exported as HTM and not cut & paste mechanism.
Note:
In static html pages the data will be stored mostly in ISFOC format.
How to go about making the static HTML pages is explained in Dynamic fonts
Interactive
HTML pages are pages where data is updated on the fly as per a query. Or where
the clients inputs are required say typically filling out a registration form
or writing an e-mail or posting a message and so on. So the Indian Language
components should be there on the clients machine. How to deliver these components
to the clients is what this technology is all about.
Data
is stored in ISCII / ISFOC in a database and depending upon the user’s query
the contents of the page is displayed by retrieving data from the database.
The s/w tools which are required out here are ActiveX controls/ plug-in for
accepting or editing Indian Language data as well as conversion tools which
will allow the data to convert from ISCII to ISFOC. The sets of tools, which
are available with us,
GIST SDK which includes set of ActiveX Controls and which has built-in data conversion methods. (ISCII to ISFOC and reverse). This set of controls also support both monolingual and bilingual inputs. As IE support ActiveX controls this can be straight away used without any changes. In the case of Netscape there is no provision for ActiveX Control support. Hence
iPlugin is required for the same which will help in accepting and editing data in Indian Languages. iPlugin works for both Netscape as well as Internet Explorer. To learn details go to iPlugin
Points
to be kept in mind for data storage
It is always better to store the data in ISCII because converting from ISCII to any font code is easier. Sorting or indexing can be done only in ISCII format not in ISFOC format. ISFOC data occupies more disk space than ISCII. It is approximately 2 times more than ISCII data.
Note: As the tools are available to convert back and forth it is better to store the data in ISCII.
|
|
|