GALA Blog

Language service providers around the globe have been heavily impacted by the economic downturn, but many expect a rebound in the next three months, according to the Globalization and Localization Association’s most recent quarterly survey. The survey, which asks GALA members about trends in the industry, was conducted in May and was the third in a row to question language service providers on the economic downturn.

A full 78 percent of respondents said they had been impacted by the downturn in the last three months (Feb – April), a marked increase from 57 percent who indicated they had been impacted in the previous February survey. Far fewer in North America felt a direct impact (55 percent) than Europe (83 percent) and Asia (85 percent).

The Internationalization Tag Set (ITS) version 1.0 has just been published as a W3C Recommendation. You can read the W3C press release.

ITS is a set of attributes and elements designed to help in the internationalization and localization of XML material. It can be used externally to the documents (a bit like the “DTD Settings” file in Trados), and it can be integrated within the XML documents themselves.

The ITS 1.0 Specification can be found here: www.w3.org/TR/its

You can find extensive examples, descriptions and links to implementations of ITS on the ITS Working Group page: www.w3.org/International/its.

The next step for the Working Group is the publishing of the “Best Practices for XML Internationalization” which is currently a Working Draft.

The Last Call Working Draft of the Internationalization Tag Set has been published.

Along with it a new document the Best Practices for XML Internationalization has also been published as a First Working Draft.

I would encourage anyone who develop translation tools that provide support for XML to review the ITS Specification document. Part of the specification addresses some of the XML localizability issues, offering a common way to specify localization information:

• what should or should not be translated,
• some terminology identification mechanism,
• identification of inline codes and sub-flows,
• localization notes,
• and more…

You can use Bugzilla to point out issues and provide comments. The review period lasts until June-30 (6 weeks).