Hi, on the first page of the second movement in the attached project, I have several tokens I expect to not be there, and I’m not sure where to remove them.
The first and second pages of the piece render properly.
The second page of the second movement renders properly.
But the first page of the second movement includes “Pag”, “2.”, and “Flow Title”, which I don’t want. I can remove the tokens from the frames, but that doesn’t address subsequent movements, which also display the “first page, unexpected tokens” problem.
I’m not sure where in the page templates I should be working to remove these.
Thank you for your time!
weird-headings.dorico (1.9 MB)
You’ll note that “Pag” and “Flow Title” are in gray, which means that they won’t print – they’re just placeholder text indicating that there’s a token there. The token is (correctly) not resolving, because you have these settings in Layout Options:
As for the “2.” in the header – it’s unfortunate that Dorico doesn’t have a corresponding setting to hide the flow number in the header. There are a few ways you can handle this.
First, if you don’t want the flow number to ever appear in the header, you can go to Engrave mode, edit the Default template, and remove {@flowNumber@}.
Make sure to make this change on both the left and right pages of the template. When you apply the template, the “2.” will disappear – but the number will also disappear from the header of the second and fourth pages (BTW, I notice that your template has the page number in the upper left corner of both pages, instead of being on the right side of the RH page. Was this intentional?)
If that’s not what you want – if you want the header on p.2 to read “1. Overture” and the header on p.4 to read “2. Second Movement” – then you can edit the Flow Headings template and remove the flow number token from there. Then go into Project Info and change your flow titles so that they include the number and the period.
You’ll also need to uncheck this box, at the bottom of the Project Info page for the project.
4 Likes
Thank you so much for the detailed and helpful respose, @asherber! This makes sense to me.
Also…
That was not intentional; thank you for catching it!
1 Like