Copy link to clipboard
Copied
Dear all,
I am giving the finishing touches to a scholarly publication on classical music. The document will include a conspicuous musical part and extensive editorial and critical notes both at the beginning and at the end of the book.
Now, I am aware that aligning to baseline in multiple column works gives them a cleaner look but, in this specific case, with several images and quite a few section titles, I feel that doing so makes everything look a bit colder and encyclopaedic. It certainly look fine but I wonder if you could give a look at the two pdfs attached below and tell me both what you think of it and any additional feedback I could have overlooked.
Right now the body text is 11pt in size and the leading is 16.5 (150%). I have set up the baseline to repeat every 16.5 pt (correct?) as anything less would make lines appear one every two baselines (it took me a while to understand this). Of course, this causes all other paragraph styles (whose spacing was governed by Space before/after values) to always skip a line. That is, every new section will have a 16.5+ space above in any case. I wonder if this is correct or if I set something wrong up.
You will have already noticed that I am not super-confident with this, but tutorials on long-form documents are rarer and rarer these days.
Thank you for your time and help!
Copy link to clipboard
Copied
Right now the body text is 11pt in size and the leading is 16.5 (150%). I have set up the baseline to repeat every 16.5 pt (correct?) as anything less would make lines appear one every two baselines (it took me a while to understand this). Of course, this causes all other paragraph styles (whose spacing was governed by Space before/after values) to always skip a line. That is, every new section will have a 16.5+ space above in any case. I wonder if this is correct or if I set something wrong up.
Yes, all this is absolutely correct. That's the way it has to be done.
According to me, but (of course) it's subjective: version with text aligned on baseline grid is far better than the other one.
Copy link to clipboard
Copied
Hi! As a book designer myself, I vote to leave the baseline grid on. It just looks so much more professional (IMHO). BTW, you've done a lovely job.
Copy link to clipboard
Copied
Thank you so much, Susan.
I'm self-taught in this—with huge help from this forum and from the BYOL courses—so every time something doesn't work I feel so much outside of my comfort zone.
I will keep working on this copy and convert the paragraph styles until they look good.
For now the only PS that I have kept not aligned to baseline are the lists, but I will keep experimenting. I'm already 90h in this project, a couple more should not hurt!
Copy link to clipboard
Copied
Here I am, 2 hours later, with a new version.
I have to say it: I'm surprised at how sleek it looks now. At first sight, it looks like the text is breathing less and it is more cramped, but the professional look is unmistakable!
Some issues I ran into were that the musical symbols in titles had some spacing options that prevented them from being in the top line (see screenshot attached). I solved that by editing, in the parent page, the baseline options for the text frame from Ascent (default) to Baseline. This had the side-effect of causing a few other headings not liking the first line. I then locally changed only those text frames to have Ascent.
In the attached PDF I have added a few comments for you to check which are the few doubts I still have about this design.
I would be immensely grateful if you could look at this when you get a chance.
Thank you so much! As always, I'm deeply enjoying the learning process.
Copy link to clipboard
Copied
Hi again! I hope you don't mind my giving you some pointers as well as answering your queries.
Note 1: Size looks fine. For the ToC, only the page numbers in roman numerals should be italic. Any regular numerals should be Roman (not italic). This goes for the running heads as well; you can do this manually in the parent page or apply an Italic character style to the roman numerals.
Note 2: You're right, those few lines could be tighter. You can adjust the paragraph style to not apply baseline grid, assuming you have a separate paragraph style for those lines (which you definitely should).
Suggestions:
Paragraphs following a heading should be flush left, no indent in the first lines. It's important to have a separate paragraph style for this, everything the same as the body style but no first line indent.
Footnote callouts (the numbers in the text) should follow the periods with no spaces.
What font are you using? I see you've used small caps in the Exercise headings, but it doesn't look as if the font contains small caps, so it's making its own, but they are too light. You could play around with using one weight higher than the headline text, but only if you have a few weights to try, because making them bold would probably be too dark. If you only have Roman, italic, and bold, you probably shouldn't use small caps.
In your screenshot, you marked that you had to do a lot of fiddling to get the # sign to align with the baseline. There's a nifty tool in the top bar that lets you shift the position of text up or down point by point (see below). Notice that the capital C is a point higher than the rest of the letters. This might be easier for you.
Lastly, if at all possible it's good practice to "balance" the pages at the bottom. If you want to spend the time making sure the pages all end on the same line, you can get a how-to for tracking and kerning at this link: https://helpx.adobe.com/indesign/using/kerning-tracking.html .
Good luck! And please, if I've given any advice that anyone in the group disagrees with, please correct me! I'm not a true "expert," just a lowly worker bee 🙂
Copy link to clipboard
Copied
Hey! Sorry for being slow, but here I am.
Thank you so much for your feedback, it is incredibly valuable to me!
Note 1: Size looks fine. For the ToC, only the page numbers in roman numerals should be italic. Any regular numerals should be Roman (not italic). This goes for the running heads as well; you can do this manually in the parent page or apply an Italic character style to the roman numerals.
For the ToC, since I used the same paragraph style for the same kind of headers, I have had to manually change the three entries with arabic numerals to use Regular style. For the preface itself, are you also suggesting that the roman numerals in there should be italics? I use this same parent page both for the Editorial Notes (before the musical part, with Roman numerals) and for the Critical Notes (after the music, with Arabic numerals). Were I to follow your suggestion I think I would need to make a separate parent page with italic numbers for the Editorial Note. Is that correct?
Note 2: You're right, those few lines could be tighter. You can adjust the paragraph style to not apply baseline grid, assuming you have a separate paragraph style for those lines (which you definitely should).
Awesome, thank you! Yes, I have almost too many paragraph styles — perhaps there is not "too many" when it comes to PS, though 🙂
Suggestions:
Paragraphs following a heading should be flush left, no indent in the first lines. It's important to have a separate paragraph style for this, everything the same as the body style but no first line indent.
Thank you for this! It looks so much better.
I have created a copy of the main body PS and set it to bear no indent. Trying to make things quicker, I applied it as "Next Style" to the various Headings used in the Preface, hoping that it would automatically fix all of them. It did not. There are a few reasons I think that why that may be but I am not sure. Is it normal for this to behave like this?
I have also set the next style for the no-indent body to be its indented version but, upon pressing Return, it didn't work. This I really do not know why. My intuition is that it may have to do with parenting, the no-indent being a copy of the indent one, but that may be unrelated.
Any idea?
Adding additional (new) text to the end of the preface worked as intended though. So, may it be that existing text is not being influenced by these changes?
Footnote callouts (the numbers in the text) should follow the periods with no spaces.
I'm not sure I agree with this. I am using British English with an academic style and, from what I have learned, the callout goes before the period in this case. It goes after the period in American English, though. I am no expert in this, but it is what I have read around and been advised to do. Ready to be contradicted!
What font are you using? I see you've used small caps in the Exercise headings, but it doesn't look as if the font contains small caps, so it's making its own, but they are too light. You could play around with using one weight higher than the headline text, but only if you have a few weights to try, because making them bold would probably be too dark. If you only have Roman, italic, and bold, you probably shouldn't use small caps.
Very interesting remark.
The font I am using is Rooney Sans for the inner cover and Rooney for the text. They are both Adobe Fonts. How can one check that a font has or doesn't have small caps? This font has Light, Regular, Medium, Bold, Heavy, and Black so plenty to play with. Starting from Bold, I set the lowercase letters to Heavy and, while a big too fat to me, it looks more cohesive. Do you think that leaving it as it is would be a bad design choice?
Generally speaking, I wasn't using small caps in my design before so I may just as well revert to ordinary capitalisation. What do you think?
In your screenshot, you marked that you had to do a lot of fiddling to get the # sign to align with the baseline. There's a nifty tool in the top bar that lets you shift the position of text up or down point by point (see below). Notice that the capital C is a point higher than the rest of the letters. This might be easier for you.
Oh, I have fiddled with baseline shift more than one ever should but nothing, it would not bulge. Perhaps the font used to render the musical symbols is not too prone to collaborating but, in any case, the only thing that worked reliably was editing the Text Frame Options so that the Baseline type would be either of Ascent, Baseline, or x-height. Sometimes one would work, sometimes the other would work. Not knowledgeable enough to know or understand why at this point. I've not yet had enough Nigel French in my InDesign life 🙂
Lastly, if at all possible it's good practice to "balance" the pages at the bottom. If you want to spend the time making sure the pages all end on the same line, you can get a how-to for tracking and kerning at this link: https://helpx.adobe.com/indesign/using/kerning-tracking.html .
This is another very good point.
The first thing I noticed is that the chosen baseline does not divide perfectly into the text frame, resulting in the last line always being empty. Not a big deal since this is consistent throughout. I would try to make it more precise in a future project, though.
I asked myself several times why the last few lines of several columns would remain empty but the only reason I found as a possible culprit would be my paragraph style's Keep Options, which are like this to avoid orphaned lines:
These settings certainly do what I tasked them to, but have the side effect that you mentioned.
I am not sure how changing the tracking-kerning would help here; perhaps making paragraphs stretch to the end of the column? Or something else?
Going page by page in the new version attached below (using PDF page number):
Kindly let me know what you think of this, no rush at all!
Thank you once again for your fantastic feedback!
Copy link to clipboard
Copied
Note 1: Yes, you should make different parents for pages with Roman numerals and Arabic numerals (those with Roman numerals get italic page numbers, those with Arabic pages get Roman numbers—not too confusing, right? 🙂
Note 2: There really aren't "too many" para styles; just depends on your text. In many of my documents, I might have dozens. It's alway best to have para styles rather than manual styling.
I've had similar poor luck with "Next style" settings but have just never taken the time to explore; I just apply the proper para style. BTW, here's a hint: I set a keyboard shortcut to all my frequently used para styles, so as I go through the text, I only have to select the paragraphs in question and press the keyboard shortcut. To create the shortcuts, edit your para styles, and on the first screen you'll see where to set this up (see below).
Next, I love small caps when the font contains them. To check, highlight the font to which you've applied Small caps, then see below (BTW, thanks to Jongware for the answer to this in 2010; I created my own screenshot to avoid copying):
Re baseline shift, I don't have your musical font, so I can't check this, but we all need more Nigel French!!!
As for balanced pages, as my dad used to say, "Everything's a tradeoff." It's much more important to keep the first and last two lines together than it is to balance the pages. Focus on balancing pages in your next project (IMHO). Please, anyone with a better answer, please chime in!
Happy to help, and please remember, I'm just a user like you, I've just been doing this for a long time, but by all means I don't have the expertise of the vastly more knowledgeable folks here!
Copy link to clipboard
Copied
Thank you! The duplicated parent page with Italic roman numerals (lol) worked like a charm!
Good to hear that it's not only me having issues with Next Style—although, it seems to be limited to existing text, not to the typing/placing act.
It seems that Rooney has Small Caps and so does RooneySans. I may write to the designer to see if this weight difference is intentional.
The music font used is called MusGlyphs (and has a brother in MusAnalysis); it is available here for free (or donation) if you want to check.
I have checked everything once more and I can say with a certain degree of certainty that all unbalanced columns are caused by keep options. The only remaining question could be: do I need all those paragraph breaks?! Options, options, options! 😄
Thank you once again for all this. I have learned immensely and, with your permission, I would like to mention your help in the presentation article of this edition when it will be released. It will just be on my blog, few followers, few readers, nothing really big... I will not do it without your blessing, of course!
Copy link to clipboard
Copied
I checked online, and Rooney Pro is the version with real small caps. I was wrong when I told you how you could find out. But for just those cases where you use the small caps, maybe just increase the weight a bit. I'd hate to have a change in fonts for the whole book have unintended consequences.
And BTW, having shorter paragraphs helps to balance the pages because makes for more flexibility in how the paragraphs are spaced, and it makes it more readable. But don't go crazy! 🙂 Everything in moderation. Too many short paragraphs looks funny (that's the technical term).
And sure, go ahead! I do a lot of self-published books on Amazon.
Cheers,
Susan
Copy link to clipboard
Copied
Woah! So the version on Adobe Fonts is intentionally limited?! How to know what other features I may be missing out? You mentioned there may be another method to learn whether the small caps are included into the font. Can you share it?
I've just checked both Rooney Pro and RooneySans Pro and they would be a 420€ purchase each. At the moment this is not justifiable for my indie publishing business. Sure, I could do one weight at a time according to needs but I fear that would very easily lead to me losing my compass in my paragraph styles.
You will be happy to hear that, with a couple of tweaks here and there, I managed to achieve last-line alignment on 80%+ of the pages! I'm so happy! ☺️
I will let you know when the post goes live!
Thank you so much!
PS: we are both using double-returns in these posts. May we all be forgiven 😂
Copy link to clipboard
Copied
I just searched on https://fonts.adobe.com/ for Rooney Pro, and for some reason it doesn't seem to have it—it gives me Paradigm Pro. I just Googled "does font Rooney have real small caps," and I got the answer that the Pro version has them. I'd search online for "What features does Rooney Pro have that Rooney doesn't" or something like that. I don't know how to get this information on the fonts.adobe.com site, maybe someone else here knows that.
However, for your purposes, either you could get Paradigm Pro from fonts.adobe.com and use that font for those specific headings, you could just increase the weight of the small caps, or not use small caps. I'm sorry I don't know this in depth. The font should be free at fonts.adobe.com.
For the future, you can't go wrong with the classic standards for text, such as Adobe Garamond or Adobe Caslon, both available from font.adobe.com.
Copy link to clipboard
Copied
BTW, I said the font should be free at fonts.adobe, but I think this is just if you're an Adobe Creative Cloud subscriber, which is $59.99/year. You probably are if you're using InDesign, but I just mention it. Rooney is there, so I hope you didn't pay for it somewhere else!
Copy link to clipboard
Copied
Oh yes, I am an ACC subscriber and I got Rooney and RooneySans from Adobe. Actually the story is quite interesting: I was at a modern art exhibition and I fell in love with the font used in the descriptive plaques next to the paintings. I instinctively took out my phone, launched the Adobe Capture app and tried to see what it was. While the app could not identify that font precisely, it suggested RooneySans and so that was!
Only recently I switched the body text from the Sans to the Serif version because I wanted to make it more pleasing and less tiring to read. Still a process, of course.
Nice font the Paradigm Pro (and also other fonts from this designer). I will keep experimenting in the future!
Copy link to clipboard
Copied
It seems that Rooney has Small Caps and so does RooneySans. I may write to the designer to see if this weight difference is intentional.
By @Inélsòre
I did a little digging on this myself, and what you've said seems not to be true. Rooney Pro has small caps, but there seems not to be a "pro" version of Rooney Sans, and Adobe only distributes the standard version of Rooney, not the Pro, so as far as I can tell, there are no true small caps available with Adobe Fonts. You can purchase a license for Rooney Pro at MyFonts.com for the serif, but as I mentioned, there doesn't seem to be a Sans Pro.
Copy link to clipboard
Copied
This issue deserves a Feature Request. I'm going to put one in and see what happens. I know my most-used font, Adobe Garamond, has them, but it shouldn't be this hard to figure out.
Copy link to clipboard
Copied
I am often very confused by features availability within fonts. For example, when I open the contextual menu and dig into OpenType features, I have —passively?— learned that features in square brackets are either missing or not available. Following that logic, since Small Caps did not have square brackets around it, I assumed it to be working. I too was surprised by the difference in weight but that did not disturb me so much as the difference in height between capitals and small capitals.
Copy link to clipboard
Copied
The small caps should be the same as the x-height (the height of a lower case letter, such as x or m) of the text. the screenshot below (from pg vii) looks pretty good as far as the height goes.
Copy link to clipboard
Copied
The small caps should be the same as the x-height (the height of a lower case letter, such as x or m) of the text. the screenshot below (from pg vii) looks pretty good as far as the height goes.
By @Susan Culligan
If the font does not include a small caps, make one. Set a lowercase x next to a capital X then select the capital X. Adjust horizontal and vertical scaling until it looks as close as possible to the dimensions of the lowersace x. You might try bumping the weight up too, like from Light to Normal or Normal to Semibold. Once you have a style that looks right make it a character style and use that for your small caps.
Here my body copy is Avenir Roman. THe lowercase x on the right was used to set a guide. I adjusted horizontal and vertical scaling until the capital X (selected) was the same size, then I bumped the weight up to Medium and made a character style. It’s not perfect but it’s better than the default.
Copy link to clipboard
Copied
Brilliant solution!
I have heard back from the designer who confirmed that the non-Pro version of Rooney (and the only version of RooneySans) available on Adobe Fonts do not contain small caps.
Upon my request, he kindly shared the presentation document for the Rooney Pro font, telling me that features from page 10 to 12 are not included in the non-Pro version. That's all OpenType features basically!!
Now, you may say, if I haven't noticed it until now, little damage done, but I think I may need to start to find a replacement for both RooneySans (cover titles and headings) and Rooney (text within the textual portion of the music edition). I would like to avoid things that everyone is already using in music publishing: Plantin, Roboto, Minion Pro, Academico (Century Schoolbook derivate) ... Whatever I find, though, needs to have its Pro, full-feature version, on Adobe Fonts. I don't want more subscriptions for this, please.
Copy link to clipboard
Copied
Try Aldi.
Copy link to clipboard
Copied
Do you mean this one? https://fonts.adobe.com/fonts/adobe-aldine
Find more inspiration, events, and resources on the new Adobe Community
Explore Now