W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > April 2012

[ACTION-42]: Provide some input on the scripting issue

From: Pedro L. Díez Orzas <pedro.diez@linguaserve.com>
Date: Wed, 4 Apr 2012 19:48:59 +0200
To: <public-multilingualweb-lt@w3.org>
Message-ID: <4D2462F74F4B4C15884AF141863F89B9@newlas.local>
Dear all,


This action is related to [ISSUE-5]: Scripting content, which is related
itself with including a “best practices” section in the MLW-LT Metadata
Standard document. If we go ahead with this section, this list needs to be
completed and revised. We suggest if possible to leave open the “best
practices” section during the implantation phases of the use cases of the
mlw-lt metatada. This could maybe allow us to transmit more near experiences
and best practices as result of using the mlw-lt metadata. 


In this sense, we provide some input for three scenarios: script content,
CMS, and published pages:


1) Scripting content best practices


The basic principle is to use patterns to treat (remove, import, insert, etc
) text strings to translate. 


a.- Server-side (PHP, ASP, etc.) scripting language recommendation: Grouping
the literal text and messages in text files, such as properties or other
types of repositories as a DB, it is recommended, not in the code.


b.- Client side (e.g. JavaScript) scripting laguage recommendation; two


(i) Literals may exist in both JS files as JavaScript code embedded in HTML
code. For this you can generate an array of literals. This case is not
really practical for the developer. For example, the literal is inserted
into the first line the code: 


var myLiterals= ["Click here", "More", "Back"];


(ii) Data structures are used and are marked with tags. This indicates that
only need to translate all the text in quotes (eg "Name") in the comments
JS_texts (with / ****). This case is functional and suitable for the
programmer but more complicated for the filtering by the application or the
CAT system (more complex regular expressions).:


/*** JS_texts_begin ***/

var APP.literales = {

                name: "Name",

                age: "Age"


/*** JS_texts_end ***/



< JavaScript Code>




2) I18N best practices for CMS


a. Avoiding to mix different languages in texts of the same content.

b. Providing the most complete possible contents for translation (eg the
ideal granularity for translation in Web content is the main body of the
page, eliminating the side menus, headers and footers).

c. Contextualizing the translation of short texts, for example, sections of
a Web (section names, names of form fields, alerts the user) or extraction
of texts from applications.

d. Using standard structured formats in exchange systems for B2B translation
type (for example, xml, xhtml…).

e. Internationalizing the scripts.

f. Avoiding the inclusion of script tags (jsp, php, asp, etc.) within the
tags of other languages (html, JavaScript).

g. The same content in its various language versions being horizontally
accessible without having to go through another upper categorie. To do this
it should be referenced / related among then.

h. Categorizing the content by type (news, calendar, restaurants ...) 


3) I18N best practices for published web pages


a. Do not use styles or formatting tags (strong, em, etc), and apply as much
as possible styles with CSS and class attributes at the label level. 

b. Do not use br tags to create vertical text, but always use CSS style

c. Use friendly URLs based on directories, never Query String (GET or POST

d. Use internationalized suffixes or directories in the paths for static
files, such as /images/ example_pt_br.jpg or /images/pt_br/sample.jpg



We hope it helps.






Pedro L. Díez Orzas

Presidente Ejecutivo/CEO

Linguaserve Internacionalización de Servicios, S.A.

Tel.: +34 91 761 64 60
Fax: +34 91 542 89 28 

E-mail:  <mailto:pedro.diez@linguaserve.com> pedro.diez@linguaserve.com

www.linguaserve.com <http://www.linguaserve.com/> 


«En cumplimiento con lo previsto con los artículos 21 y 22 de la Ley
34/2002, de 11 de julio, de Servicios de la Sociedad de Información y
Comercio Electrónico, le informamos que procederemos al archivo y
tratamiento de sus datos exclusivamente con fines de promoción de los
productos y servicios ofrecidos por LINGUASERVE INTERNACIONALIZACIÓN DE
SERVICIOS, S.A. En caso de que Vdes. no deseen que procedamos al archivo y
tratamiento de los datos proporcionados, o no deseen recibir comunicaciones
comerciales sobre los productos y servicios ofrecidos, comuníquenoslo a
clients@linguaserve.com, y su petición será inmediatamente cumplida.»


"According to the provisions set forth in articles 21 and 22 of Law 34/2002
of July 11 regarding Information Society and eCommerce Services, we will
store and use your personal data with the sole purpose of marketing the
products and services offered by LINGUASERVE INTERNACIONALIZACIÓN DE
SERVICIOS, S.A. If you do not wish your personal data to be stored and
handled, or you do not wish to receive further information regarding
products and services offered by our company, please e-mail us to
clients@linguaserve.com. Your request will be processed immediately."



Received on Thursday, 5 April 2012 12:07:09 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:43 UTC