Adobe Caslon Pro: Glyph as bullet does not function
InDesign version 18.2.1 (Windows 10 x64). I would like to use a glyph as a bullet (the opentype digit 3 of Adobe Caslon Pro - an acorn). In the paragraph style box for my "Bulleted list" style, I am trying to add the bullet. When I click "add" and then click "ok," a standard round black dot appears in my list of bullet characters to choose from. If I try to add my preferred glyph (or any of the other opentype glyphs from the font's set, for that matter), the program tells me: "The selected bullet already appears in the Bullets and Numbering dialog box with this font and style association. Specify a different font or style, or select a different bullet." I also cannot add the glyph as bullet manually in the lists window. In short, adding a glyph as bullet is not functioning. There has been extensive discussion of this issue on the Adobe Support Community. Many people have suggested numerous solutions, but none have worked. For steps attempted to resolve the issue, see: https://community.adobe.com/t5/indesign-discussions/glyph-as-bullet-not-functioning-in-paragraph-styles/m-p/13723795#M523395. One user has pointed out the encoding of ornaments in the most recent version of the font as an issue. I hope that you will consider remedying this apparent bug. Thank you.
Adam Bresnahan
shared this idea
Thanks for reporting the issue. We're reviewing this.
--
Adobe InDesign team
-
Bevi Chagnon | ACP
commented
Here's the glyph chart for Adobe Caslon Pro.
-
Bevi Chagnon | ACP
commented
There's something not correct with accessing the ornaments in Adobe Caslon Pro.
When we've used this font in accessible PDFs as just a glyph in the content stream (original layout file in InDesign), it is voiced by screen readers as "3" rather than as an ornament or a specific Unicode name.This isn't the usual pattern for Unicode fonts. In the screen capture, A Caslon Pro's ornaments use the same Unicode codepoint as alpha numerics.
As an example, Minion Pro encodes its ornaments as 2022 (Bullet), shown in the 3rd screen capture, and they work flawlessly.
.
