Dorico 5.1.81.2225 Windows specific: Weird text line leading distance in some cases

[rogerhuang]

Hi Dorico Team,

I currently collaborate with other members in my church for a hymnal project. I have both Dorico 5 and Dorico 6 on my Windows system as others have not updated to Dorico 6 yet. But I found an text issue that seems only happening on Dorico 5 windows version.

I use line break in some token columns to break the content text into two lines. I noticed that in some specific text string combination, the line leading distance is higher than normal. Subtle but noticeable. Yet when I open the same file in Dorico 5 macOS version, it doesn’t have the problem. Then I tried to open the file in Dorico 6.0 Windows version, it is displaying and exporting correctly as well. So this is not happening in Dorico 6 windows and Dorico 5/6 macOS version. It seems the bug only exists in Dorico 5 (5.1.81) Windows version.

Please see the example of how Dorico 5 Windows displays and exports below in this specific case. Look at the distance of the two lines of lyricist information at the left side:

And compare it to the result from Dorico 6 (both windows and mac versions) :

You can see that the distance between “William H. Clark” and the second line “Ralph E. Hudson (Refrain)” is bigger on Windows than on Mac. It should be the same like the composer information on the right side. Interestingly I only found the problem happened with this specific text string combination. Other hymns seem normal with various lyricist/composer information text combination.

I currently use Windows as my main machine for the project and many of my collaborators have not upgraded to Dorico 6 yet. So I have to keep working on the project with Dorico 5. With this bug, I either have to export the PDFs on a Mac or urge my collaborators to update to Dorico 6 (But we can’t do this for now, as our church just bought D5 a few months ago before the grace period and have no budget to update to D6 immediately.) And along with the buggy behavior I just reported about the text tokens on Dorico 6.0.10 in the thread below, I am having troubles temporarily before the bug is fixed.

Some token shown incorrectly when previewing/exporting since 6.0.10 (Windows)

Hi Dorico team, Just after updating to 6.0.10. I found that in some cases the text frames with multiple tokens would display incorrectly when previewing and printing/exporting. In Dorico 5 they work perfectly fine. In Dorico 6.0 the tokens without content written in project info would display grey token text and make tokens that have content displayed with offset position but previews and prints fine. Now in Dorico 6.0.10 it would also show the grey tokens but now print/exports with them, whic…

I understand now Dorico 6 is the way to go moving forward. But it would be great if the bugs on Dorico 5 can be identified and fixed as some of us need to complete projects on D5 for various considerations. I hope that the bugs on D5 and D6 I reported can both be fixed soon. I’ve also attached the project file below so you can check. Thank you!
Dorico 5 strange text leading distance issue with specifc text.dorico (1.2 MB)

[dspreadbury]

We won’t be making any further updates to Dorico 5, I’m afraid.

I won’t be able to look into the other issue you have posted about until tomorrow, but you should find that simply deactivating View > Token Placeholders is sufficient to allow you to print and export graphics from Dorico 6 with no problems.

[rogerhuang]

Hi Daniel,

Thank you for looking into the issues and the quick reply. I tried to deactivate the token placeholders in view options but the problem persists in my case. Indeed the token placeholders that has only that single token disappears, but the ones that are connected with another token as a string in the same text frame still displays and exports (I use this method to apply different fonts for English and Chinese text that needs to be at the same position by utilizing different tokens). This was not happening in Dorico 6.0, only since version 6.0.10. Maybe still an issue to solve. Thank you!