Skip to main content
W
Wing2024
Participant
February 27, 2024
Question

Character Encoding issue with a certain Asian languages and fonts

  • February 27, 2024
  • 2 replies
  • 1054 views
 

I have a set of pdf leaflets in Hindi, Nepali, and Thai. Acrobat's Accessibility Checker fails all of the PDFs on character encoding.
The fonts are all OK, and the .ps/Distiller doesn't work.

 

    2 replies

    S
    shanper215
    Participant
    July 3, 2024

    I've been running into the same character encoding issue. Fonts are fine on the PDF, but they do have display issues when reviewing them within the Accessibility Tags panel.

     

    Have you found anything that works or a workaround?

    T
    Tariq Dar
    Legend
    April 22, 2025

    Hello, 

     

    You may try using the Preflight tool for font Fix-ups or accessibility fixups: https://adobe.ly/4lI4J7z

     

    You can use the Preflight tool to fix many errors in a document. You add error corrections, called fixups, to a profile to do this. The fixup automatically corrects the problem, if possible, or provides information so that you can correct the problem in the source file. A profile with a fixup has the gray wrench icon next to it. An outline of a wrench means no fixups are associated with the profile.

    Preflight includes several predefined fixups that you can add to a profile. These cover a broad range of errors that affect color, fonts, images, print production, compliance with international standards like PDF/X and PDF/A, and other areas. Preflight also includes a toolkit for creating your own single fixups.

     


    ~Tariq

    L
    Lexidoc
    Participating Frequently
    February 29, 2024

    I am finding this too with PDFs in Bengali, Hindi, Punjabi etc. The job I have is an update to some leaflets from two years ago which passed Acrobat's checker then but don't now (character encoding), so it looks like there have been some updates.

     

    However, if I run the same PDFs through PAC they all pass for encodings/fonts for both PDF/UA and WCAG so I'm not sure what's happend in Acrobat to make them fail. Support for this issue from Adobe is very thin indeed :(.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices