Known bug LH3796. See [url=https://forum.literatureandlatte.com/t/lh3796-compile-slicing-lines-horizontally-in-half-across-page-breaks/47148/5] for more discussion.
Potentially dumb follow-up question: Does L&L have a bug tracking system, or is subscribing to the forum links the best way to keep track of the progress of these and other bugs?
They do have a bug tracking system but it is only visible to the L&L staff. When a bug is confirmed and entered into their system, the forum thread(s) that reference that bug are modified to include the LHXXXX number of the bug. You then watch for that bug to be referenced as fixed or otherwise addressed in the release notes.
Seems a bit klunky for those wishing to provide up-to-date feedback.
For example, I’ve found two forum topics related to the topic (they share the same code):
[LH3796] Compile slicing lines horizontally in half across page breaks (this mentions the next link)
[LH3796] : Compile Formatting issue in PDF using Scrivener built in format
In the second link above Tiho_d says: “This has been improved and hopefully fixed in the next Beta 28 update.”
In the post mentioned by Kinsey, I can see a list like the below:
The fixes and changes from Beta 28 to Beta 29 are listed below.
Bug Fixes
Compile - Header and Footer only work in “First Pages” [3602]
…
So if the bug is still not fixed in Beta 29, and it’s assumed that it was (at least partially) resolved in Beta 28, what’s the best way to report on that fact: open a new thread, comment on an existing thread, or…?
Note: I’m not moaning, I’m just trying to contribute efficiently and per any established guidelines.
In general, unless you see that a bug is marked as fixed in a given beta and you can show that it’s not (with a reproducible test project), or have additional data (or a better set of repro steps/test case) to help them nail down a bug that’s still open that no one seems to have provided, just keep an eye on those threads and the release notes and test it when it’s resolved. Threads were there’s a lot of pile-on seem to obscure things for the devs.
Not all bugs will get fixed before release, and I am obviously not an L&L employee, but I would think a bug like this (where it breaks PDF output) would be high enough priority to make the cut.