Acrobat Reader errore con font ArrowNARROW

Se aprendo tramite Acrobat Reader un ODF vi viene segnalato un errore relativo alla mancanza del font ArrowNarrow non riuscendo quindi a visualizzare le parti del documento scritte con tale font, le cause possono essere diverse. Inoltre l’issue è legato ad un OS o ad una versione particolare di Acrobat Reader.

Una prima causa può essere legata alla versione del font come indicato nella KB di Acrobat Arial Narrow unavailable, incomplete:

Reason
In revising Arial Narrow, Microsoft added new name fields for the “preferred” family and style, andintroduced the behavior wherein all four Arial Narrow fonts are labeled as having the same style (e.g. “Narrow” instead of “Narrow Bold Italic”).

Solution 1 : Install an updated version from Microsoft.

  1. Close any Creative Suite application
  2. Go to http://support.microsoft.com/kb/956514 and follow the installation instructions.
  3. Search your system for adobefnt*.lst and delete any of these files; example, adobefnt02.lst.
  4. Restart the application.

Solution 2: ReplaceArial Narrow version 2.35 with previous version font files (version 2.30 or earlier).

  1. Quitall Adobe applications.
  2. Locate the Arial Narrow font files in the C:\windows\fonts folder and confirm the version of the font files:
    – ARIALN.TTF- ARIALNB.TTF

    – ARIALNBI.TTF

    – ARIALNI.TTF

  3. Double-click the font file to open the font preview and display the version number.

Nel caso che ho analizzato io ho risolto il problema in modo differente dal momento che non volevo eseguire un downgrade del font  per non causare eventuali problemi ad altre applicazioni. La procedura che ho utilizzato è stata semplicemente quella di copiare con privilegi amministrativi i file del font ArialNarrow(ARIALN.TTF, ARIALNB.TTF, ARIALNBI.TTF e ARIALNI.TTF) da %WinDir%\Fonts in %ProgramFiles(x86)%\Adobe\Reader 11.0\Resource\Font.

Come si può leggere nel documento Accessing and embedding fonts using Distiller dell’help online di Adobe tale cartella viene utilizzata come primo punto da cui avviare la ricerca dei font:

When converting a PostScript file to PDF, Distiller needs access to the file’s fonts to insert the appropriate information in the PDF. Distiller first searches the PostScript file for Type 1, TrueType, and OpenType fonts. If the font isn’t embedded in the PostScript file, Distiller searches additional font folders. Distiller searches the following font folders in Windows:

  • /Resource/Font in the Acrobat folder
  • /Windows/Fonts
  • Distiller searches the following font folders in Mac OS:
  • /Resource/Font in the Acrobat folder
  • /Users/[user name]/Library/Fonts
  • /Library/Fonts
  • /System/Library/Fonts
    The Acrobat installation includes width-only versions of many common Chinese, Japanese, and Korean fonts, therefore Distiller can then access these fonts in Acrobat. Make sure that the fonts are available on your computer. (In Windows, choose Complete when you install Acrobat, or choose Custom and select the Asian Language Support option under the View Adobe PDF category. In Mac OS, these fonts are installed automatically.)
    For information on including fonts in a PostScript file, see the documentation that came with the application and printer driver you use to create PostScript files.
    Note: Distiller does not support Type 32 fonts.

To specify other font folders for Distiller to search, in Acrobat Distiller, choose Settings > Font Locations. Then in the dialog box, click Add to add a font folder. Select Ignore TrueType Versions Of Standard PostScript Fonts to exclude TrueType fonts that have the same name as a font in the PostScript 3 font collection.

Note: To provide Distiller with access to a font folder that has been moved, use this dialog box to remove the folder listed in its old location and add it in its new location.

Una terza soluzione che non ho provato potrebbe essere quella di eliminare o rinominare i file che contengono l’enumerazione dei font: %appdata%\local\Adobe\Acrobat\11.0\Cache\AcroFnt*.lst a riguardo si veda il post LiveCycle ES: what is the AdobeFnt11.lst file? sul blog di David McMahon (Sr.Technical Account Manager at Adobe Systems – Germany).