osang Posted January 20, 2019 Share Posted January 20, 2019 A bug, but in Positioning and Transform the superscript is working. Link to comment Share on other sites More sharing options...
walt.farrell Posted January 20, 2019 Share Posted January 20, 2019 Not a bug, probably, @osang The Typography settings only apply to a subset of characters implemented by the font. Positioning and Transform should work for all characters, as it's handled by Affinity, not the font. But the results may not be as good as Typography can provide for the characters provided by the font. -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
osang Posted January 21, 2019 Author Share Posted January 21, 2019 23 minutes ago, walt.farrell said: Not a bug, probably, @osang The Typography settings only apply to a subset of characters implemented by the font. Positioning and Transform should work for all characters, as it's handled by Affinity, not the font. But the results may not be as good as Typography can provide for the characters provided by the font. Strange, but in Designer 1.61, same setting and font, the superscript is working. Link to comment Share on other sites More sharing options...
walt.farrell Posted January 21, 2019 Share Posted January 21, 2019 Interesting. Might be one of the areas where 1.7 changed. Or, might be a bug -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 17.7, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.7 Link to comment Share on other sites More sharing options...
A_B_C Posted January 21, 2019 Share Posted January 21, 2019 The explanation for this is the new implementation of the superscript and subscript function. Have a look here: https://forum.affinity.serif.com/index.php?/topic/67116-superscript-and-subscript/&tab=comments#comment-347521 You will always have to use Character Panel > Positioning and Transform > Superscript to have “fake” superscripts when the respective glyphs are not in the font. The standard Arial typeface that comes with macOS doesn’t have them. Cheers, Alex 3Dshark, Alfred, paschulke2 and 2 others 2 3 Link to comment Share on other sites More sharing options...
3Dshark Posted December 10, 2019 Share Posted December 10, 2019 Thanks A_B_C ! I would never have noticed the "fake" superscript, well hidden away A_B_C 1 Link to comment Share on other sites More sharing options...
Recommended Posts