Term Paper Report: Bachelor of Technology IN Computer Science Engineering (2011-12)

ACCESSING DYNAMIC WEB PAGE IN USER LANGUAGE
TERM PAPER REPORT

submitted
In partial fulfillment of the requirements for The award of the degree of
BACHELOR OF TECHNOLOGY IN COMPUTER SCIENCE ENGINEERING (2011-12)

Submitted By J.DEVI SANTHOSH SHAH N.VAHINI GYAN PANDEY Y8CS249 L9CS365 L9CS361 Y8CS245
KONERU LAKSHMIAH COLLEGE OF ENGINEERING(AUTONOMOUS)

Approved by AICTE, Affiliated to Acharya Nagarjuna University, Accredited by NBA and ISO 9001-2000 certified Green Fields, Vaddeswaram, (P.O), Guntur Dist. A.P, India522502
KONERU LAKSHMAIAH COLLEGE OF ENGINEERING(AUTONOMOUS)
NOVEMBER 2011
KONERU LAKSHMIAH COLLEGE OF ENGINEERING(AUTONOMOUS)

Approved by AICTE, Affiliated to Acharya Nagarjuna University, Accredited by NBA and ISO 9001-2000 certified Green Fields, Vaddeswaram, (P.O), Guntur Dist. A.P, India- 522502
CERTIFICATE
This is to certify that this Term paper report has been presented by J.Devi,Santhosh shah,N.Vahini,Gyan Pandey on 05-11-2011 in partial
fulfillment of the requirements for the award of degree of
Bachelor of
Technology in Computer Science and Engineering Department under the Koneru Lakshmaiah College of Engineering.
STAFF INCHARGE GUIDE
K.V.D Kiran Ch.Jyothsna Devi
HEAD OF DEPARTMENT
Prof. S.Venkateswarlu
ACKNOWLEDGMENT
We take this opportunity to remember and acknowledge the co-operation, good will and support both moral and technical extended by several individuals out of which this project has evolved. We always cherish our association with them. We are greatly elated and thankful to our Head of the Department Prof. S.Venkateswarulu for his enthusiastic assistance and inspiring us all the way and for arranging all the facilities and resources needed for my project. It is with immense pleasure that we would like to express our indebted gratitude to our project guide Ch.Jyothsna Devi who have guided us a lot and encouraged us in every step of research extent. We are also thankful to Dr. K.Rama Krishna, DEAN-Academics and Mr. Dr. K. Rajasekhar Rao, DEAN-Student welfare of our college for their interest in our academic performance. We are very grateful to God for his blessing with which we competed our term paper successfully. We are grateful to our family members for their moral and financial support. about the topic . Her invaluable moral support and guidance throughout the project helped us to a greater
Finally, our verbal abilities limit the expression of heartful feelings towards our non-teaching staff and friends who had directly or indirectly helped and supported us in completing project in time.
Table of Contents 1. Introduction 1.1 1.2

1.3 1.4
Page No
Terminology Definitions Theoretical foundations related to the problem area Need for investigating the problem area Problem definition Scope 1.6.1 Literature survey
1.6.2
1.5 1.6
Macro level problem definition
1.6.3 Comparative analysis 1.6.4 Presentation on solution domain 1.6.5 Investigation and presentation
1.6.6 Conclusions 1.7 1.8 1.9 2.0 3.0 4.0 5.0 6.0 Methodology Limitations Conclusions
Literature survey at micro level Comparative analysis Investigation of problem area and Findings Comparative analysis for proof of findings Conclusions
References Appendix
Abstract
Today and Tomorrow , the most advanced technology is Information Technology (IT) . But, the applications of IT are being limited to only those who are familiar in English. It is not useful for those who are unknown in digital literacy. In an increasingly interconnected world, the interactions among devices, systems, and people are growing rapidly. At present the repositories in Internet are mainly in English, as a consequence users unfamiliar in English are not able to get benefits from Internet. Although many enterprises like Google have addressed this problem by providing translation engines but they have their own limitations. One major limitation is that translation engines fail to translate the dynamic content of the web pages which are written in English in web server database. We address the problem in this work and propose a user friendly interface mechanism through which a user can interact to any web services in Internet. We illustrate the access of Andhra Pradesh State Road Transport Corporation System and interaction with Wikipedia English Website signifying the efficacy of the proposed mechanism as two case studies.
INTRODUCTION
1.1 Terminology 1.2 Definitions
Static Web Page: A static web page (sometimes called a flat page) is a web page that is delivered to the user exactly as stored, in contrast to dynamic web pages which are generated by a web application. Dynamic Web page: A dynamic web page is a kind of web page that has been prepared with fresh information(content and/or layout), for each individual viewing. It is not static because it changes with the time (e.g. news content), the user (e.g. preferences in a login session), the user interaction (e.g. web page game), the context (e.g. parametric customization), or any combination thereof. Client Side Scripting: Client-side scripting to change interface behaviors within a specific web page, in response to mouse or keyboard actions or at specified timing events. In this case the dynamic behavior occurs within the presentation. Server Side Scripting: A program running on the web server (server-side scripting) is used to change the web content on various web pages, or to adjust the sequence of or reload of the web pages. Server responses may be determined by such Conditions as data in a posted HTML form, parameters in the URL, the type of browser being used, the passage of time, or a database or server state. User Language: Any language chosen by user (mother language/required language).
1.3
Theoretical foundations related to the problem area
At present the repositories in Internet are mainly in English, as a consequence users unfamiliar to English are not able to get benefits from Internet. One major limitation is that translation engines fail to translate the dynamic content of the web pages which are written in English in web server database. It is noted that many translation engines which convert web pages from English to Indian languages, have addressed the problem for static content of a web page.
1.4
Need for investigating the problem area

