Jump to content

Recommended Posts

Posted

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.

 

Screenshot 2025-02-28 160236.png

Posted

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

Posted

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.

Screenshot 2025-02-28 201416.png

Posted

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.

Posted

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...

Posted

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.

Screenshot2025-02-28at8_08_38PM.png.ab5f384c478968bfb9ed4843da5a3ba6.png

Posted

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)

Clipboard 1.jpg

Posted

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.

 

Posted

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.

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.