Compositor K Posted August 1, 2023 Share Posted August 1, 2023 I've looked around the Support site, and can't find anything about this in V2. (Am I missing something?) In V1, there were apparently problems with ligatures not being created when the text was justified, even though ligatures were enabled in the text style. In V2, I'm getting the ligatures. (The spacing around them isn't entirely satisfactory, same as in V1, but I can live with that). However, I'm getting some very strange behavior, which makes it impossible to place a cursor to make corrections. This is not a grave problem so far--I can make the text flush left, make the corrections, and change it back to justified. But perhaps it's worth bringing it to someone's attention. Standard ligatures are enabled in the paragraph style, other ligatures are disabled. Changing the font (Trump Medieval OTF) to Minion Pro doesn't eliminate the problem. 1. I've circled the problem ligature and the location of the cursor. 2. This is the result when I press delete-backwards. The 'n' was deleted, but the cursor isn't where it should be. 3. Another example. Note cursor placement, and the word 'sed'. 4. This is the result when I press delete-backwards. 5. I also can get the cursor to apparently move outside the column. (It's not outside the text frame here, but in the gutter to the right of a column.) Any information about the status of this problem would be appreciated. Thanks for your attention. Quote ---------------------------------------------------------------------------------- Affinity V2.1.1 | macOS 13.3.1(a) Ventura | 24" iMac M1 Link to comment Share on other sites More sharing options...
Oufti Posted August 1, 2023 Share Posted August 1, 2023 Could it be related to this reported bug? Symptoms seem similar… Quote Affinity Suite 2.5 – Monterey 12.7.5 – MacBookPro 14" 2021 M1 Pro 16Go/1To I apologise for any approximations in my English. It is not my mother tongue. Link to comment Share on other sites More sharing options...
Compositor K Posted August 1, 2023 Author Share Posted August 1, 2023 Thanks! This looks like it might even be the same thing. One common factor is that the problem occurs in justified text. Another, perhaps, is the presence of ligatures or other possibly combined characters. I've found the same problem in paragraphs containing an umlauted o (which also appears in the examples in Scythian's bug report). I don't know whether or not the ö is a pre-composed character in that font. This also seems to have some relation to a problem I noted in another post, titled "Problem with "combining accent" use." In the bug report thread, it was noted that the issue has been forwarded to the developers. I'm looking forward to future developments. Callum 1 Quote ---------------------------------------------------------------------------------- Affinity V2.1.1 | macOS 13.3.1(a) Ventura | 24" iMac M1 Link to comment Share on other sites More sharing options...
Staff Callum Posted August 2, 2023 Staff Share Posted August 2, 2023 It looks as though this is the same issue I have added an extra report to the original bug report and will update this thread once I have more info. Thanks C Quote Please tag me using @ in your reply so I can be sure to respond ASAP. Link to comment Share on other sites More sharing options...
Compositor K Posted August 2, 2023 Author Share Posted August 2, 2023 Thank you Callum! I've since found that the same problem occurs in centered text. Again, I'll be very interested in further news whenever it comes. Quote ---------------------------------------------------------------------------------- Affinity V2.1.1 | macOS 13.3.1(a) Ventura | 24" iMac M1 Link to comment Share on other sites More sharing options...
Chicky Posted November 6 Share Posted November 6 Not sure if this is the same issue, but I'm writing a story with a character named Raffin and the ffi ligature doesn't always properly engage in Publisher v2. Sometimes it will ligate correctly right after I finish typing the second f and the i, and sometimes it will not. Sometimes it will look odd in the text for a little while and then fix itself later on. It seems like the default behavior of special ligatures (here I am using Arno Pro Regular) is inconsistently applied. Quote Link to comment Share on other sites More sharing options...
walt.farrell Posted November 6 Share Posted November 6 11 hours ago, Chicky said: Not sure if this is the same issue, but I'm writing a story with a character named Raffin and the ffi ligature doesn't always properly engage in Publisher v2. Sometimes it will ligate correctly right after I finish typing the second f and the i, and sometimes it will not. Sometimes it will look odd in the text for a little while and then fix itself later on. It seems like the default behavior of special ligatures (here I am using Arno Pro Regular) is inconsistently applied. Is it always in the first line of a paragraph, as you show in that screenshot? If so it might indeed be related, and @Callum could add your situation to the report, too. (As an aside: personally, I do not like the way that Raffin looks with that R with its long tail. The space between the bowl of the R and the a is too big, to my eyes. With it being used so often, I would pick a different font, or a different variation of the R if one is available ) Quote -- 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 18.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
Chicky Posted November 6 Share Posted November 6 Thanks for the note. Looking at it, I DO think it's always in the first line of a paragraph. And thanks for your note on the font; it's actually a lot easier on the eyes at 11pt than it is at the zoomed-in. Fortunately, this is a minor character. And Arno is generally gorgeous and has a wealth of typographic features. It's interesting how even in our favorite fonts there are some weird outliers and clunky kerning pairs! walt.farrell 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.