There is explosive growth of ICT and its many applications in education, health,
agriculture etc. are confined to a limited number of privileged people who have both language and digital literacy. At present the repositories in Internet are mainly in English, as a consequence users unfamiliar to English are not able to get benefits from internet. A dynamic web page is a page that changes based on the user. It responds to the user's needs, and provides relevant information to meet them, by accessing information in a connected database. A dynamic web page allows users to go beyond reading text and looking at graphics. It allows for an interactive experience, with the user being in control of the information he views. Thus the dynamic web pages maintain up to date information and provides a two - way interaction with server and can retrieve results. This problem had been addressed and then we can access static web page in any language required by user with the help of Google Translate. But , by static web pages user cant give input to the web page in his own language . To overcome , this paper has been proposed to access dynamic web page in user language.
1.5
Problem definition
Although many enterprises like Google have addressed the problem of accessing dynamic web page in user required language i.e by providing translation engines to translate the content present in the web page but having some limitations. It is unable with Google translate to translate user input also in the user required language. It can be made possible with the help of virtual keyboard and some translation engines.
1.6 Scope
1.6.1 Literature Survey:
According to UNESCO report [1], about 64% of population of the globe is English illiterate. The percentage is more in developing countries like India, China, and Pakistan etc. where nearly 76% people are English illiterate. It is obvious that these people are deprived from the advantages of Internet because majority of web pages (nearly 45%) are in English . Hence, there is a need to bridge the digital divide exists since beginning of IT revolution i.e. the last decade of the previous century. Lets discuss about challenges ahead to access the Internet repository. In present scenario, users who are familiar with Indian languages and less conversant with English face difficulties in accessing the web services. The traditional web services (like Indian Railways) generate dynamic web page with respect to query given by the user in English language as they maintain their database in the same language. Thus, the services are lacking of support to users query in Indian languages and as a result, unable to produce dynamic web pages in any language excluding English.
1.6.2
Macro level problem Definition

In present scenario, users who are familiar with Indian languages and less conversant with
English face difficulties in accessing the web services. The traditional web services (like Indian Railways) generate dynamic web page with respect to query given by the user in English language as they maintain their database in the same language. Thus, the services are lacking of support to
users query in Indian languages and as a result, unable to produce dynamic web pages in any language excluding English. It may be also noted that many translation engines which convert web pages from English to Indian languages, have addressed the problem for static content of a web page. For dynamic web page content, the success rate is very poor. This specific challenge has been addressed in this work. We propose a mechanism, called Two-way Interaction which enables a user to interact with the dynamic web pages in users mother language only and the results returned during interactions are displayed in same language.
1.6.3 Comparative Analysis

