Superscripts not working?

[Minus44]

I reported this in the Bug section, but I thought I'd mention it's also not working in beta 146 either. The problem with superscripts seems to affect only the desktop versions (on macOS... I'm not sure about Windows versions) for Photo AND Designer. See thread below: 

 

Apologies if the cross-post is unnecessary. Please delete if already reported and unnecessary.

Superscripts.afphoto

[MaxWaterman]

The problem is still actual. I've found a similar request here. Anyone can support?

[Minus44]

8 hours ago, MaxWaterman said:

The problem is still actual. I've found a similar request here. Anyone can support?

The answer seems to be that this is "by design." My further investigation revealed that my original assumption was actually WRONG. I'd assumed that common fonts such as Arial or Times New Roman included many superscript and subscript fonts, when in fact they only contain a few. Therefore, Affinity Photo is designed to "fake" these fonts as desired, providing controls to access the REAL sup/sub font, as well as generate fake versions. 

[Alfred]

21 minutes ago, Ulysses said:

The answer seems to be that this is "by design." My further investigation revealed that my original assumption was actually WRONG. I'd assumed that common fonts such as Arial or Times New Roman included many superscript and subscript fonts, when in fact they only contain a few. Therefore, Affinity Photo is designed to "fake" these fonts as desired, providing controls to access the REAL sup/sub font, as well as generate fake versions. 

For “font”, read “glyph” throughout (except for the phrase “common fonts”): a font is a collection of glyphs/characters. For example, my copy of the font Arial Bold contains a complete set of superscript numerals, but the only superscript letter is n.

[Minus44]

9 hours ago, Alfred said:

For “font”, read “glyph” throughout (except for the phrase “common fonts”)

Ahhhhh, thank you! Good catch!  

[Patrick Connor]

Sorry.

Thank you for reporting a problem using the pre 1.8.0 beta builds. It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. 

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

• Report a Bug in Affinity Designer
• Report a Bug in Affinity Photo
• Report a Bug in Affinity Publisher

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the release build.