A to Z of Internationalizing your Eclipse and testing challenges

"A person who speaks two languages is called bilingual. A person who speaks three languages is called trilingual. So what do you call someone who speaks/understands any language? ..called Multilingual" as such products called globalized products. Today, providing a software product solely in English is no longer acceptable from a usability, quality, marketing, and in some cases, legal standpoint. Enabling your product for the world market simply makes product reachable to all.


1 favorite thumb_down thumb_up 4 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

This session talks about understanding & importance of Internationalization and localization. Also explains about implementation & testing of I18N aspects in eclipse based products. 

  • Move translatable strings into *.properties files
  • Separate presentation-dependent parameters
  • Use proper locale-sensitive data formatting, substitutions APIs
  • Test in domestic language
  • Create initial translated plug-in fragment
  • Prepare and send domestic language materials for translation
  • Repackage and validate translated materials
  • I18N UI testing tips

Learning Outcome

Key takeaways are:

  • Complete understanding on I18N concepts and terminology.
  • Implementation in Eclipse.
  • Techniques for testing

Target Audience

First-level developers, QA

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Submission
  • Pradeep Balachandran
    By Pradeep Balachandran  ~  2 years ago
    reply Reply

    Hi Divya,

    Please respond to Naresh's queries below.  I would also suggest to include the coding patterns available in Eclipse in helping developers to externalize the strings - there is a wizard, there is the NLS class, etc. This will make it very relevant to the participants. Internationalization does not need any introduction. You can focus on advanced topics in this area.

    Please respond ASAP as we need to decide the final agenda soon.  Thanks!

  • Naresh Jain
    By Naresh Jain  ~  2 years ago
    reply Reply

    Hi Divya,

    i18n and l20n are very important topic and I'm glad you proposed a session to cover these topics. I'm pretty sure today, no one would argue against the need for i18n and l20n. Its a pretty standard industry practice in all kinds of application development. However there are several changes when it comes to implementing and testing for i18n and l20n.

    Right now, your session is proposed as a generic talk which touches upon several topics ranging from implementation & testing of I18N. I've following questions for you:

    • Are you focusing on i18n alone or would you touch upon l20n also?
    • Looks like your experience is based on a real world example, do you think it would be better to focus on a case-study rather than a generic overview talk? As part of the case-study would be you able to walk us thru actually what happened?
    • Implementation & testing of I18N are both very vast topics. Would it be better to focus on just one?
    • Is there are reason you need 3 people to present this topic?

    We would greatly appreciate, if you can update your proposal by adding a link to any of your past presentation video. This will really help the program committee to understand your presentation style and schedule your session accordingly.


  • Pradeep Balachandran
    By Pradeep Balachandran  ~  2 years ago
    reply Reply

    Hello, thanks for the submission on the topic of internationalization. Very relevant talk for the audience. Could you please mention in the abstract if you are contributing to Eclipse Babel project (http://www.eclipse.org/babel/)?

    • Venkat Rajesh
      By Venkat Rajesh  ~  2 years ago
      reply Reply

      We are not currently contributing to babel project, however, as part of this talk, we will touch up on babel.