Comparison between accessing of static and dynamic web page: A static website is one that is written in HTML only. Each page is a separate document and there is no database that it draws on. What this means functionally is that the only way to edit the site is to go into each page and edit the HTML - so you'd either have to do it yourself using a web page editor or we can edit the site each time you wanted something changed. A dynamic website is written using more complex code and can do a lot more. For instance, we can make an area where you can log in and change various parts of the website, such as adding information or products or changing existing products. Ecommerce websites, news websites are some examples of dynamic websites. This is because each page is constructed based on the information in a database, and the information in that database can be changed via another interface. Dynamic websites can reduce ongoing maintenance costs if you don't want to change things yourself with a web page editor or with the HTML. They usually cost more to develop, as they require more complex coding and a content management utility needs to be developed to help you manage your website information. Another benefit of dynamic websites is that they allow you to change only the content of the website and not the design, so you will not be able to accidentally break the visual style of
the website. They have other benefits when websites start to get very large, as they make data management much more efficient and your website more expandable. Many clients do a combination, having some dynamic areas such as a product catalog where they have to change information or pictures regularly, and leave other pages such as contact information as static pages.
1.6.4
Presentation on solution domain
The multi-language design paradigm for designing complex systems can be summarized as follows (see Fig 1):
Problem domain analysis - analysis, identification and classification of concerns in a problem domain. Solution domain analysis - identification of programming languages and analysis of their capabilities in a solution domain. Selection of languages - mapping of each problem domain concern to the most suitable solution domain language. Implementation - composition of a heterogeneous system from the multi-language components implemented using the selected languages.
1.6.5 Investigation and presentation

We address the problem in this work and propose a user friendly interface mechanism
through which a user can interact to any web services in Internet. It helps the users to access Internet in their day to day life without worrying much about the language web page is originally written. We propose a mechanism, called Two-way Interaction which enables a user to interact with the dynamic web pages in users mother language only and the results returned during interactions are displayed in same language.
1.6.6 Conclusion
Interacting Dynamic Web Portal in local Language plays a great role, as it will minimize the gap between the Internet and user due to language barrier. It helps the users to access Internet in their day to day life without worrying much about the language web page is originally written. This service provides the Internet content to millions of people who might not have good capability to read the web content in English.
1.7 Methodology
The proposed approach to interact with a web service in users language. Let the users language be L. The framework consists of two major components: RTR and IHDD. RTR which performs retrieving, translation and rendering of data present in web page. IHDD which handles input and also dispatches the input and again handover it to the RTR module.
1.8 Limitations
There are some limitations for the current system to which solutions can be provided as a future development: 1. The system is not configured for multi-users language at this time. 2. The Website is not accessible to everyone. It can be deployed on a web server so that everybody who is connected to the Internet can use it. As for other future developments, the following can be done: The user can give input in the form of voice based communication rather than using virtual keyboard. By voice based communication the stress on user can be reduced
2.0 Literature survey at micro level
2.1 Analysis of Multi-Language Design Paradigm:

Introduction to Multi-language design: Design of applications using multiple programming languages has been known for a long time in software engineering. Recent methodological developments in the area are as follows.
Multi-dimensional
separation of concerns focuses on identification and
classification of orthogonal and dependable concerns along multiple dimensions in a domain.

Feature engineering analyzes features across the problem and solution domains.
Scripting.
Meta-programming both aim at the implementation of different design concerns
using multiple design languages or different subsets of the same language.
2.2 Analysis of multi-language design approaches:

After analysis the heterogeneous systems domain, we have identified several approaches for designing multi-language System as follows:
Common files are used to store data that a reused by several software components.
The components have to agree on data formats used and access the data using the input/output mechanisms of the respective programming language.
Remote procedure call (RPC) is used as a software integration technique for
communicating between different components of a distributed heterogeneous system. RPC transmits the parameters of a procedure, executes operations in a different memory space and returns the values. Heterogeneous RPC is executed between components written in different programming languages and using different data representation formats.
Message passing is a method of communication used to send units of information
called "messages" between "sender" and "receiver" components. The components must agree on a common message format, or each component must have a front-
end (or wrapper) that translates a message into one of understandable formats. An example of message passing system is MPI (Message Passing Interface) for parallel computing.
2.3 Standard architecture for web-based applications

This system is designed based on a traditional three-tier architecture used by many web applications. Three-tier architecture includes a presentation layer, business rules/ logic layer, and the data layer. The three-tier architecture is generally used when an effective distributed client/server design is needed that provides
increased performance flexibility maintainability reusability and scalability
The three-tier architecture has three different layers which is a standard one. The three different layers can be defines as follows:
Presentation Layer: It is the top most layer which is used for viewing purpose and interacts with user. Business Layer: It is also known as logic layer as the business logic of the application is present in this layer. Data Layer: This is the bottom layer where original data is stored in database using SQL Queries. From this layer itself the data is retrieved.
Fig: Three tier Standard Architecture
2.4
Static Web Page

