Hi Joel
Thanks you so much for trying this - i followed your instructions but when exporting i still get the error - could you send me the indesign file that you managed to output this from so i can compare other settings to see if this is in combinationwith something else?
thanks
Alan
No problem! Let me tell you what I tried. I might be remembering some of the details incorrectly, but here's basically what I did:
1) First I looked at your INDD and saw that it really wasn't set up for accessibility. So I first made four paragraph styles, one for each of your test fonts. I made sure that each one was marked as "Bangla (India)" and that each paragraph was mapped to the P tag in the Export Tagging.
2) Then, at export, I chose "Interactive PDF" and chose "Bangla (India)" in the Language dropdown in the Advanced section of the "Export to Interactive PDF" dialog.
3) That didn't work, so I made more coffee. While doing that, I realilzed that almost every time I've had a problem with any kind of complex script encoding recently, it's been the fault of HarfBuzz. So I went back to my INDD, turned on the Legacy Character Shaping preference, and exported a PDF. That worked fine with no character encoding failure.
4) I then said to myself, "I wonder if it's all HarfBuzz' fault." So I went back to your original INDD, turned on the Legacy Character Shaping pref, made no other changes that I recall, and exported a fresh PDF, with the language "Bangla (India)" selected in the "Export to Interactive PDF," which I then attached to my last post, here. So I decided "Oh, all that other accessibility work was pointless, Alan just needs to turn on the Legacy Character Shaping Engine." At that time I didn't remember that I'd left the language setting in the "Export to Interactive PDF" dialog, so that may well be the missing piece you'd need to make this work. Honestly, it might be worth testing with the language set in the "Export to Interactive PDF" dialog, but without the Legacy Character Shaping Engine, to see if it really is just declaring the language that is resolving the issue.
That being said, I encourage you to not bother to try testing accessibility in PDF output from InDesign without doing all of the prepwork. Something that passes muster in Acrobat might fail when you run it through CommonLook or PAC 2024. If you're only using Acrobat to test, then something that passes muster in Acrobat might fail when it makes it to the end user. So: I'd suggest that you make a full set of paragraph styles, declare language everywhere you can, and maybe map your styles directly to H1 and P tags in the Export Tagging section (I don't know how well the Automatic setting works, I've just been specifying them manually).
AdChoices