You can download this file and edit it with the TMX Editor from Heartsome. Register with Heartsome and get a 30-day trial copy of TMX Editor.
For those of you with Translation Memory (TM) Tools, we can convert this multilingual file into source-target language pairs. Contact Bob Doyle to get language-pair files, in SDLX or TRADOS formats.
If you would prefer an Excel spreadsheet with the English-language source labels, here is a spreadsheet with the translations so far.
Contributors/Localizers
| Arabic | Rana Allam |
|---|---|
| Dutch | Adriaan Bloem, Erik Hartman |
| French | Robert Bédard, Raymond Bissonnette, Jane McConnell, Benoît Secher |
| German | Anna Fuhrmann, Jörg Dennis Krüger |
| Hebrew | Yair Dembinsky |
| Italian | Paola Di Maio |
| Japanese | Tomoko Yamato |
| Spanish | Mario López de Ávila Muñoz |
We may be able to do this with the existing CMS Wiki where collaborative development is done for the Content Management Glossary.
This CM glossary is repurposed for glossaries in closely related disciplines like Information Architecture, Interaction Design, Knowledge Management, and Taxonomy.
In general,
The browser writes a value for the Accept-Language request header field that it sends to the web server. You can set this value in Preferences (Netscape) or Internet Options (Internet Explorer). If you choose multiple languages, they are sent to the server as a comma-delimited list in your preferred order.
With the settings above, the request header field will be Accept-Language = de,en-us,it,fr,pt-br,es.
How does the web server determine which language to serve? Is there a naming convention for multi-lingual web pages?
|
Deciding which page to serve is called content negotiation.
Tim Berners-Lee's discussion of generic web pages and their language variants describes two different naming conventions, index.fr.html and index.html.fr. The Apache Web Server compiles in content negotiation (the mod_negotiation module) by default. It postpends the two-letter language code to the URL and looks for files to serve. For example, if you set your browser preferred language to French and browse the CM Pros site, an Apache server would look for the file www.cmprosold.org/index.html.fr. Unfortunately, postfixing the language code is not as desirable as infixing it - index.fr.html - which allows the server's operating system to use a familiar extension. The Apache docs on content negotiation say that you can choose between naming conventions, because files can have more than one extension, and the order of the extensions is normally irrelevant (see mod_mime documentation for details). We suggest infixing the language (and other) variants. Microsoft Internet Information Server negotiates language with an optional ISAPI filter. There does not appear to be a standard ISAPI filter for language negotiation on the market. |
|
Do web servers handle multi-lingual requests automatically?
Not normally. The web server must have multiple language versions of a web page in order to serve them. It needs to know how the language-variant web pages are named. Besides naming them with a URI (index.fr.html), it may be possible to transmit the language variance as metadata in the HTTP header. This is the direction of the WebDAV protocol being developed by the IETF.
Finally, multi-lingual audiences may be served by XML/XSLT with each structured page containing the separate language versions in the master XML file for the page. This is a bit more difficult for localizers, who may want to edit their own page content. CM Pros is primarily doing page-oriented web content management. Some pages are XML/XSLT as part of the DITA/XML community initiative. For example, our controlled vocabulary best practice.