A Static web page consists of some HTML code typed directly into a text editor and
saved as a .htm or .html file. It is a web page that is delivered to the user exactly as stored, in contrast to dynamic web pages which are generated by a web application. Static pages are already established and are not drawn up from bits and pieces from a search query. However it takes longer for them to index all the data especially when there are thousands of products and if you have set up products with similar descriptions it can cause duplicate content issues.
Communication between client and server:
By typing a URL (Uniform Resource Locator) into the address box of the browser the communication between a browser and a web server is started. Each conversation consists of two pieces:
a request for information from the browser software and a response from the server addressed by the URL.
Fig: Communication between client and server
Communication in static web page:

The following five steps are involved for the building of a static web page : An author writes a HTML page, and saves it within an .htm or .html file on the server Sometime later, a client (user) requests a page by typing a URL into their browser, and the request is passed from the browser to the web server The web server locates the .htm or .html page and converts it to an HTML stream The web server sends the HTML stream back across the network to the browser
The browser processes the HTML and displays the page.
Fig: Steps of communication in static web page
2.5 Dynamic Web Pages

In a dynamic web page content (text, images, fields, etc.) on the web page can change, in response to different contexts or conditions. There are two ways to create this kind of web pages: 1. Using client-side scripting to change interface behaviors within a specific web page. 2. Using server-side scripting to change the sequence of the web pages or web content. 2.5.1 Client Side Scripting: Using client-side scripting to change interface behaviors within a specific web page, in response to mouse or keyboard actions or at specified timing events. In this case the dynamic behavior occurs within the presentation. Such web pages use presentation technology called rich interfaced pages. Client-side scripting languages like JavaScript or Action Script, used for Dynamic HTML (DHTML) and Flash technologies respectively, are frequently used to orchestrate media types (sound, animations, changing text, etc.) of the presentation. The scripting also allows use of remote scripting, a technique by which the DHTML page requests additional information from a server, using a hidden Frame, XML Http Requests, or a Web service.
The Client-side content is generated on the user's computer. The web browser retrieves a page from the server, then processes the code embedded in the page (often written in JavaScript) and displays the retrieved page's content to the user. The innerHTML property (or write command) can illustrate the client-side dynamic page generation: two distinct pages, A and B, can be regenerated as Document. InnerHTML = A Document. InnerHTML = B; or "on load dynamic" by document.write(A) and document.write(B). There are also some utilities and frameworks for converting HTML files into JavaScript files. For example webJS uses innerHTML property for rendering pages from converted HTML on client-side. and
Fig: Client side scripting for dynamic web pages
2.5.2 Server Side Scripting: A program running on the web server (server-side scripting) is used to change the web content on various web pages, or to adjust the sequence of or reload of the web pages. Server responses may be determined by such conditions as data in a posted HTML form, parameters in the URL, the type of browser being used, the passage of time, or a database or server state. Such web pages are often created with the help of server-side languages such as ASP, ColdFusion, Perl, PHP, and other languages. These server-side languages often use the Common Gateway Interface (CGI) to produce dynamic web pages. Two notable exceptions are ASP.NET and JSP, which reuse CGI concepts in their APIs but actually dispatch all web requests into a shared virtual machine. Server-side dynamic pages can also use the first kind of dynamic content on the client side. While VM-based server-side languages and CGI would be preferred for new development, some web-servers also support Server Side Includes (typically for a file extension such as .shtml), and Jhtml was a Java server-side technology developed before JSP.
Fig: Server side scripting for dynamic web page
2.6 Design of Virtual Keyboard

Virtual/soft keyboards allow users, to input text using touch screen and stylus. For English language, several virtual keyboard layouts have been proposed. These include Mackenzies and Zhangs OPTI layout, improved OPTI layout in a 5x6 layout (OPTI II) with38 wpm (words per minute), FITALY keyboard and Chubon keyboards. Evaluation of the performance of virtual keyboards involves the use of Fitts Law. Keyboard input speed is measured in wpm (words per minute). Mean time (MT), to move to a key on virtual keyboard, is computed in terms of moving to a target key K of width W lying at distance A from the current position of pointing device . The layout of keys on virtual keyboard should be such that to minimize the mean time for all digraph movements. The digraph frequencies are a natural feature of languages. Mackenzie and Zhang evaluated the performance of their virtual
keyboard by computing 27x27 digraph frequencies from a corpus [5]. The distances (amplitudes) for all the 27 x 27 digraph movements in a given keyboard layout were computed, and for each movement the Fitts Law was used to compute the MT. The following equation was used to compute the MT. The main step is to design the virtual keyboard in Hindi.
To design the virtual keyboard in Hindi we are using Devanagari script.
The Bureau of Indian Standards has standardized the character set for the Devanagari script.
The standard is named the Indian Script Code for Information Inter change (ISCII).
Fig: Sample Virtual Keyboard in hindi
2.7 Need for Translation and Security of Regional Language

