solerous
-
Posts
11 -
Joined
-
Last visited
Posts posted by solerous
-
-
Since the text boxes were creating that odd ghosting which replicated onto the other master template, I tried going back to a paragraph style. It seemed promising at first, but it doesn't work with all the letters. Even though it's set to show drop caps for the first 3 lines, sometimes it only does it for two and then overlaps the third line.
-
6 minutes ago, MikeW said:
May I ask what the font for the DCs is?
Whistler from Letter Head Fonts
-
22 minutes ago, thomaso said:
Yes, an additional text box makes it a little cumbersome. So, why preferring that workflow if it feels hard while there are alternatives?
I can't get the drop cap font to move up vertically the way you showed. Using a text box was the only way I could get it to work right. If I adjust the baseline, it affects the regular text as well.
-
1 minute ago, thomaso said:
For text editing and styling you don't need to detach.
Because of the way the text overlaps, I actually need to change the size of the text box on each page. That's why I need to detatch.
-
Oh, no, I've hit another snag. In creating a text box for the Drop Cap, I've somehow mucked up my master file. See the attached images for the problem. I need to have a Facing template to account for whether the chapter starts on the left or right hand page (to ensure correct margins). But even though I assign the "Main Text" master (which has no drop caps and a standard text block) the ghost of the drop cap text box remains. Worse, I can't even remove it via detatching from the master. It's like the text is underneath the master and both templates are being applied.
-
Thanks Mike and Tomaso. Each letter in this font has a different "overlap" so in the end I think I will just have to do them by hand. It will be a bit hard having to detatch each page to adjust for each letter, but I don't see any way around it.
-
18 minutes ago, walt.farrell said:
Change the font you're using?
It looks like I may just have to do them by hand, then. Thanks for your suggestions and help.
-
Okay, that explains why it's not in the text style options. So, is there a way to make Section Name lowercase?
-
Thanks, Bruce, for the reply. I was kind of afraid you would say that about the drop caps. I think I may just insert a single text box in there and do it by hand, then, typing in the letter manually.
As for the section name, this font has small capital letters as the "lowercase". So in another font, it would be:
chapter i
Section Name
(the O and the R are for the "<" and ">" characters)
I can highlight that placeholder code "<Section Name>" and choose Text > lower case but it does absolutely nothing. It works if I choose all caps, though. It's just weird. And why is the option for "lowercase" not in the styles menu? It feels like these are oversights, but I am new to the software so maybe I'm missing something.
-
I am new to Affinity publisher. This is my first post.
The software has so much promise, but I'm getting tripped up on a few things.
1) How do I limit drop caps to the first paragraph of a section of text? Also, how to I keep the Drop Cap from overlapping the text. If I use certain fonts it worked, but on other decorative fonts it overlaps.
2) How do I choose Capitalization > Lowercase for a style? It doesn't seem to exist in the style options, though it is available to be used manually via the menu.
See the attached screenshots for the problems. There is also an additional issue with the chapter start master page that if it starts on the left hand side the margin is messed up (it doesn't adjust to the correct margins).
Thanks.




Drop Caps and Lower Case Section names
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
Thanks, Thomaso, for all the help. It's very much appreciated. I think at this point I've resigned myself to using text boxes individually inserted onto each page. This is regrettable since it creates extra work and may not respond to changes in pagination (when a chapter moves from the left page to the right, etc.). Hopefully they will make this more intuitive and robust in a future update.