Publisher v2 to Acrobat Pro rendering bug?

[Jim Monson]

I am preparing a map for printing in Publisher v2 (2.5.7), then creating a PDF and checking it in Adobe Acrobat's Print Production/Output Preview (V. 2019.021.20049) before sending the PDF to the printer. I have done this for years in Publisher v1 and Acrobat without a problem. Now Publisher v2 and Acrobat raises the following issue. Three spot colors (with their tints) are used in this doc. 

Publisher v2  produces this a proper dash line (0.5 pt stroke, 0.1/3 pt spacing) over a blue (3005 20% tint) seen in attachment #1.

Adobe Acrobat renders the above in attachment #2.

I tried a dash line (0.5 pt stroke, 1.5/3 pt spacing) over a blue lake (3005 20% tint) seen in attachment #3.

Adobe Acrobat renders the above in attachment #4.

I have tried  making the dash line white but it renders the same as the black in Acrobat. I wonder if this incorrect rendering an Affinity of Acrobat problem? Also, I have such dash lines over my map relief without any problem. Thus it appears that having dash lines of any solid color over the 20% blue (3005) may be the problem.

[loukash]

It's likely the "Expand Stroke" bug.

Try the following workaround:

[Jim Monson]

Thanks, loukash. Before I saw your message I used another work around to get the job done. I created a solid line and then "blued out" the solid line with small blue boxes the same color as the water. This left small black squares rather than dots, but that works fine. I do believe that I found the BUG in the program. There are three options for stroke caps. By testing found that the first and last option wrongly default to the second option (that produces the thin strokes in my attachments above) rather than what they are supposed to do. This is not evident in Publisher and only shows up in the pdf. I'm not sure where the bug is in this whole process, but I would like to report it to Affinity.

[loukash]

Hm… could it be that it's been fixed in v2.6 beta?
I can't reproduce any similar issue.
But I don't have v2.5.x installed; I skipped it exactly because of these problems. 

Perhaps you may want to share an example document?