Translation As we know India is a multilingual country, so communication takes place in many regional languages .
The translation of a regional language into corresponding English script will provide a way to connect people through their native languages.
Security
Many a times it is required to secure a communication in regional language over the networks. For example to secure an e-mail in a regional language.
Script Translation
HOW?? Rule-based Script Translation DEVNAGARI Phonetics based script
Words are largely written according to phonetics(pronunciation)
Possibility that a written word is pronounced differently is very less Does not require memorizing spellings
The pronunciation of Hindi (Devnagari) words is not continuous; it takes momentary stops
in between. E. g.
2.8 TRANSLATION PROCESS: The translation processes implies an entire process of how a translator produces equivalences between a text or portions of a text into another language. The translation process can be described as: Decoding the meaning of the source text, and Re-encoding or translating this meaning in the target language. Behind this simple process lies various activities like checking grammar, syntax, idioms, semantics, and the like of the source language and also the culture of its speakers. 2.8.1 Translation Types: There are different types of Translation Technical translation scientific translation artistic (literary) Translation translation of documents general translation Translation used in this approach is artistic translation. It can be defined as: In this paper, we only deal with artistic translation, i.e. only the text in the html
page need to be translated . so it is literary translation. Literary translations don't only require a
thorough knowledge of the source and target languages, but also the ability to correctly translate the original feelings and to employ the most appropriate language means in the translation. A good translation agency will provide you with an experienced proofreader whose native language is the target language of the translation.
2.8.2 Steps Involved in Language Translation To maintain the highest quality of translation, usually three step quality processes is followed:
The document is translated by a professional translator. This translator is a native
speaker of the required language. He is also an expert in his area of specialization.

The document is then proof-read by another translator for accuracy. He can offer
suggestions for any changes that make the document easier to understand. Finally, the document is reviewed to ensure accuracy, consistency, appropriate formatting, and overall quality of the final product so that everything meets the expectations and is ready for delivery to the clients. 2.8.3 Translation Tools: Google Translate Tricia 2.7.3.1 Google Translate Google Translate is a free, web-based and statistically-based machine translation service provided by Google. It enables to translate section of text, document or webpage, from one language to another. Google translate API
The Google Translate API lets websites and programs integrate with Google Translate programmatically. During the project development phase Google provides two versions of API. The version 2 is the latest available version of the Google Translate API. We decided to use version 2 within the project. After that point whenever we refer to translate API in this report, we mention version 2. One needs a Google account to use the translation service. Because, the Translate API requires the use of an API key and it can only be received from Google APIs console8. There are two ways to invoke the API: Using REST 9 directly or using REST from JavaScript (This does not require server-side coding.). JSON10 is used by Google as a data format. Limitations When one uses the Google API, it is required to accept the terms and conditions. Here are the most important limits for our project: 1. Every request text to be translated can be up to maximum of 5000
characters long. 2. 3. Daily limit is 100.000 characters per API key. Continuous translation requests successively results in Suspected Terms
of Service Abuse. 4. Batch requests are against Terms of Service.
2.8.3.2 Tricia Tricia Platform is an Open Source platform for developing dynamic web applications. It is built in Java and realizes the model-view-controller pattern, which consists of the following components: I. II. III. An abstraction for dening control ow A templating language An object/relational persistence mapping
It has to be emphasized that what has been described so far is called Tricia Platform, since it is a generic platform for building arbitrary dynamic web applications. Tricia Platform is implemented in the Eclipse project Toro. In addition to the pure infrastructure, the toro project already comes with the basic asset types Person and Group, which are required by almost any dynamic web application. Additionally, Toro comes with an existing basic layout. On the other hand, there are concrete plug-in built on top of the Tricia platform and the basic Tricia plug-in. combining these plug-in results in the Tricia Application. A typical conguration of Tricia consists of the plug-in Toro, File, Wiki, and Blog. The distinction between the platform and the application is similar to Ruby on Rails as a platform and applications like Base camp or Backpack, which are built using Ruby on Rails. Client and Server Side: I. Tricia is a web knowledge collaboration and communication tool. As common to every web tool, Tricia has client side features and server side functionalities. II. The server side functionalities of Tricia include the user management and management of the plug-ins to the Tricia core like blog, wiki page. The client side features of Tricia includes the handling of inputs (user generated contents) like wiki page content, blog content, comment, feedbacks. What needs to be translated? The internationalization plug-in of Tricia needs to translate of the server side static texts such as labels of elements, warning messages along with the dynamic user generated content such as the blog content generated by the user. The server side static text includes: The text available in Messages class. This text represents the static String messages that are used display information to the user The text available in messages.xml
The static text messages available as objects of SimpleMessage.java class
The domain values. For example, instances of Membership Visibility class

