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

18 thoughts on “The Adobe Globalization Blog”

  1. 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?

    1. 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)

  2. 太好了,不过希望ADOBE能在中文本地化服务方面做得更好

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

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

      (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.)

      1. 在中文排版中单字是不能成一行的,希望在段落样式中有一个功能当出现段尾单字时自动挤压到上面,不要出现单字行。如果在长文件的排版中没有这样的功能全靠自己手动微调工量是很大的。

        (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.)

      2. 谢谢您提供反馈的例子。针对段落支持,因为我们有很多软件产品需要支持,但我们时间有限,所以我们需要决定那些产品有更急迫的需求。请告诉我们您希望那些产品尽早的提供这种支持。

        (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?)

      3. 文字排版要求最急迫的是indesign

        (Text layout requirements are most urgent for InDesign)

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

  4. 請告訴我:我的電腦是ipad2我該裝置那一種貴公司銷售的軟件,請詳細回復!謝謝!

  5. Somos usuarios de los productos Adobe desde hace más de 20 años, desde los tiempos de tipos de letra y distiller en mac 🙂 siempre es interesante para nosotros seguir las noticias del blog

Leave a Reply

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