The Adobe Globalization Blog

This article was originally written in English.


Today we are launching Adobe’s first ever globalization blog. Adobe believes that everyone in the world should be able to express and exchange ideas in the language they prefer, and thus we have a strong interest in ensuring that our global customers are able to create applications, content and systems that satisfy the requirements of every geographical market.

Through this blog, we intend to provide our users with information that will enable them to achieve that. In addition, we will inform readers about new globalization-relevant product features, tools and libraries.

Also, we hope to hear from you! Have you found a globalization or localization bug? Do you have a globalization-related request for one of our products? Wrote some globalization guidelines that you want to share with the world? Here’s the place to share your feedback.

The Adobe Globalization Team

16 Responses to The Adobe Globalization Blog

  1. scau_pdc says:

    this is a good news

  2. Qc says:

    cool, looking forward more

  3. Steve Maule says:

    Good luck – look forward to following the discussions/learning!

  4. Cool, now I have two blogs where can I post about globalization :)

  5. vikash says:

    I have a flex application where user can create content in any language.
    How does flex 4 helps in achieving this through unicode without installing additional fonts?

    • Leandro Reis says:

      In flex SDK 4.0, if a developer uses the spark components or uses the mx components with the “textFieldClass” style set to
      ClassReference(“mx.core.UITLFTextField”) then the text that is displayed will be using the Text Layout Frame (TLF) and the new Flash.Text.Engine APIs made available in Flash Player 10.0. These provide font back for both embedded fonts and system fonts.

      The following specification shows how to use TLF with the halo components:

      Unfortunately there is no control over which fallback fonts are used. To get a correct fallback font for Traditional Chinese, Simplified Chinese, Korean, and Japanese ideographic characters, the “locale” style also needs to be set correctly. The developer will therefore need some way to determine if the content is in one of these writing systems and set the locale style appropriately.

      One other caveat is that TLF and the flash.text.engine classes only support OpenType fonts. Thus fallback may not work correctly for all languages on each operating system. For example on the Mac, Hindi content may not appear due to the lack of a Devanagari OpenType font.

      Answer provided by Craig Rublee, Globalization Architect (Adobe Systems)

  6. yangart says:


    (Great, but I hope Adobe does a better job with its Chinese localization.)

    • Lily Wen says:

      我在本地化部门工作。希望您能以举例的方式提供更详细的,需要改进的具体方面, 我们以便加以改进。

      (I work at Adobe’s product localization. Could you please provide more detailed feedback as to what areas Adobe should improve so we can work on them? Some examples would be helpful.)

      • yangart says:


        (For Chinese hyphenation, the rule is to have no single character in a separate line. Wish to have a feature to “squeeze” that single character up to the previous line when the automatic hyphenation leaves one character in the last time.)

        • Lily Wen says:


          (Thanks for your feedback examples. With regard to hyphenation support, since many of our products need enhanced support, due to limited time, we need to prioritize. Could you please let us know which Adobe product(s) are of immediate need of such support to you?)

  7. yangart says:

    ID CS5中文版在排阿拉伯语言时不能按正确的阿拉伯语言规则来排,我记得IDCS4的时候是可以正确排的。希望可以增强多语言的混排功能。比如:英文+阿拉伯语言的混排,中文+阿拉伯语言的混排。

  8. florence says:


Leave a Reply

Your email address will not be published. Required fields are marked *