The static text messages embedded within the template htm les .
The dynamic user generated text includes: The RichStringProperty elds which includes the user-generated content of the blog page, wiki page, comment and description elds, etc. Existing Internalization System The present internationalization system in Tricia is not fully tested and does not perform its full intended functionality. It is a partially implemented system. The internalization features present in Tricia are: Language Handler: The Language Handler handles the change of language parameter as triggered by the user action. The Language Handler identies the user chosen language from the url parameter and sets in to the session variable. The session variable is set when the user clicks his/her preferred language on the Tricia page. The languages are identied with the ags as icons. The user can chose any of the language available from the ags displayed on the top right corner of the home page.
Translator Congurator:
The Language ags on the Tricia pages can be congured through the Translator congurator tool of Tricia Platform. This tool provides a way to add the desired languages (according to the multiple languages required to be supported by the Tricia). A language can be added through the congurator tool. The Internationalization plugin for Tricia has to Identify the texts appropriate for translation.
Store and handle the transalted text. Update the Tricia Web page according to the language chosen by the user. Regularly update the translations.
2.9 Technical Design:
As we mentioned before, static texts are not stored in database in the Tricia. However, we decided to save translated texts into database because of three reasons: Performance issues, Google Translate API limitations and memory Consumption. If we think translation as a kind of computation, we can say that we use optimization
technique so-called memorization . We translate the texts once and store them. Whenever we need a translation of a text, we look up from database table. On the other hand, this method reduces API calls and helps us not to exceed API limits. The last but not least is memory consumption. The static texts were stored in the les and when Tricia started to run, the texts were copied into memory in order to benet of speed of memory operations. This was acceptable for one language but what happens when Tricia supports many languages? This increases memory consumption factor of supported number of languages. Scalability of Tricia was undermined due to the internalization. Storing the static texts into database enables us to overcome all these problems.
2.10 Tricia is based on state-of-the-art technology

