What Every Translator Should Know About Software Localization
Upcoming SlideShare
Loading in...5

What Every Translator Should Know About Software Localization






Total Views
Views on SlideShare
Embed Views



3 Embeds 49

https://twitter.com 39
http://www.linkedin.com 6
https://www.linkedin.com 4



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • WIP Japan Corporation
  • Lionbridge
  • LISA = L11N Industry Standards Association
  • Swedish for ORacle
  • Monster, Manpower,

What Every Translator Should Know About Software Localization What Every Translator Should Know About Software Localization Presentation Transcript

  • Cris Silva [email_address] American Translators Association 51 st Annual Conference November 2010, Denver
    • G11N, I18N, L10N
    • A Typical L10N Project
    • L10N Best Practices
    • Bugs and Types of Bugs
    • Working On-Site
    • Standards
    • Jobs
  • “ Globalization, as defined by rich people like us, is a very nice thing... you are talking about the Internet, you are talking about cell phones, you are talking about computers. This doesn't affect two-thirds of the people of the world.” Jimmy Carter in 2002 Economic, industrial, financial, political
    • Everybody talks about globalization
      • “ Integration” of trade
      • “ Removal” of barriers between borders
    • Research on and identification of global markets
    • Market validation and selection
    • Identification and formalization of global business requirements
    • Language translation and cultural integration (a.k.a. Internationalization and Localization)
    • Identification of technology standards and solutions (format and structure)
    • Identification of cross-market affinities (to enable marketing and technology asset reuse)
  • Internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes.
    • Creating illustrations for documents in which the text can easily be changed to another language and allowing expansion room for this purpose
    • Allowing space in user interfaces (for example, hardware labels, help pages, and online menus) for translation into languages that require more space
    • Creating print or web site graphic images so that their text labels can be translated inexpensively
    • Leaving enough space in a brochure to drop in different length languages
    • Separating the language elements from the graphic elements, or abstracting content from markup in a web application and software
    • Using written examples that have global meaning
    • Insuring that the tools and product can support international character sets
    • For software, ensuring data space so that messages can be translated from languages with single-byte character codes (such as English) into languages requiring multiple-byte character codes (such as Japanese Kanji)
    • L10n is the process of adapting the text and applications of a product or service to enable its acceptability for a particular cultural or linguistic market.
    • Translation is the central activity of localization.
    • Localization goes beyond literal translation
    • Other locale information such as currency, national regulations and holidays, cultural sensitivities, product or service names, gender roles, and geographic examples among many other details must all be considered.
    • A successfully localized service, software or product is one that seems to have been developed within the local culture.
    • Translating text content, software source code, web sites, or database content; machine translation may be used in early stages.
    • Adjusting graphic and visual elements and examples to make them culturally appropriate
    • Post-production quality control of content, systems and the integrated product
    • First let’s consider what needs to be localized:
      • Website - search functionality, look and feel, etc.
      • Device (medical, pharmaceutical, industrial) – look and feel, functionality
      • Software
        • General computing = search, functionality, etc.
        • Financial, banking = SSN, currency
        • Gaming = humor, culture
    • Quality Assurance: A set of activities designed to ensure that the development and/or maintenance process is adequate to ensure a system will meet its objectives.
    • Quality Control: A set of activities designed to evaluate a developed work product.
    • Testing: The process of executing a system with the intent of finding defects. (Note that the "process of executing a system" includes test planning prior to the execution of the test cases.)
    • Verification : sampling
    • Most testing and verifications are done in native OS in:
      • Windows
      • Mac
      • To simulate end user’s in-country experience.
    • Some projects may be tested in combinations of OS versions:
    • For example, in one project, Spanish may get localized and then tested for Windows 7, but Romanian in Windows Vista or XP due to market requirements
    • User's language, country and any special variant preferences that the user wants to see in their user interface.
    • A few locale settings:
      • Number format setting
      • Date/Time format setting
      • Currency format setting
      • Paper size setting
    • A few locale “flavors”
      • Spanish – “Neutral” or Castilian?
      • French – European or Canadian?
      • Portuguese – Brazilian or European?
      • English – American or British?
    • How well has a software build been localized into a particular target language?
      • Operating System
      • Keyboards
      • Text Filters
      • Hot keys
      • Spelling Rules
      • Sorting Rules
      • Upper and Lower case conversions
      • Paper Size
      • Mouse Date formats
      • Rulers and Measurements
      • Memory Availability
      • Voice User Interface language/accent
      • Video Content
    • Error, flaw, mistake, failure, or fault
    • Unexpected result
    • Unintended behavior
    • Linguistic = having to do with language syntax, structure, grammar, etc. Also stuff that was not translated.
    • Formatting = Layout, clipping.
      • These bugs can be fixed by engineer and DTP.
    • Functional = Program functionality.
      • These bugs are generally fixed by engineering.
    • Internally, with itself:
      • Terminology
    • Externally, with other materials:
      • Does the software match the User’s Guide?
      • Does the Help match the User Interface?
      • Consistency – internally and externally
    • In-house, confidential projects
    • In-country
    • In the US
    • Not your workstation
    • Not your keyboard
    • Not your chair
    • Not your environment
    • Not your monitor
    • Team work
    • Individual work
    • Project Managers
    • Project Coordinators
    • Engineers
    • Desktop Publishers