SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Internationalization of HTML client-server applications

barto avatar
barto
10 diapositives · 202 Views · Aug 31, 2014

Learn the key concepts, strategies, and limitations of internationalizing HTML applications, including design considerations, coding practices, and testing methods. Find practical tips for managing charsets, browsers, and form data to create a multilingual user experience. Explore resources for further information and join the global community of developers dedicated to i18n.

Internationalization of HTML client-server applications - slide 1
01 / 10Internationalization of HTML client-server applications
1 / 17

Télécharger la présentation

Internationalization of HTML client-server applications
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  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!