Skip to main content
michaelb46780291
Participant
January 22, 2016
解決済み

Why doesn't the Creative Cloud Packager support true multilingual installations?? The same as the Acrobat customization tool where it allows the user to chose the language at the time of installation. It's a huge complication to have to download all

  • January 22, 2016
  • 返信数 1.
  • 513 ビュー

Why doesn't the Creative Cloud Packager support true multilingual installations?? The same as the Acrobat customization tool where it allows the user to chose the language at the time of installation.  It's a huge complication to have to download all Adobe apps in many languages to support a global company.  This feature would be a HUGE improvement to the Adobe  deployment process.

    このトピックへの返信は締め切られました。
    解決に役立った回答 alisterblack

    We have just released a new version of Creative Cloud Packager with greatly improved multi-language support:

    Multi Language Packages

    "Yes you have read that right. A significant issue for IT admins who support multiple locales is the requirement to create one package per language. This release of CCP and the Deployment tab (in the enterprise dashboard) will offer the ability to “Match the OS language” and the ability to specify at deployment time what language you want the package to be installed in. This in a nutshell means one package regardless of the language you wish to deploy in. This hopefully solves a significant pain point for IT admins."

    返信数 1

    alisterblack
    alisterblack解決!
    Inspiring
    January 25, 2016

    We have just released a new version of Creative Cloud Packager with greatly improved multi-language support:

    Multi Language Packages

    "Yes you have read that right. A significant issue for IT admins who support multiple locales is the requirement to create one package per language. This release of CCP and the Deployment tab (in the enterprise dashboard) will offer the ability to “Match the OS language” and the ability to specify at deployment time what language you want the package to be installed in. This in a nutshell means one package regardless of the language you wish to deploy in. This hopefully solves a significant pain point for IT admins."