1 / 10

Internationalization of HTML client-server applications

Internationalization of HTML client-server applications. Andrea Vine iPlanet Internationalization Architect. Designing the functional interface . Plan for i18n when you create your specifications Consider the nature of the data your application is processing

barto
Download Presentation

Internationalization of HTML client-server applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Internationalization of HTML client-server applications Andrea Vine iPlanet Internationalization Architect

  2. Designing the functional interface • Plan for i18n when you create your specifications • Consider the nature of the data your application is processing • How will the majority of customers access the application? • Will users be working with one language at a time or with multiple languages?

  3. Some concepts and limitations • Each HTML page is limited to a single charset • The CGI script has no knowledge of the client • Provide customers ways to access the interface by language • Create a single home page displaying a choice of languages on it • Allow for customization of the initial access point

  4. Choosing the CGI language • Any programming language is internationalizable • The classic CGI script has no persistence in server memory • There are server utilities that provide an API for CGI scripts • Java servlets are persistent as well, but they require Web servers with servlet support

  5. Writing the HTML • Create the configuration of pages, frames, and browser windows • META tag or comment with proper charset • Use fixed text as images to solve some charset incompatibility • Alternate text for images may not always work

  6. Managing HTML FORMs • FORM data is submitted in the charset of the page/frame • Input text and textareas are handled by the native system • Pre-filled text may not always look right • Charset conversions and defaults in browsers

  7. More HTML quirks • <SELECT> and <OPTION> tags - value parameter, dynamic filling • Local file access and other browser-controlled elements • Testing environment may not work like actual environment

  8. Coding the CGI script/program • Writing internationalized CGI is like writing any internationalized programs • Parse FORM fields, gathering charset and locale values first • Code workarounds for mismatched client and server charsets, locales • Inspect for other data, such as HTML inside input text

  9. Test your application • Set up machines in various locales as clients • Run server in various locales • Use different browsers and versions • Invite customers to beta test

  10. Where to find out more • Discussion lists – i18n-prog@acoin.com • Book – Global Solutions for Multilingual Applications, by Chris Ott Experimentation!

More Related