L10n:WorldReady/Screenshot Guideline

Introduction

There are two way of creating the screens. One is by taking a screenshot using a functioning and localized product. Another is by translating all the strings in an en-US mockup in a spread sheet. The former requires guidelines on the specification for the screenshot, the latter relies an creative agency to implement localized content. With each solutions, there are pros and cons.

Taking Screenshot

• Pros:

  *  Actual reflection of a functioning and working application
  *  No issues of possible inconsistency with terminologies
  *  No issues of multiple localizers using different terms for the same English word/phrase
  *  Reviewed and approved product UIs.
  *  

• Cons:

  *  A QAed working product may not be ready until late in the development cycle.   
  *  Screenshot resolution may not be high enough for printing large poster for PR and Marketing purpose.
  *  Not everyone follows the step by step guidelines on how the screenshots must be taken, specs on the image size and resolution.  Quality may vary. 

Faking Screenshot

• Pros:

  *  As soon as mockup is approved, localizable strings can be identified and translated
  *  Creative agency assembles the final images that may require high resolution for printing purpose.  
  *  Long lead time before launch, can be worked on simultaneously while the product is still being developed.  

• Cons:

  *  A QAed working product may not be ready until late in the development cycle.   
  *  Screenshot resolution may not be high enough for printing large poster for PR and Marketing purpose.