Skip to main content
Known Participant
April 14, 2020
Question

Feature Request for Glyph &Uppercase numbers (lining figures) are not possible with uppercase button

  • April 14, 2020
  • 1 reply
  • 1642 views

I really miss selecting alternative numbers and glyphs in Adobe XD. Especially is there a bug in the uppercase button: If I select this the numbers should change from old-fashioned figures to lining figures (uppercase numbers). See attached.

 

{Renamed By MOD}

1 reply

Rishabh_Tiwari
Community Manager
Community Manager
April 14, 2020

Hi there,

 

Thanks for reaching out. It does sound like a great feature request to have access to Glyphs of a given font style. We have received a similar request on Adobe XD UserVoice page, I'd request you to please share your comments and upvote this request: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/13719966-glyphs-palette

 

If that's not what you were looking for, I'd request if you can explain a bit more about the concern, we'll try our best to help you with that.

 

Regards

Rishabh

geshonsAuthor
Known Participant
April 14, 2020

The feature request is 4 years old … and the problem is more than a bug then a feature request. XD has the uppercase-function. But if I select this the numbers have to be transformed automatically in normal lining figures, because with old-fashioned figures/numbers the "uppercase" makes no sense … It this way my hands are tied while designing … I can't design what I want. My font Meta Pro has this old-fashioned figures/numbers. But often there are the normal lining figures are needed, because in heading etc. it looks weird if the first glyph (number) is a small old-fashioned figure/number. But how to select this? I can't paste it in from Photoshop or something else. It's not possible. I have to tell my client: "Sorry but my designing software is crazy, I can't show you the design how I like to. You have to imagine how the design should be …" That's really bad … 😞

Luco Rodrigues
Participant
September 11, 2023

6 years now and the problem persists. Whoa. Shame on you, Adobe.