mick0005 Posted February 28 Posted February 28 I noticed that with some forms of automatic capitalization, the automatic hyphenation doesn't work. This applies to "(only) small caps", "(only) petite caps" and "title font". The hyphenation only works as expected when using "Capitalization". See also my screenshot as an example, The problem is independent of the Font I use. I hope for a remedy. Mir ist aufgefallen, dass die automatische Silbentrennung bei einigen Formen automatischer Großschreibung nicht funktioniert. Das gilt für "(Nur) Kapitälchen", "(Nur) Petite Caps" und "Titelschrift". Die Silbentrennung funktioniert nur bei "Großbuchstaben" wie erwartet. Siehe hierzu auch meine Bildschirmkopie, das Problem tritt bei allen Schriftarten auf. Ich hoffe auf eine Lösung. Quote
MikeTO Posted February 28 Posted February 28 Could you please share a test document here for review? I can't duplicate this problem with English or German text. I formatted text as All Caps, Small Caps, and all uppercase (true uppercase, not all caps), and in all cases it hyphenated correctly. Good luck Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
mick0005 Posted February 28 Author Posted February 28 Here it is, Arial has funnily another kind of capitalisation called "Unicase" (where auto-hyphenation doesn't work either). auto-hyphenation.afpub Quote
MikeTO Posted February 28 Posted February 28 All of the text in your test doc is hyphenated for me. Here's what I'm seeing, three hyphens in the paragraph identified as not working. What are you seeing when you open it? Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
mick0005 Posted February 28 Author Posted February 28 That's what I see, no hyphenation in the right colum. I use Publisher 2.6.0 on Windows 11 and I had that problem on previous versions of Publisher, too. Quote
MikeTO Posted February 28 Posted February 28 We're getting different results - the word BLINDTEXT in the first line of the second paragraph on the left is hyphenated in my screenshot but not in yours. Which hyphenation dictionary do you have installed and are you on Mac or Windows? Unless you've installed your own dictionary, it should be dated 2017-01-12 (you can open the dictionary in a text editor to verify this). Note: you chose a different font for the bottom right of your screenshot. Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
mick0005 Posted February 28 Author Posted February 28 I have installed and are working with Publisher 2.6.0 on Windows 11. I really don't know how to find out which dictionary I have installed as I don't know where to find that file or that information I'm afraid. Note: I didn't choose a different font for the bottom right, it's an open type feature called "unicase" ('unic') the Arial font comes with on Windows. Don't know if anyone ever used that because it looks a little peculiar... Quote
MikeTO Posted March 1 Posted March 1 If you haven't installed your own dictionary then you should have the same one as me. This is peculiar. I rebuilt your doc in 2.5.7 so I could compare versions but it worked identically. auto-hyphenation 257.afpub This is how it appears for me in both 2.5.7 and 2.6.0 - everything is hyphenated. Open this doc and check Character > Language > Spelling - is it set to German or Unknown de-DE? If it's unknown, fix it. Try changing Language > Hyphenation from Auto to German. That shouldn't make a difference but give it a try. Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
mick0005 Posted March 1 Author Posted March 1 I gave it a try, it's still no difference, hyphenation doesn't work with "all small caps" and "small caps". One thing I noticed: Your example doesn't show real small caps but "fake" ones (scaled capital letters of the font). I didn't notice that on the first screenshot of my file you posted here. But that seems to lead us to where the problem may lay: Auto hyphenation simply doesn't work with Open Type features! I tried different settings for spell checking and stumbled upon a strange behaviour which seems to confirm my suspicion: When I turn Spell Checking to "none" the text switches from real small caps to fake ones and the auto hyphenation works then. That's of course not a solution of my problem: I like to have auto hyphenaton while using Open Type features like small caps, titling etc. The problem may be: auto hyphenation doesn't work when there is an substitution of glyphs provided by an Open Type feature and it's not a fault of the font (I tried several) but of Publisher which doesn't "know" how to handle those replaced glyphs for auto hyphenation. My example shows what happens, when I swich of spell checking (it should not change the appearence of the text nor switch off Open Type features, what it apparently does) Quote
MikeTO Posted March 1 Posted March 1 You right, it is the OpenType substitution that is causing the problem. It's hard to compare cross-platform with Arial because we don't have as full-featured version of it on macOS. I switched the test document to EB Garamond and now I can see your issue. EB Garamond is cross platform and free and has lots of OpenType features so it's often used for testing. auto-hyphenation 257-2.afpub It turns out this was reported last fall, too. Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
mick0005 Posted March 1 Author Posted March 1 O.k., thanks for your afford, I hope it will be solved soon. Sorry I didn't find the report from last year, sometimes it's not easy to choose the right search terms. Quote
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.