U bekijkt help-inhoud voor de versie::

You can manually configure the FontManagerResources.properties file to map the default AEM forms fonts to fallback (or substitute) if the default fonts are not available on the server. This property file is located in the adobe-fontmanager.jar file.


Fallback font configuration also applies to the assembler service.

  1. Navigate to the adobe-livecycle-[appserver].ear file in the [aem-forms root]/configurationManager/export directory, make a backup copy, and unpackage the original.

  2. Locate the adobe-fontmanager.jar file and unpackage it.

  3. Locate the FontManagerResources.properties file and open it in a text editor.

  4. Modify the Generic and Fallback font locations and names as required and save the file.

    The font entries in the FontManagerResources.properties file are relative to the [aem-forms root]/fonts directory. If you specify fonts that are not default AEM forms fonts, you must install those fonts within this directory structure (either within an existing directory or in a newly created one).


    If the specified font or default font does not contain a specific unicode character or if it is unavailable, the character is taken from a fallback font according to the following priority:

    • Locale-specific font

    • ROOT font if locale not set

    • Generic font, searched by order set in the fallback table

  5. Repackage the adobe-fontmanager.jar file.

  6. Repackage the adobe-livecycle-[appserver].ear file and then redeploy it either manually or by running Configuration Manager.


Do not use Configuration Manager to repackage the adobe-livecycle-[appserver].ear file because it will overwrite your modifications with the AEM forms default values.

Dit werk is gelicentieerd onder de Creative Commons Naamsvermelding/Niet-commercieel/Gelijk delen 3.0 Unported-licentie  De voorwaarden van Creative Commons zijn niet van toepassing op Twitter™- en Facebook-berichten.

Juridische kennisgevingen   |   Online privacybeleid