Minimal technical requirements for enterprise-wide access 1. Client: Browser without plug-ins, also mobile access Internet Explorer, Firefox, Safari, Chrome iPhone, iPad, Android, Windows Phone 2. Server: Operating system: Windows or Linux Database: MySQL, Microsoft SQL or Oracle Based on established open source components i. ii. iii. Cost, stability, time-to-market, Java, MySQL, LDAP, E-Mail, Lucene, jQuery (Ajax), JSON, REST, Well-understood, non-viral licenses
State-of -the-art software architecture i. ii. Plugins, mixins, data model driven, introspective, service-oriented Cloud-ready
3.0 Comparative analysis
Table of Language that support separation of concerns
4.0 Investigation of problem area and Findings 4.1 Analysis of Problem Domain:
Identification of concerns: Automatic design of web pages is a very important and complex problem. Here we have to consider a lot of interconnected factors such as constantly increasing users requirements, a large variety of the languages used, advanced standardization, etc .After analyzing the domain of the automatic web page creation, we have identified three main groups of concern (see Figure 2) as follows:
Presentation concerns reflect the problems of presentation of data to the users,
including the graphic solutions for web pages (pictures, background, animation, etc.), national languages of the text used, the architecture and structural layout of web pages.
User concerns are related with identification and authentication of users,
personalization and ensuring security of the transmitted information.
Variability concerns relate with variability in a domain such as different types and versions of web pages, dynamic aspects of web pages and transformation of web pages.
Taxonomy of Concerns:
4.2 Basic Frame work Of Proposed Approach: A framework of our approach is shown below. The framework consists of two major components: RTR and IHDD, which are discussed in the subsections below. The RTR (Retrieve, Translation and Render) module searches the Internet for the web page with respect to request given by the user. After getting the requested page, it translates the retrieved web page into language L and renders the resulting web page in proper manner to the client machine. This module consists of three sub modules namely Retrieve, Translation and Render. The Retrieve sub module retrieves a web page as requested by the user and separates the content of web page (by using HTML parser) into HTML tags and English text. Proper indexing of links in the page is done and maintained using a table called Index Table. The Index Table handles the layout and links present in the original web page. The Translate sub module takes the
extracted English text from the Retrieve sub module and converts the text to the language L. The Render sub module fully furnishes the web page in language L. Once text is converted, it merges the content in language L and set HTML tags using Index Table. In fact, the Render sub module recreates the web page in users language having same look as the original web page. The IHDD (Input Handler and Data Dispatcher) module is responsible for converting users input from language L to English and forward them to original web server. The module has been subdivided into two sub modules namely Input Handler and Data Dispatcher. The Input Handler first extracts the input data from web page in language L and then converts the data from that language to English. The module then invokes the Data Dispatcher which performs the authentication needed to access the web site and finally regenerates the query to be posted to original web server in English. The working of the module is described as follows. User enters the URL of a web page what he wants to get serviced.
Fig: Frame Work of Two Way Interaction
The proposed interface then invokes the Retrieve sub module within RTR, (Step 1).After that, Retrieve module searches the specified web page in the Internet and result is returned back to the same module (Step 2 & 3). Once the web page is fetched, the Retrieve module separates the HTML tags and English text from the web page. The separated English content is further sent to Translation module (Step 4) for converting to language L and stores the link information in Index Table for proper maintenance of the web page (Step 6). After the completion of text conversion, Render module takes the input from Index Table and Translation module to merge the content of English text and HTML tag and generates the virtual web page in users language (Steps 5, 6 and 7). This completes the first phase of converting the requested web page in Language L. In second phase, user gives input in his language by filling forms which appears on the virtual web page in L with the help of virtual keyboard [19] (Step 8). Input Handler then extracts the text entered by user (Step 9) and calls Translation module to convert the text from Language L to English. After that, this generated English text and the virtual web pages are sent to Data Dispatcher module (Steps 10 and 11) which regenerates the query in English, handles all the authentication needed to post the web page in Internet and then invokes the Retrieve module (Step 12). Now the task of Retrieve module is to process the request and invoke the remote server which accesses the database (database contents are in English). The result returned from the remote server has finally been stored within the Retrieve module (Step 13 and 14). The Retrieve module then sends the result to the Translation (Step 15) and Render (Step 16 and 17) modules which generate web page in language L. This gives illusion to user that the result which is displayed on the virtual web page fetched exclusively in users language instead of English.
5.0
Comparative analysis for proof of findings :

In this section, we illustrate our proposed mechanism with two case studies to compare the
results for the proposed approach .Here we deal with two cases. They are a. Indian Railway Passenger Reservation System b. Wikipedia English website c. Andhra Pradesh State Road Transport Corporation System A. Indian Railway Passenger Reservation System We consider one of the popular web services in India, Indian Railway Passenger Reservation System (IR-PRS). Our proposed mechanism provides an interface between the User and IR-PRS in Internet maintained by Indian Railways (CRIS). The interface gives a flavor to the user that the entire IR-PRS web page is written in his language. It also provides facility to the user for giving input and getting output in his language in his language. In this study, we Explain the accessing the IR-PRS in Hindi language (spoken majority of people in India). It is not necessarily limited to Hindi. In fact it can be applied to any language, of course with their corresponding translation scheme in needed.
Fig: Original content of IR-PRS
Fig: Entering input in Hindi to virtual web page of IR-PRS
The original service provided by Indian railway will be beneficial for user familiar to English language. The corresponding web page of Indian railway written in English language is shown . The converted web page in Hindi language is shown . When user gives source and destination name of stations say Kharagpur and Delhi to the original web page of IR-PRS the results returned by IR-PRS in English is shown in. With our proposed Interface, this original web page is first translated to Hindi using machine translation systems and displayed the same but in Hindi. The users are now allowed to enter the text directly in Hindi Unicode format using virtual keyboard for Hindi. After entering the source (Kharagpur) and destination (Delhi), the user submits the form to Hindi web page for processing as shown . The result returned by IR-PRS is retrieved, translated, rendered and finally displayed in Hindi. The web page shows the detail of the train name with number in Hindi language. One can also check the availability and train time table in the same language source (Kharagpur) and destination (Delhi), the user submits the form to Hindi web page for processing as shown .The result returned by IR-PRS is retrieved, translated, rendered and finally displayed in Hindi. The web page shows the detail of the train name with number in Hindi language. One can also check the availability and train time table in the same language. Results of IR PRS:
Fig: original Results returned by server
Fig: Displaying the desired result in Hindi B. Wikipedia English website: Searching for the word (wood) in English Wikipedia http://en.wikipedia.org/wiki/ using Google website translation service, will return only those page written in Unicode. As the word (wood) doesnt exist in English Wikipedia it will not return any result but when the word wood is given it will display the English pages containing the word wood.
Fig: Result when user gives input in Hindi under Google translation for word (wood)
Fig : Actual results returned by server As our national language is Hindi, we are transforming the original web pages in English to Hindi. Every citizen in India has a minimum knowledge in Hindi.
Fig: Desired Results in Language Hindi
C. Andhra Pradesh State Road Transport Corporation System We consider one of the popular web services in India, Andhra Pradesh State Road Transport Corporation System (APSRTC). Our proposed mechanism provides an interface between the user and APSRTC in Internet maintained by Andhra Transport .The interface gives a flavor to the user that the entire APSRTC web page is written in his language. It also provides facility to the user for giving input and getting output in his language in his language. In this study, we explain the accessing the APSRTC in Hindi language (National language of India). It is not necessarily limited to Hindi. In fact it can be applied to any language, of course with their corresponding translation scheme in needed.
Fig: Accessing Dynamic web page of Andhra transport in English language
Fig: Accessing Dynamic web page of Andhra transport in Hindi language
6.0
Conclusion
gap between the Internet and user due to language barrier.
Accessing Dynamic Web Page in Users Language plays a great role, as it will minimize the
This service provides the Internet content to millions of people who might not have good capability to read the web content in English . It will minimize the gap between the Internet and user due to language barrier. It helps the users to access Internet in their day to day life without worrying much about the language web page is originally written.
Future Scope:
The user can give input in the form of voice based communication rather than using virtual keyboard. By voice based communication the stress on user can be reduced.
The user can give input by using touch screen keyboard which should be designed in respective language.
References:
[ 1 ] Unesco, international literacy statistics a review of concepts, methodologyand current data, http://unesdoc.unesco.org/images/0016/001 628/162808e.pdf . [2] India worlds second largest english speaking country, http://tesolindia. c.in/EnglishTeachingIndustry/india-worlds-second-largestenglish- speaking-country [3] Languages and cultures on the internet study 2007, http://dtil.unilat.org/LI/2007/ro/resultados ro.html. [4] Wikipedia, dynamic web page, http://en.wikipedia.org/wiki/ Dynamic web page [5]Googletranslate,http://translate.google.com [6] Translate a block of text, http://in.babelfish.yahoo.com [7] World lingo, free website translator, http://www.worldlingo.com/en/websites/url translator.html [8]Freetexttranslation,http://www.freetranslation.com [9] Free automatic translators, machine translations comparison tests, http://www.humanitasinternational.org/newstran/more-trans.htm [ 10 ] Language translation, translate phrase or word, http://www.translation.langenberg.com [11] Websites translator, translate your website from english, http://www.websitestranslator.com 2010). [12] Taming the beast, web page translation,http://www.tamingthebeast.net/articles6/page-languagetranslation.html language
[13] Ability, website translation and localization, http://www.localizationtranslation.com/translation-ocalizationservices/ web-sites-localization.html [14] Google translate api documentation, . URL http://code.google.com/apis/ language/translate/overview.html. [15] Nereid documentation, . URL http://wwwmatthes.in.tum.de/wikis/nereid/home.
[16] Tricia developer documentation, . URL http://infoasset.de/wikis/infoasset/tricia- developerdocumentation . [17] Tricia framework, . URL http://www.infoasset.de/wikis/infoasset/tricia .

Term Paper Report: Bachelor of Technology IN Computer Science Engineering (2011-12)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Term Paper Report: Bachelor of Technology IN Computer Science Engineering (2011-12)

Uploaded by

Copyright:

Available Formats

ACCESSING DYNAMIC WEB PAGE IN USER LANGUAGE